Use Cases / Lead-tracking break

GA4 · QA

Catch a lead-tracking break before it costs a week of ad spend.

The tracking didn't error. It just stopped counting — and the media team kept optimising toward a number that was now a lie.

The situation

What actually happens

  • A brand ships a redesigned enquiry form on a Tuesday.
  • The new form doesn't record the conversion the way the old one did.
  • GA4 keeps reporting — just fewer leads. No alert. The daily number looks like normal variance.
  • Paid Search keeps bidding to a signal that's now under-counting by 60%.
  • Nine days later the client asks why cost-per-lead doubled. Now it's a fire.

With ODDVX

The same week, instead

The overnight check runs

ODDVX watches every brand's lead and purchase events against their own history. This one normally fires many times a day, so a single quiet day is already a red flag.

You get the alert Wednesday morning

Ranked most-urgent first, with a plain-English reason and a file you can forward straight into the client thread.

A test confirms the cause

Point ODDVX at the live form. It submits a test enquiry and reports the conversion failed — so you know it's the site, not the analytics config.

Dev fixes it, you re-run

Same test, clean pass, confirmation page included. Sign-off in an hour — not a post-mortem in a fortnight.

What it uses

Stop finding out from the client.