Skip to main content
custom SaaS + GooglePlatform solution

Google Ads and GA4 tracking for custom SaaS

With full control, the Google side becomes a design question rather than a technical one: which milestone is the bidable conversion, given that it has to sit inside the import window and produce enough volume for Smart Bidding to learn from.

Free30 minutesNo obligation

custom SaaS + Google · what breaks

What goes wrong on custom SaaS

  1. 01

    Nothing exists unless specified

    No theme, no plugin, no defaults. An unspecified event doesn't fire.

  2. 02

    The click ID stored in a cookie

    Which is long gone by the time the card is charged.

  3. 03

    Conversions weeks past the click

    Straining every import window.

  4. 04

    Signups optimized instead of revenue

    Because signups are the only thing anyone wired.

custom SaaS + Google · the fix

What changes — custom SaaS + Google

  • 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 + Google · architecture

How the Google destinations behave on custom SaaS

A design question rather than a technical one.

  1. 1

    Measure median click-to-payment

    Against the 90-day import window.

  2. 2

    Pick the bidable milestone from that

    Activation if payment is too slow or too sparse.

  3. 3

    All four click parameters captured

    At landing, before signup.

  4. 4

    Real amounts, not projections

    Each payment as it clears.

  5. 5

    Counting set to every

    Recurring payments are recurring conversions.

custom SaaS + Google · 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.

  1. 01

    Check what share of accounts carry a click ID

    The ceiling on everything.

  2. 02

    Check where it's stored

    A cookie won't survive to first payment.

  3. 03

    Measure median click-to-payment

    Against the import window.

  4. 04

    List which lifecycle events are actually emitted

    Usually signup and nothing else.

  5. 05

    Compare channel rank by signup and by revenue

    The gap is the value of doing this.

custom SaaS + Google · prove

The QA evidence — custom SaaS + Google

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 + Google · 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

Get my free conversion tracking audit

Free30 minutesNo obligation

custom SaaS + Google · 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 + Google · what we deliver

What gets built for Google on custom SaaS

  • GA4 ecommerce events in the recommended shape

    Correct names, transaction_id present, currency per order, an items array that agrees with the value.

  • Click identifiers captured and persisted

    gclid, gbraid and wbraid — not just the first, because iOS traffic arrives with the others.

  • Enhanced Conversions from the data layer

    Not from CSS selectors, which break on every redesign silently.

  • Conversion action settings reviewed

    Counting, primary status and attribution window — free to change and more consequential than most tag work.

Written guarantee

95%+ tracking accuracy

Measured against your own billing and account records. 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 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
Fix what I have

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
Rebuild it server-side

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

FAQ

custom SaaS + Google questions, answered

Measure median click-to-payment. If it's inside 90 days with enough volume, use first payment. If not, move upstream to activation.

Free · 30 min

Get Google Ads and GA4 right on custom SaaS

Free30 minutesNo obligation