Send closed revenue back to the ad platforms, not just form fills
If your ad platforms only ever hear about form submissions, that is exactly what they will find you more of — and in lead generation the cheapest form fills are reliably the worst leads. We capture the click ID at first touch, carry it onto the CRM record, and send qualification and closed-won back as offline conversions with real values, so bidding optimises toward deals instead of submissions.
Free30 minutesNo obligation
CRM & offline conversions · what breaks
The problem this solves — CRM & offline conversions
- 01
Sales says the leads are junk
And nobody can prove which campaign produced them.
- 02
Cost per lead looks great, cost per customer doesn't
The signature of optimising on the wrong event.
- 03
No click ID anywhere in the CRM
Which makes every downstream attribution question unanswerable.
- 04
An import that silently stopped matching
Usually after a CRM field was renamed, with the upload still reporting success.
CRM & offline conversions · the fix
What you get out of it — CRM & offline conversions
Bidding optimising toward real outcomes
Qualified leads or closed deals, whichever has the volume to train on.
Closed revenue visible per campaign
The question the business actually wants answered.
Match rates you monitor
Rather than an upload nobody checks.
Channel budget on real return
Which usually reorders the ranking substantially.
CRM & offline conversions · architecture
Why the numbers were wrong before you got here — CRM & offline conversions
Worth understanding before buying anything, because it decides which tier you need — and for some readers the answer is that you don't need us yet.
- 1
The browser is the weakest link, and it is getting weaker on purpose
Every browser-side tag has to survive the page loading, the visitor staying, the script running and the request leaving. All four are now contested. The order in your database is certain; the browser event reporting it is not.
- 2
Safari caps the cookie your attribution depends on
Intelligent Tracking Prevention limits JavaScript-set cookies to seven days whatever expiry you set, so a customer who takes longer than a week to decide returns as a stranger. A cookie your own server writes in an HTTP response is not capped — the single largest practical difference between browser-side and first-party server-side.
- 3
Ad blockers remove the tag with no error
A blocked pixel does not warn anyone. The customer buys, the order lands, and no platform hears about it. First-party events from your own subdomain are not a third-party request and are not filtered the same way.
- 4
Consent is enforced by hope, not by architecture
Client-side consent means trusting each vendor script to honour a flag. A server container decides at the container: a denied destination receives nothing. That is a materially stronger position, and it also stops the over-blocking that discards data no law required losing.
- 5
Checkout can end where your tag isn't
Wallets and hosted payment pages can be abandoned after the money moves. Sending the purchase from the order record means it arrives whether or not anyone came back.
CRM & offline conversions · diagnose
How we scope the offline conversion loop
Before quoting. Each step narrows what the work actually is, so the price reflects your account rather than an average.
- 01
Check whether any CRM record holds a click ID
The blocking issue, and the first thing to establish.
- 02
Trace one real closed deal backwards
Click, form, CRM record, stage changes, close. Every stage that lost the identifier is a stage to fix.
- 03
Audit stage hygiene
Inconsistently set stages export inconsistency straight into bidding.
- 04
Count weekly volume per stage
To pick the deepest stage bidding can actually learn from.
- 05
Compare cycle length to attribution windows
A 90-day cycle against a 30-day window can never work.
- 06
Check existing upload match rates
Success and matching are different results.
CRM & offline conversions · prove
How the work gets proven — CRM & offline conversions
A dashboard turning green proves a dashboard turned green. These are what we hand over instead.
Source of truth
Your CRM's qualified and closed-won records
- Click IDs present on the large majority of CRM records created from paid traffic.
- Match rates read from each destination platform rather than upload counts.
- Closed-won revenue visible against originating campaigns in at least one platform.
- One deal traced end to end from click through to signature, documented.
- Upload monitored, so a silent failure alerts rather than accumulating.
- Reconciled over a fully closed window, matched on ID rather than on totals — totals hide equal and opposite errors.
- Payload evidence captured from real transactions, saved to your own records.
- The same reconciliation repeated 30 days later, because a setup that works once and drifts is the harder failure.
CRM & offline conversions · free audit
What we check in the free audit
- Check whether any CRM record holds a click ID
- Trace one real closed deal backwards
- Audit stage hygiene
- Count weekly volume per stage
- Compare cycle length to attribution windows
- Check existing upload match rates
Checked against
Your CRM's qualified and closed-won records
Free30 minutesNo obligation
CRM & offline conversions · when not to buy
When you shouldn't buy this — CRM & offline conversions
We would rather say it now than three weeks into an engagement.
- You get under about 20 leads a month. Bidding cannot learn from deeper stages at that volume, and manual review serves you better.
- You have no CRM, or one nobody updates. This loop depends entirely on maintained stage data — fix that first.
- Your leads close in the same session. A standard conversion event already covers you.
- Your problem is that leads don't convert, not that they're miscounted. Tracking will measure that faster; it won't change it.
CRM & offline conversions · what we deliver
What's included in the offline conversion loop
Click ID capture and storage
gclid, gbraid, wbraid, fbclid, msclkid and li_fat_id onto the CRM record at first touch.
Stage mapping
Which CRM stages become which platform conversions, agreed and documented.
Automated export
Stage changes sent back on schedule, with values attached.
Per-platform delivery
Enhanced Conversions for Leads on Google, offline events on Meta, offline conversions on LinkedIn and Microsoft.
Match rate monitoring
So a silent failure raises an alert instead of surfacing a quarter later.
Attribution windows aligned
To your real median sales cycle, so deals aren't refused for closing late.
Written guarantee
95%+ tracking accuracy
Measured against Your CRM's qualified and closed-won records. 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
The correct browser-side build, done properly and verified on a live transaction. Honest about its ceiling: it will not survive Safari's cookie cap, an ad blocker, or a checkout that ends somewhere your tag isn't. If you spend $1K+/month on paid media, start one tier up.
- Correct events, correct parameters, correct values
- Verified on a live transaction, not in preview
- Reconciled against your own order records
- Written handover you keep
1st-party server-side
Recommended$800One-time fee · most popular
The tier that changes the outcome rather than patching it. Your money events stop depending on the browser: they are sent from your order records through a first-party server container on your own subdomain, so iOS, ad blockers, consent banners and interrupted payment redirects can no longer take them away. Built in 2–4 days. You own the stack outright, with no monthly SaaS.
- First-party server container on your own subdomain
- Money events sent from your order records, not the browser
- Meta, Google, TikTok, Microsoft and LinkedIn all fed server-side
- Deduplicated on a shared event ID, verified at every destination
- First-party cookies beyond Safari's 7-day cap on JavaScript-set cookies
- 95%+ conversion accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid-media channel server-side, plus the offline loop that connects closed revenue back to the click. For advertisers whose spend makes an attribution leak more expensive than the build.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop, so closed revenue reaches bidding
- Refunds and cancellations reversed at every destination
- Klaviyo identity stitching, BigQuery and Looker Studio
- Monitoring, so the next break surfaces in days rather than a quarter
FAQ
CRM & offline conversions questions, answered
Only where the click ID was captured at the time. If it wasn't, that information doesn't exist anywhere and can't be reconstructed — which is why this is worth fixing the day you find it.
The deepest one with enough weekly volume to train. Closed-won is ideal and often too sparse; qualified lead is the usual compromise.
Optimise on an earlier stage inside the window, and report closed revenue separately for budget decisions.
Not necessarily. A workflow webhook or a scheduled export both work. What matters is that stage changes leave with the click ID attached.
Free · 30 min
Get closed revenue back into bidding
WhatsAppFree30 minutesNo obligation
