Skip to content

Trials, demos and paid plans

Two hundred signups. Eight paying customers.

SaaS ads are judged on signups because that's what the tag sees, but most signups never pay. We send qualified trials, demos held and paid plans back from Stripe or the CRM, with plan value or ACV, so bidding learns which campaigns bring customers, not just accounts.

WHO IT'S FOR

  • B2B SaaS companies with self-serve free trials or freemium plans
  • Sales-led SaaS booking demos, with deals managed in HubSpot or Salesforce
  • Products with both, where trials and demos need to be told apart in reporting

Why it's different

The rules that change the setup.

  • 01

    A signup isn't a customer

    Free trials attract students, competitors and tyre-kickers. If bidding only sees signups, it finds more of them.

  • 02

    Cycles run for weeks or months

    Trials convert after days or weeks, and sales-led deals can take months. Outcomes need sending back as they happen, within the window the ad platforms accept.

  • 03

    Product analytics isn't ad tracking

    Mixpanel, Amplitude or PostHog show what users do in the app. Ad platforms need a few clear outcomes tied to a click ID. Both have a place, and they shouldn't be confused.

  • 04

    Signup often happens on another domain

    Marketing site on one domain, app on another, payments on a third. Without cross-domain setup, the click ID is lost before the conversion.

The data map

What goes out, and what never does.

What ad platforms receive

  • Signup, qualified trial and demo booked as separate conversions
  • Paid plan or closed-won from Stripe or the CRM, with plan value or ACV
  • Click IDs carried from the marketing site into the app and CRM
  • Hashed work email where the privacy policy and consent allow it

What we never send

  • What users do or store inside the product
  • Company financials, contract terms or deal notes
  • Customer data the client processes on its own customers' behalf
  • Usage data from logged-in pages in URLs or event parameters

How we set it up

Step by step, in the client's own accounts.

Pricing

Qualified trials, demos and paid plans sent back from Stripe or the CRM are in Revenue Connected, $890 per client account. Starts with a free tracking check.

See full pricing
  1. 01Map the journeyAd click, marketing site, signup, app, billing and CRM, with every domain and tool in between.
  2. 02Keep the click ID through signupCross-domain tracking and hidden fields so gclid, fbclid and UTMs are saved on the user or contact record at signup.
  3. 03Define a qualified trialWith the client, agree what qualified means: a work email, an activation step, a team invite. One rule, written down.
  4. 04Separate trials from demosDistinct conversion actions, so reports and bidding can treat self-serve and sales-led differently.
  5. 05Connect Stripe or the CRMPaid plans from Stripe, or closed-won deals from HubSpot or Salesforce, sent to Google Ads and Meta by click ID.
  6. 06Set valuesFirst-year plan value or ACV for paid, and agreed example values for earlier stages, so bidding can weigh them.
  7. 07Test and documentTest signups and a test payment through the whole path, a test log, and a data spec for the client's team.

Outcomes

From signup to paid

Example stages. The client decides what counts as qualified and what each stage is worth, from its own conversion rates.

  1. Stage 1

    Signup

    Counted, but usually as a secondary conversion.

  2. Stage 2

    Qualified trial

    The trial meets the agreed rule, such as an activation step.

  3. Stage 3

    Demo held

    For sales-led deals, the meeting actually happened.

  4. Stage 4

    Paid

    First payment in Stripe or closed-won in the CRM, with plan value or ACV.

Platforms covered

Works with the client's existing stack.

  • Google Ads
  • Meta
  • LinkedIn Ads
  • GA4
  • Stripe
  • HubSpot
  • Salesforce
  • Segment
  • Mixpanel
  • Server-side GTM

Something else? Tell us which tools the client uses and we'll confirm before you pay.

What we do and don't claim

We don't promise more signups or lower acquisition costs. We send the outcomes the client defines, so bidding learns from customers instead of accounts. Which systems we can connect depends on the client's stack, and we confirm that before you pay.

SaaS tracking: questions

4 questions

Usually they stay as a secondary conversion for reporting, while bidding optimizes on qualified trials or paid. Low-volume accounts may need an earlier stage until there's enough data.

We send earlier stages, like qualified trial or demo held, that happen inside the window. Bidding learns from those while the deal is still open.

Those tools are for product decisions. Ad platforms only learn from conversions tied to a click. We connect the two where it helps, without sending in-app behaviour to ad platforms.

Yes, when the click ID or a matching identifier is saved with the customer at signup. We set that up first, then send payments back automatically.

Got a saas client whose numbers don't add up?

Send us one account. We review it for free and send a short video of what's working and what isn't.