Intern
What you actually do
Purchase and cancel tests. Newsletter inventory: who sent what. You are looking for double mail, not a prettier Kajabi theme.
Library / Wire / Kajabi offers still need a CRM spine
Kajabi can host the product, the landing, and some email. The leak is the same as any LMS: two lists, two welcome sequences, and a pipeline that never sees the buyer. If you run sales calls, applications, or a GHL calendar, Kajabi events must write GHL — or you will discount people who already paid.
Kajabi can host the product, the landing, and some email. The leak is the same as any LMS: two lists, two welcome sequences, and a pipeline that never sees the buyer. If you run sales calls, applications, or a GHL calendar, Kajabi events must write GHL — or you will discount people who already paid.
Pick the email system of record. If GHL owns sales nurture and Kajabi owns product onboarding, write the split. If both send 'value' newsletters, you will earn unsubscribes and blame deliverability.
Purchases must flip GHL. Otherwise the next campaign offers 20% off to customers.
Kajabi pipelines are not a substitute for GHL if your team already lives in GHL. Two pipelines with different stage names is how reporting becomes a negotiation.
Subscriptions: active, paused, canceled are states. A canceled member is not a cold lead. Do not dump them into acquire.
Landings can stay in Kajabi. Thank-you still needs to write GHL if GHL is where sales works. Hidden UTMs apply the same as any form.
Intern
Purchase and cancel tests. Newsletter inventory: who sent what. You are looking for double mail, not a prettier Kajabi theme.
Operator
Protect the split. GHL is sales truth if that is where the team works. Kajabi is campus. Suppressions every launch.
CEO
Two email systems is a tax on customers. Until write-in and one sender exist, more Kajabi offers multiply the tax.
Kajabi offer, purchase, subscription status, GHL contact, offer field, status buyer/churned, calendar/application objects in GHL, suppressions, one email system of record.
Kajabi purchase → GHL buyer state + offer; acquire and 'book a call' spines stop
Kajabi cancel/churn → status change; win-back in one system with a stop rule
GHL application or call → still the sales objects; Kajabi is not the pipeline
Choose one marketing sender: GHL or Kajabi, not alternating blasts
One page: Kajabi owns campus/access. GHL owns pipeline, sales email, WhatsApp. Product email: pick one sender. Kill the other newsletter.
Why: Without a split, every launch becomes a turf war and a double send.
Done when: A stranger can say which tool sends which email job.
Offer name, email, amount if you have it, subscription flag. Match identity. Stop sales nurture.
Why: Manual 'add a tag when we remember' is how customers get sold again.
Done when: Test purchase tags buyer in GHL within minutes.
Canceled → field and a finite save path or alumni. Not acquire. Not the same as never bought.
Why: Treating churn as a new lead is how you look greedy and how you misread conversion.
Done when: Test cancel does not receive the 'book a discovery' spine.
Applications, Calendly, opportunities stay GHL. Do not rebuild a second sales CRM in Kajabi because it has a pipeline feature.
Why: Feature overlap is how operators duplicate work and trust neither board.
Done when: A test application never creates a Kajabi 'contact' as system of record.
If Kajabi hosts the page, pass UTMs into GHL via form hidden fields or query on thank-you redirect to a GHL form.
Why: Otherwise Kajabi analytics and GHL sources will never agree.
Done when: Test URL with utm_source writes GHL source field.
Buy a Kajabi offer with a GHL lead email. Confirm GHL buyer, sales emails stopped. Cancel a subscription test. Confirm not in acquire. Send a test launch list that excludes buyers. Confirm one marketing sender. If Kajabi and GHL both sent a newsletter this week, that is the ticket.
Another Kajabi product or a GHL snapshot pack until the email split is written and purchase write-in is true. More offers into two lists is more accidental discounts to customers.
Funnel in GHL, product in Kajabi, both sending. Purchase tags missing. Sales books a call with someone who already has access. Launch blast is 'the whole Kajabi list' plus 'the whole GHL list'. That is two companies sharing a brand.
Purchase, cancel, UTM landing, launch exclusion, one newsletter sender. Monday: Kajabi sales vs GHL buyer tags.
If you have no sales team, no WhatsApp ops, no multi-step pipeline, maybe. Most training brands still need GHL objects. Then Kajabi must write in, not compete.
Now is how domains get hurt. Pick one marketing sender this week.
That split can work if purchases update GHL and suppressions are real. Write it. Test it. Do not assume.
This week
This week: job split on one page, purchase webhook, cancel state, one marketing sender, UTM test. Pause a second product.
A full calendar and an empty pipeline is two databases.
Read ↗A high score in a CSV is not a qualified opportunity.
Read ↗If the thank-you does not change the contact, the page was a brochure.
Read ↗If paid lives in Stripe and the opportunity is still open, reporting is theatre.
Read ↗Working notes
Webinar, workshop, and launch rails that survive the week after the event. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.