Skip to main content
Trial to paidEngagement pattern

Attributing paid subscriptions back to the campaign that produced the trial

The moment that matters for a SaaS business happens weeks after the click, usually in a billing system with no browser attached, so browser-side tracking cannot see it by construction. The chain that works is: capture the click ID at signup, store it on the account record, and fire the conversion when the first payment clears — referencing the click that started it. The two constraints that shape the design are Google's 90-day import window and a trial length that has to fit inside it.

Free30 minutesNo obligation

Trial to paid · what breaks

The situation, as it usually presents — Trial to paid

  1. 01

    Bidding optimizing toward trial signups

    Including the ones that never pay.

  2. 02

    Paid conversions invisible to the platforms

    They happen with no browser present.

  3. 03

    Channels ranked by signup volume

    Rather than by revenue.

Trial to paid · the fix

What changes — Trial to paid

  • Paid conversion attributed to the original click

    Weeks later.

  • Trial and paid as separate events

    Different values, different roles.

  • Channel ranking by revenue

    Which frequently reorders the list.

Trial to paid · architecture

Why this pattern keeps recurring — Trial to paid

The trial-to-paid gap is a timing problem rather than a tagging problem, which is why more tags never close it.

  1. 1

    The conversion happens with no browser

    A card charged on day 14 involves no page, no tag and no session. Only the billing system knows.

  2. 2

    Cookies are long gone by then

    Even without ITP, weeks exceed most attribution storage. The identifier has to live on your account record.

  3. 3

    Google's window is 90 days

    A 30-day trial plus a slow start still fits; a 6-month enterprise cycle does not.

  4. 4

    Signups and revenue rank channels differently

    Which is the whole reason to do this — the cheapest signups often produce the worst customers.

Trial to paid · diagnose

How the root cause gets found — Trial to paid

In this order. Each step rules out a class of cause, so the last one usually has a single explanation standing.

  1. 01

    Measure what share of accounts carry a click ID

    The ceiling on everything.

  2. 02

    Check where the ID is stored

    Session, cookie or account record.

  3. 03

    Measure trial length against 90 days

    It constrains the design.

  4. 04

    Confirm the billing system can fire a webhook

    It's the trigger.

  5. 05

    Compare channel rank by signup and by revenue

    The gap is the value of this work.

Trial to paid · prove

How the work is proven — Trial to paid

Against the client's own records, not a dashboard turning green.

Source of truth

Billing records for first successful payment

  • Click ID present on a live account record after signup.
  • First payment confirmed firing a conversion referencing that click.
  • Trial and paid arriving as distinct events with distinct values.
  • Import match rate read rather than assumed.
  • Reconciled over a fully closed window, matched on ID rather than on totals.
  • Payload evidence captured from real transactions and handed over.
  • The same reconciliation repeated 30 days later.

Trial to paid · free audit

What we check in the free audit

  • Measure what share of accounts carry a click ID
  • Check where the ID is stored
  • Measure trial length against 90 days
  • Confirm the billing system can fire a webhook
  • Compare channel rank by signup and by revenue

Checked against

Billing records for first successful payment

Get my free conversion tracking audit

Free30 minutesNo obligation

Trial to paid · when not to buy

Why there are no client numbers on this page — Trial to paid

Most agency case studies lead with a percentage. This one doesn't, and the reason is worth stating.

  • We don't publish client results we can't substantiate. An audit of this site in August 2026 found named testimonials and before-and-after figures that had never been measured — all of it was removed, and nothing has replaced it that isn't checkable.
  • The results that do exist belong to clients under agreement. Publishing anonymised numbers without their sign-off would be the same problem in a thinner disguise.
  • What we will commit to in writing is 95%+ conversion accuracy and 8+ Meta Event Match Quality, reconciled against your own order records. That is checkable by you, which a case study percentage never is.
  • For proof from actual clients, the video testimonials on the site are real people describing their own rebuild. That is the strongest evidence we have, and it isn't a number we wrote.

Trial to paid · what we deliver

What the work involves — Trial to paid

  • Click ID captured at signup

    And stored on the account record permanently.

  • First payment wired to a server conversion

    From the billing system.

  • Trial length checked against the 90-day window

    It constrains what's importable.

  • Values assigned per stage

    Trial modelled, paid actual.

Written guarantee

95%+ tracking accuracy

Measured against Billing records for first successful payment. Miss it and we keep working at no cost.

Get my free conversion tracking audit

Pricing

Pick the package that fits your ad spend

Browser-side starter

$400One-time fee · lifetime ownership

Repairs the fault in your existing browser-side setup and verifies it on a live transaction. Honest about its ceiling: it fixes this instance, not the class.

  • Root cause fixed, not worked around
  • Verified on a live transaction
  • Reconciled against your own records
  • Written handover
Fix what I have

1st-party server-side

Recommended

$800One-time fee · most popular

Removes the class of failure rather than this instance. Money events sent from your order records through a first-party container on your own subdomain, so the browser can no longer lose them.

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

Full 1st-party stack

$1,800One-time fee · lifetime ownership

Every paid channel server-side plus the offline loop, 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
  • Refunds reversed at every destination
  • Monitoring so the next break surfaces in days
Get the full stack

FAQ

Trial to paid questions, answered

Google's import window won't reach it. Optimize toward an earlier qualified milestone inside the window and use the later data for reporting rather than bidding.

Free · 30 min

Attribute paid subscriptions, not just trials

Free30 minutesNo obligation