Server-side tracking for Keap
The Keap build is mostly discipline. Write the identifier to a contact field at first touch and guard it, fire from an HTTP post inside the automation that runs on a genuine money event, and resist the temptation to treat every tag as a conversion. At Keap's typical business size a small handler is the right infrastructure, not a container.
Free30 minutesNo obligation
Keap server-side · what breaks
What goes wrong on Keap
- 01
Tag applications sent as conversions
Tags come from automation as readily as from sales events.
- 02
The identifier overwritten by nurture sequences
Keap touches contacts constantly.
- 03
Orders and opportunities as two different money models
Product sales and service deals both live here.
- 04
Small-business scale versus build complexity
Over-engineering is the common failure at this size.
Keap server-side · the fix
What changes — Keap server-side
Orders paid or opportunities won as the conversion
At the real amount.
The first-touch identifier preserved
Guarded against automation overwrites.
Automation-driven tags excluded
Only commercially meaningful events reach the ad platforms.
Keap server-side · architecture
What Keap exposes to a server container
The server-side build on Keap specifically.
- 1
Write the identifier once, at first touch
And guard it against automation overwrites.
- 2
Fire from an HTTP post on a money event
Order paid or opportunity won, not tag applied.
- 3
Value subscriptions over their term
Not at the first payment.
- 4
Keep automation tags out of the conversion path
Report them; never send them.
- 5
Size the build to the business
A handler, not a container.
Keap server-side · diagnose
Where Keap tracking breaks, in diagnostic order
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Check whether the identifier field survives a nurture click
Look at a contact who engaged after converting.
- 02
Compare Keap orders against reported conversions
Per order, over a closed window.
- 03
Look for tag applications being sent as conversions
The Keap-specific trap.
- 04
Check the nurture sequence length
Against every import window.
- 05
Confirm subscriptions are valued over term
Not per payment.
Keap server-side · prove
The QA evidence — Keap server-side
Run on Keap specifically, on a live conversion rather than in preview mode.
Source of truth
Keap's orders and won opportunities — by date, at their amounts
- A contact created from a paid click, with the identifier unchanged after a later automation touch.
- Orders reconciled per order against each platform over a closed window.
- A subscription confirmed to carry its term value.
- Tag applications confirmed absent from every conversion action.
- The nurture-to-sale duration measured against every import window.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Keap server-side · free audit
What we check in the free audit
- Check whether the identifier field survives a nurture click
- Compare Keap orders against reported conversions
- Look for tag applications being sent as conversions
- Check the nurture sequence length
- Confirm subscriptions are valued over term
Checked against
Keap's orders and won opportunities — by date, at their amounts
Free30 minutesNo obligation
Keap server-side · when not to buy
When you don't need this on Keap
Worth reading before you buy anything, from us or anyone.
- If money is taken in a separate system you already track, the Keap side may only need the identifier preserved.
- If you only run broadcast email with no automation, most of this does not apply.
- Check whether tags are currently being sent as conversions. Removing them is free and often the biggest single improvement.
- At Keap's typical scale a container is more infrastructure than the business needs.
Keap server-side · what we deliver
What the server-side build gives you on Keap
Container on your own subdomain
Your domain, your certificate, hosting in an account you control.
Money events from Keap orders and won opportunities
Keap's orders are authoritative for product revenue and its opportunities for service revenue. If payment is taken elsewhere, that system is authoritative and the two need reconciling before either is used as evidence.
Deduplicated at every destination
On a shared event ID, verified before any existing path is removed.
Consent enforced before dispatch
A denied destination receives nothing, verified by capture rather than configuration.
Written guarantee
95%+ tracking accuracy
Measured against Keap's orders and won opportunities — by date, at their amounts. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Keap server-side questions, answered
Because Keap applies them from automated sequences, from internal admin actions and from genuine sales events, and nothing outside Keap can tell those apart. A tag-based conversion feed teaches your ad platform to find people who trigger your automation, which is a much larger and much less valuable population than your buyers.
Write it once on contact creation and add a condition so later sequences cannot rewrite it. Without that guard, a nurture click updates the field and your own email gets credited for a sale paid media produced.
Handler. Keap businesses are small by design, and an HTTP post from an automation to a small endpoint does everything a container would here.
Good for understanding your automation. Not a substitute for sending money events to ad platforms, which it does not do.
WhatsApp