Conversion tracking for Keap
Keap is a CRM and marketing automation platform aimed at small businesses, and its defining characteristic for tracking purposes is that campaign automation is the centre of gravity rather than a bolt-on. Tags drive everything, which is powerful and creates a specific hazard: a tag applied by an automated sequence looks identical to one applied by a genuine sales event, and sending tag applications as conversions teaches an ad platform to find people who trigger your own automation.
Free30 minutesNo obligation
Keap tracking · 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 tracking · the fix
What changes — Keap tracking
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 tracking · architecture
What Keap actually lets you do
What Keap gives you.
- 1
Custom contact fields
Where the identifier lives across a long nurture sequence.
- 2
Campaign automation with HTTP posts
The reliable outbound trigger.
- 3
Orders, subscriptions and opportunities as distinct objects
Two money models in one platform.
- 4
Tags as the universal mechanism
Powerful, and ambiguous as a conversion signal.
- 5
No conversion sending
Automates and reports; pushes nothing to ad platforms.
Keap tracking · 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 tracking · prove
The QA evidence — Keap tracking
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 tracking · 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 tracking · 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 tracking · what we deliver
The event map on Keap
Contact created
Where the identifier is written, once.
Tag applied by automation
Not a conversion. Reported at most.
Opportunity won
The money event for service businesses.
Order paid
The money event for product businesses.
Subscription started
Recurring revenue, valued over its term.
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 tracking questions, answered
You can, and it is usually a mistake. Keap tags get applied by automated sequences, by internal admin, and by genuine sales events, and they look the same from outside. Send orders or won opportunities — things that represent money — and use tags only where a specific tag reliably means a specific commercial event.
An order paid, or an opportunity marked won, at its amount. Keap holds both, and which one applies depends on whether you sell products or services.
A custom contact field, written once at first touch and guarded against being overwritten by later automation. Keap's sequences touch contacts constantly, so an unguarded field will be rewritten.
No. It automates internally and reports internally. The loop back to bidding is not there.
