Conversion tracking for custom SaaS
A custom SaaS product has no platform constraints at all, which removes every excuse and creates a different problem: nothing is provided, so nothing exists unless someone specified it. The conversions that matter — activation, first payment, expansion, churn — all live in your own database, weeks after the click, with no browser anywhere near them. That's an advantage as long as the click identifier was written to the account record at signup.
Free30 minutesNo obligation
custom SaaS tracking · 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 tracking · the fix
What changes — custom SaaS tracking
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 tracking · architecture
What custom SaaS actually lets you do
You own everything, so the only limits are the ones the ad platforms impose.
- 1
Your own database
Any event, any identifier, any moment.
- 2
Server-side emission
No dependency on a browser running anything correctly.
- 3
Full account records
The click ID can live permanently alongside the customer.
- 4
Your own billing
Authoritative revenue, trivially reconcilable.
- 5
No platform defaults
The one downside: nothing happens automatically.
custom SaaS tracking · 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 tracking · prove
The QA evidence — custom SaaS tracking
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 tracking · 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 tracking · 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 tracking · what we deliver
The event map on custom SaaS
Signup
Server-side. Click ID written to the account record here or nowhere.
Activation milestone
Server-side, from your product data. Often the best early predictor.
First payment
Server-side from billing. The conversion that matters.
Expansion and downgrade
Server-side adjustments.
Churn
Server-side, voluntary and involuntary separated.
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 tracking questions, answered
That nothing is automatic. No theme or plugin provides defaults, so an unspecified event simply doesn't exist.
A column on the account record, written at signup. A cookie won't survive to the first payment.
The most downstream one that fits inside the import window and produces enough volume. Usually activation or first payment.
You need somewhere to dispatch to destinations. Whether that's a container or your own code is a preference, not a requirement.
Free · 30 min
Get custom SaaS tracking done properly
WhatsAppFree30 minutesNo obligation
