Server-side tracking for custom SaaS
This is the ideal case. You own the application, the database and the billing, so events can be emitted server-side from the moment they become true, with whatever identifier you choose. The only real constraint is the ad platforms' import windows, and the only real risk is that with no defaults to inherit, an unspecified event simply doesn't exist.
Free30 minutesNo obligation
custom SaaS server-side · what breaks
What goes wrong on custom SaaS
- 01
Nothing exists unless specified
No theme, no plugin, no defaults. An unspecified event doesn't fire.
- 02
The click ID stored in a cookie
Which is long gone by the time the card is charged.
- 03
Conversions weeks past the click
Straining every import window.
- 04
Signups optimized instead of revenue
Because signups are the only thing anyone wired.
custom SaaS server-side · the fix
What changes — custom SaaS server-side
Events emitted when they become true
Server-side, from your own database.
Click ID on the account record
Permanent, and referenced for the customer's life.
A bidable milestone inside the window
Chosen deliberately.
custom SaaS server-side · architecture
What custom SaaS exposes to a server container
The ideal case, with one design decision that matters more than the build.
- 1
Click ID written at signup
To the account record, as a permanent column.
- 2
Events emitted from your application
At the moment each becomes true.
- 3
Account or invoice ID as the deduplication key
Whichever is stable for the event in question.
- 4
A bidable milestone chosen deliberately
Inside the import window, with enough volume.
- 5
Churn and expansion as adjustments
So reported value moves both ways.
custom SaaS server-side · diagnose
Where custom SaaS 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 what share of accounts carry a click ID
The ceiling on everything.
- 02
Check where it's stored
A cookie won't survive to first payment.
- 03
Measure median click-to-payment
Against the import window.
- 04
List which lifecycle events are actually emitted
Usually signup and nothing else.
- 05
Compare channel rank by signup and by revenue
The gap is the value of doing this.
custom SaaS server-side · prove
The QA evidence — custom SaaS server-side
Run on custom SaaS specifically, on a live conversion rather than in preview mode.
Source of truth
your own billing and account records
- Click ID present on a live account record after signup.
- Each lifecycle event confirmed emitting from the application.
- Deduplication keys confirmed stable per event type.
- Collected revenue reconciled against your billing for a closed month.
- Churn confirmed reversing reported value.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
custom SaaS server-side · free audit
What we check in the free audit
- Check what share of accounts carry a click ID
- Check where it's stored
- Measure median click-to-payment
- List which lifecycle events are actually emitted
- Compare channel rank by signup and by revenue
Checked against
your own billing and account records
Free30 minutesNo obligation
custom SaaS server-side · when not to buy
When you don't need this on custom SaaS
Worth reading before you buy anything, from us or anyone.
- If your product converts in-session — a paid signup with an immediate charge — this is a purchase event and none of the lifecycle complexity applies.
- Your own engineers can build all of this. It's your codebase and there are no platform constraints. What we'd add is the event design and the reconciliation, not the code.
- If nobody has written an event specification, start there rather than with tags. It's the cheaper half and it's where the expensive mistakes get made.
- Measure click-to-payment before designing anything. If it exceeds the import window, the whole design changes.
custom SaaS server-side · what we deliver
What the server-side build gives you on custom SaaS
Container on your own subdomain
Your domain, your certificate, hosting in an account you control.
Money events from your billing records
Your application, emitting each event server-side at the moment it becomes true.
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 your own billing and account 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
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
custom SaaS server-side questions, answered
Not strictly. It gives you one place to manage destinations and consent, which is convenience rather than capability here.
Your own account or invoice ID — whichever is stable for the event type being sent.
Yes. With full backend control, a container is an organisational choice rather than a technical necessity.
An unwritten event specification. Everything else follows from that document existing.
Free · 30 min
Move custom SaaS events off the browser
WhatsAppFree30 minutesNo obligation
