Skip to main content
trial-to-paid not trackedDiagnosis and fix

Why isn't my trial-to-paid conversion being tracked?

The trial-to-paid conversion happens days or weeks after the signup, when the first charge succeeds — and there is no browser session at that moment for a tag to fire from. So unless the click ID was stored on the account at signup and the billing system is wired to send the charge back, the event that actually matters is invisible. The consequence is that bidding optimises on trial starts, which is exactly how you buy people who trial and never pay.

Free30 minutesNo obligation

trial-to-paid not tracked · what breaks

What this looks like when it's happening to you — trial-to-paid not tracked

  1. 01

    Bidding optimising on trial signups

    And finding you people who never convert.

  2. 02

    Paid conversions absent from the ad platforms

    The revenue event never reported.

  3. 03

    Trial volume up, paid volume flat

    The signature of optimising on the wrong event.

trial-to-paid not tracked · the fix

What changes once it's fixed — trial-to-paid not tracked

  • The first charge reported

    As a conversion, with its real value.

  • Bidding trained on paying customers

    Or on the activation event that predicts them.

  • Trials still visible

    Reported, but not used as the optimisation target.

trial-to-paid not tracked · architecture

Why your conversion data was wrong in the first place — trial-to-paid not tracked

Fixing this specific fault is worth doing. But it is worth understanding why it happened, because the same underlying weakness produces a different symptom every few months — and the reason your conversion data is wrong is almost never the tag itself.

  1. 1

    Your conversion depends on a browser that is being restricted on purpose

    A browser-side tag has to survive the page loading, the visitor staying, the script executing and the request leaving. Every one of those is now contested. The order in your database is certain; the browser event reporting it is not, and that gap is where wrong numbers come from.

  2. 2

    Safari caps the cookie your attribution depends on

    Intelligent Tracking Prevention limits cookies written by JavaScript to seven days, whatever expiry you set. Any customer who takes longer than a week to decide comes back as a stranger, so the sale is recorded and credited to nobody. A cookie your own server writes in an HTTP response is not subject to that cap — which is the single largest practical difference between browser-side and first-party server-side tracking.

  3. 3

    Ad blockers remove the tag before it can run

    A blocked pixel does not error, retry or warn anyone. The visitor buys, the order lands in your store, and no platform ever hears about it. First-party events sent from your own subdomain aren't filtered the same way, because they are not a third-party request.

  4. 4

    Consent banners stop tags, sometimes when they didn't need to

    Where consent is genuinely required, losing the event is correct. What is not correct — and what we find repeatedly on US-majority accounts — is an EU-style prior-consent banner applied to every visitor, discarding conversions no law asked you to discard. A server container enforces the real decision at the container rather than hoping each vendor script honours a flag.

  5. 5

    The checkout can end somewhere your tag isn't

    Wallets and hosted payment pages can be abandoned after the money moves. The customer paid; the confirmation page never rendered; the browser event never fired. Sending the purchase from the order record instead means the conversion arrives whether or not anyone came back to your site.

  6. 6

    What that adds up to

    Each of these is a separate route to trial-to-paid not tracked, and they compound. First-party server-side tracking doesn't patch them one at a time — it moves the money event off the browser entirely, so the order in your backend is what gets reported. That is why we reconcile against your own order records and put 95%+ accuracy in writing: with the event sourced from the order, the number is checkable rather than hopeful.

trial-to-paid not tracked · normal or broken

Some of this is supposed to happen — trial-to-paid not tracked

Half the time nothing is broken and the number is being read wrong. Knowing which is which stops you paying to fix something that was never a fault.

Normal, not a fault

  • Most trials not converting

    That's the funnel. The ratio matters, not the gap.

  • A delay between spend and reported revenue

    A 14-day trial plus a billing cycle means recent ROAS is always understated.

Actually broken

  • No click ID on the account record

    Nothing to attribute the later charge to.

  • No billing integration

    The charge happens and nothing tells the ad platform.

  • Attribution window shorter than the trial

    A 30-day window on a 30-day trial refuses the conversion.

  • Trial start used as the conversion

    So the platform optimises for the wrong outcome by design.

trial-to-paid not tracked · diagnose

How we find out why isn't my trial-to-paid conversion being tracked

Always in this order. Each step eliminates a class of cause, so by the last one there is usually a single explanation standing.

  1. 01

    Check whether accounts store a click ID

    Filter for non-empty. Usually the finding.

  2. 02

    Check what the platforms currently optimise on

    Signup, trial or paid.

  3. 03

    Check whether billing events reach anything

    Most accounts have no integration at all.

  4. 04

    Compare trial length to the attribution window

    A trial longer than the window can never attribute.

  5. 05

    Look for an activation event

    The early action that predicts payment.

trial-to-paid not tracked · prove

How we prove it's actually fixed — trial-to-paid not tracked

The tag firing again proves the tag fires. These prove the numbers are right.

Source of truth

Your billing system's first-charge records

  • Click IDs present on the large majority of accounts created from paid traffic.
  • First-charge count matching billing records for a closed month.
  • Conversion value equal to the amount actually charged.
  • One customer traced from ad click through to first payment.
  • Reconciled against your billing system's first-charge records for a fully closed window, matched on ID rather than on totals.
  • No record counted twice, checked across the whole window rather than spot-checked.
  • The same check repeated 30 days later, because a fix that holds once and drifts is the harder failure to catch.

trial-to-paid not tracked · free audit

What we check in the free audit

  • Check whether accounts store a click ID
  • Check what the platforms currently optimise on
  • Check whether billing events reach anything
  • Compare trial length to the attribution window
  • Look for an activation event

Checked against

Your billing system's first-charge records

Get my free conversion tracking audit

Free30 minutesNo obligation

trial-to-paid not tracked · when not to buy

When you don't need us for this — trial-to-paid not tracked

Most of these you can do yourself, and we would rather you did.

  • Your trial converts in the same session at low price. A standard purchase event covers you.
  • You're pre-product-market-fit with a small paid experiment. Learn what converts first.
  • Your billing system has no webhooks. Solve that before anything else here is possible.

trial-to-paid not tracked · what we deliver

What we do about it — trial-to-paid not tracked

  • Click ID stored on the account

    At signup, so a charge weeks later can still be attributed.

  • Billing webhook wired

    First successful charge sent as the conversion.

  • Activation event identified

    The early action predicting retention, often the better target.

Pricing

Pick the package that fits your ad spend

Browser-side starter

$400One-time fee · lifetime ownership

We fix the fault in your existing browser-side setup and verify it on a live transaction. Honest disclosure: this repairs what you have, it does not make it durable. If you spend $1K+/month on paid media, the fault will recur the next time Safari, a consent banner or a checkout change moves under you — the server-side tier is what stops that.

  • Root cause found and fixed, not worked around
  • Verified on a live transaction, not in preview
  • Reconciled against your own order records
  • Written handover documenting what changed and why
Fix what I have

1st-party server-side

Recommended

$800One-time fee · most popular

The tier that removes the whole class of failure rather than this instance of 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 — no monthly SaaS.

  • First-party server container on your own subdomain
  • Purchases 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
Rebuild it server-side

Full 1st-party stack

$1,800One-time fee · lifetime ownership

Every paid-media channel server-side, end to end, plus the offline loop. For advertisers whose spend makes an attribution leak more expensive than the build. Pay once, own everything.

  • 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
Get the full stack

FAQ

trial-to-paid not tracked questions, answered

Usually neither. The best target is the earliest event that reliably predicts payment and has enough weekly volume — often an in-product activation action rather than a billing event.

Free · 30 min

Get trial-to-paid not tracked diagnosed properly

Free30 minutesNo obligation