Lead generation tracking QA checklist
Lead tracking fails differently from ecommerce. There's no order record to reconcile against, forms submit over AJAX so a thank-you-page trigger never fires, and the click ID has to survive multi-step forms to be worth anything later. This checklist targets those specific failures in order: does the event fire at all, does the click ID reach the CRM, and does the lead count survive comparison against records that have had spam removed.
Free30 minutesNo obligation
Lead gen QA · what breaks
Where teams get this wrong — Lead gen QA
- 01
A conversion trigger bound to a thank-you page URL
AJAX forms never navigate, so it can never fire.
- 02
No click ID on the CRM record
Which is the ceiling on every offline conversion import you'll ever run.
- 03
Counting spam as leads
It inflates the number you report and destroys trust the moment the client checks.
Lead gen QA · the fix
What a correct implementation looks like — Lead gen QA
The event bound to the form's real success state
Not to a navigation that may not happen.
Click ID captured and written to the CRM
All four parameters.
Forms distinguishable from each other
A newsletter signup is not a demo request.
Spam and duplicates quantified
Rather than argued about.
Lead gen QA · architecture
The checks, in order of consequence — Lead gen QA
Lead-specific failures, ordered by how much they cost. The first two account for most of what we find.
- 1
The event fires on real submission success
Bound to the form's success callback or state, not to a navigation.
- 2
The click ID reaches the CRM
gclid, gbraid, wbraid and fbclid, captured on landing and persisted through every step.
- 3
Forms are separately identified
So a newsletter signup and a demo request aren't one conversion.
- 4
Error states produce nothing
A failed submission is not a lead.
- 5
Duplicate submissions are handled
A refresh or a double-click shouldn't count twice.
- 6
The count reconciles against CRM records
After spam and duplicates are removed and quantified.
Lead gen QA · diagnose
Common mistakes and how to validate each — Lead gen QA
Ordered by how often we find them. Each one has a specific check rather than a general instruction to be careful.
- 01
Trigger waiting for a thank-you page
Submit the form and watch the URL. Modern site builders submit over AJAX and never navigate.
- 02
Click ID lost between form steps
Complete every step of a multi-step form from a tagged click and check the final record.
- 03
Hidden field present but never populated
The field existing isn't the same as it having a value. Check the submitted data.
- 04
All forms counted as one conversion
Look at your conversion data and see whether you can tell them apart. Usually not.
- 05
Spam included in reported volume
Compare submissions against CRM records after filtering. The gap is usually larger than expected.
Lead gen QA · prove
How to prove your implementation is right — Lead gen QA
Against your own records and a live payload, not against a preview screen.
Source of truth
your CRM records, matched on a shared lead ID
- A live test lead followed from ad click to CRM record.
- All four click parameters present on that record.
- Each form separately identifiable in the event data.
- Submissions reconciled against CRM records for a closed month, with spam quantified.
- Checked on a live conversion, not in preview mode.
- Reconciled over a fully closed window, matched per record.
- Re-checked 30 days later.
Lead gen QA · free audit
What we check in the free audit
- Trigger waiting for a thank-you page
- Click ID lost between form steps
- Hidden field present but never populated
- All forms counted as one conversion
- Spam included in reported volume
Checked against
your CRM records, matched on a shared lead ID
Free30 minutesNo obligation
Lead gen QA · when not to buy
What this reference deliberately leaves out — Lead gen QA
Stated openly, because a reference that's silent about its own gaps is the dangerous kind.
- Call tracking has its own checklist, because phone leads fail differently from form leads.
- CRM-specific field mapping — particularly lead conversion behaviour — is covered on the offline conversion schema page.
- Chat and messaging conversions aren't covered here and are a common blind spot worth auditing separately.
- Vendor documentation is the authority, not this page. Where the two disagree, the vendor is right and we'd like to know so we can correct it.
- Parameter names and behaviour change. Anything here is accurate as we last verified it; verify against the current documentation before you rely on it for a build.
Lead gen QA · what we deliver
The checklist — Lead gen QA
Submit a real lead and watch for a page change
If there isn't one, a URL-based trigger can never fire.
Check the click ID reached the CRM record
After a full multi-step journey, not step one.
Confirm each form is separately identifiable
In the event data.
Test the error state
A failed submission must not count as a lead.
Reconcile a closed month against CRM records
After classified spam and duplicate removal.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies your existing browser-side setup against this reference, on a live conversion.
- Implementation checked against the spec
- Verified on a live conversion
- Reconciled against your own records
- Written handover
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, built to this specification.
- First-party server container on your own subdomain
- 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
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, documented to this standard.
- 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 so the next break surfaces in days
FAQ
Lead gen QA questions, answered
Most often the trigger waits for a thank-you page and the form submits over AJAX. Bind it to the form's actual success state instead.
No. The CRM removes spam and duplicates that were correctly counted as submissions. Quantify that gap rather than trying to close it.
Whether the click ID reaches the CRM record. That number is the ceiling on every offline conversion import you'll ever run.
Yes. A failed submission firing a conversion is a real and easily missed fault, especially on forms with server-side validation.
Free · 30 min
Follow one real lead all the way through
WhatsAppFree30 minutesNo obligation
