Server-Side Tracking for Info Product Businesses
How course creators and coaches send webinar, application, purchase and upsell events server-side to Meta, without duplicates or restricted data.
Article summary
TL;DR
Server-side tracking sends funnel events from the system that records them (your checkout, your course platform) straight to Meta, Google and TikTok, so ad blockers and browser limits don't erase them. For course creators and coaches, the hard part is the funnel: webinar sign-ups, applications, upsells and plan installments. Kajabi's own Conversions API sends only purchases and leads.
- Meta recommends running the Conversions API alongside the pixel, deduplicated with the same event name and event ID.
- Kajabi sends "two types of events via the Meta Conversions API: Purchases and Leads", and warns against using its token and a third-party gateway at the same time.
- Meta has standard events that fit a coaching funnel, including "SubmitApplication" and "Subscribe".
- Meta ads "must not request financial information, including … income, net worth or how much debt someone has" without permission: keep those answers out of your event data too.
- Meta's restrictions on health and wellness data sources apply to both the pixel and the Conversions API, as reported by CustomerLabs.
On this page
This guide is part of our playbook on the best ecommerce platform for info product businesses. The general guide: server-side tracking. The ad rules are in Meta and TikTok ads for info product businesses.
Where info product funnels lose events
A course funnel crosses more tools than a store. Each handoff can drop an event.
Fig. 1Five handoffs where a course funnel drops events
Several domains
The sales page, the checkout and the course area often sit on different domains, and the browser session breaks between them.
Webinars and calls
Registration happens on one tool, attendance on another, the sale on a call days later.
Upsells after payment
One-click upsells run on their own pages, often after the thank-you page fires.
Installments and renewals
They happen with no browser at all.
Ad blockers and privacy settings
Stop part of the pixel events everywhere.
Each lost purchase makes your cost per sale look higher and teaches the ad platform less about who buys.
What your course platform sends on its own
| Setup | Server events | What's missing |
|---|---|---|
| Kajabi with Meta token | Purchases and Leads via the Conversions API2Kajabi Help, Meta Pixel enhancements, read November 2, 2026 | Applications, webinar attendance, other events stay browser-only2Kajabi Help, Meta Pixel enhancements, read November 2, 2026 |
| Kajabi with a third-party gateway | What the gateway sends | Don't use both: purchases can be counted twice2Kajabi Help, Meta Pixel enhancements, read November 2, 2026 |
| Platform with pixel only | None | All browser losses |
| Separate checkout that sends server events | Purchases, upsells and renewals from where payment happens | Lead and webinar events still come from your page or email tool |
| Shopify store | Through web pixels and apps | Code left in "Additional scripts" stopped on August 26, 2026 for non-Plus stores6Shopify.dev, Apps in checkout, read November 2, 2026 |
On Kajabi's Enhanced Checkout, "items with different payment types" are processed "as separate purchases", each with its own Purchase event2Kajabi Help, Meta Pixel enhancements, read November 2, 2026. Check how that shows in your reports before you compare months.
Map your funnel to standard events
Use Meta's standard events where they fit. They are easier to optimize for than custom names.
| Funnel step | Meta standard event | Meta's definition3Meta for Developers, Meta Pixel reference, standard events, read November 2, 2026 |
|---|---|---|
| Free guide or waitlist signup | Lead | "A person completes a sign-up." |
| Webinar or challenge registration | CompleteRegistration | "A person finishes filling out a signup or subscription form." |
| High-ticket coaching application | SubmitApplication | "A person applies for a product, service, or program." |
| Checkout started | InitiateCheckout | Checkout started but not finished |
| Course or program bought | Purchase | "A person completes a purchase or the checkout flow." |
| Membership started | Subscribe | "A person starts a paid subscription." |
| Free trial of a membership | StartTrial | "A person begins a free trial of a product or service." |
Fig. 2One funnel, one standard event per step
- Webinar registrationCompleteRegistration · page or email tool
- ApplicationSubmitApplication · page
- CheckoutInitiateCheckout · pixel
- PurchasePurchase · pixel and server, same event ID
- UpsellIts own server event and value
- InstallmentsServer only, no browser
The later the step, the less the browser sees.
Payment plans, upsells and renewals
These are where server events matter most, because no browser is involved.
- Pick one rule for payment plans. Send the first payment as the Purchase with its real amount, or the full contract value once; don't mix both, or your cost per sale moves for no reason.
- Send each upsell as its own server event with its own value, after the payment clears.
- Keep installments and renewals apart from new sales, so this month's ads don't get credit for last quarter's buyers. How to read them: ad attribution for info product businesses.
- Send refunds back to your own reports, so a launch that drives refunds doesn't look like a win.
What data to send, and what never to send
| Send | Never send |
|---|---|
| Event name and event ID, shared with the pixel1Meta for Developers, Deduplicate Pixel and server events, read October 26, 2026 | Quiz or application answers about income, savings or debt |
| Order value and currency | Custom parameters that describe a financial situation ("in debt", "lost job") |
| Hashed email and phone, where consented | Health conditions, for health or weight coaching |
| Product IDs or neutral categories ("course", "coaching", "membership") | Audience names built on financial or health traits |
Meta's ad rules forbid ads that assert or imply personal attributes, including "vulnerable financial status"4Meta Advertising Standards, Privacy violations and personal attributes, read November 2, 2026. Event data that labels buyers by debt or income invites the same problem.
Watch out
If you sell health, weight or nutrition coaching, Meta may classify your data source as health and wellness. CustomerLabs describes four degrees of restriction, from stripping URL details to blocking events, and says they apply to the pixel and the Conversions API alike5CustomerLabs Docs, Meta health and wellness restrictions, read November 2, 2026 (vendor documentation, undated). Server-side tracking does not lift them. Never rename events or disguise products to slip past a category; ask Meta for a review if you think it is wrong.
Setup
- Keep the pixel on your pages for browser events.
- Add server events from the system that takes payment, and from your course platform where it supports them.
- Use the same event name and event ID in the pixel and the server event, so Meta deduplicates them1Meta for Developers, Deduplicate Pixel and server events, read October 26, 2026.
- Choose one server source per event. On Kajabi, its token or a gateway, not both2Kajabi Help, Meta Pixel enhancements, read November 2, 2026.
- Map every funnel step to a standard event, including applications and memberships3Meta for Developers, Meta Pixel reference, standard events, read November 2, 2026.
- Send upsells, installments and renewals server-side with the right value and a clear type.
Two sources, one event ID, one server source per event.
Check that it works
Fig. 3One purchase, two sources, counted once
approved declined or closed routing step
- PixelPurchase, event ID shared
- plusServer eventSame event name and event ID
- deduplicates
MetaMerged, not doubledApproved
| Check | How | Healthy sign |
|---|---|---|
| Deduplication | Events Manager, event overview | Browser and server events merged, not doubled |
| Coverage | Ad platform purchases vs. checkout orders, same days | A small, stable gap |
| Upsells | Server events by type | One event per accepted upsell |
| Applications | SubmitApplication count vs. applications received | Close to equal |
| Category status | Events Manager, data source settings | NoNew limitation |
How Tagada helps
Purchase, upsell and renewal events sent from the checkout
- Server-side events to Meta, Google and TikTok, sent from the checkout that takes the payment, including one-click upsells and subscriptions
- Automatic server postbacks on each paid order to trackers such as ClickFlare, Voluum, Binom, RedTrack and ClickMagick, and Hyros by email and phone; "You don't need to install pixels on your checkout or thank-you page"7Tagada Docs, Tracking overview, read November 2, 2026
- Checkout, one-click upsells, subscriptions and membership on the same funnel, so post-purchase revenue is sent from one place
- Already on Shopify, WooCommerce or ClickFunnels? Drop TagadaPay in, or run standalone or headless
"If you sell something real, we will get you paid." TagadaPay lists info products, coaching and online courses among its industries, with "enhanced review for regulated verticals"; "Most merchants are live under 24 hours"8TagadaPay, homepage, read November 2, 2026. Plans are on the pricing page.

Frequently asked questions
Does Kajabi support the Meta Conversions API?
Why are my Meta purchases counted twice?
How do I track webinar registrations and coaching applications?
Should I send payment plan installments to Meta?
Is server-side tracking the same as the Conversions API?
Sources
Checked November 3, 2026- Meta for Developers, Deduplicate Pixel and server events, read October 26, 2026
- Kajabi Help, Meta Pixel enhancements, read November 2, 2026
- Meta for Developers, Meta Pixel reference, standard events, read November 2, 2026
- Meta Advertising Standards, Privacy violations and personal attributes, read November 2, 2026
- CustomerLabs Docs, Meta health and wellness restrictions, read November 2, 2026 (vendor documentation, undated)
- Shopify.dev, Apps in checkout, read November 2, 2026
- Tagada Docs, Tracking overview, read November 2, 2026
- TagadaPay, homepage, read November 2, 2026
Tagada
Send every course sale, upsell and renewal from where it is paid
Funnels, one-click upsells, subscription billing and payment routing, on one customer record.
- 01Create your free account
- 02Connect your store or build a checkout
- 03Launch funnels, upsells and subscriptions
