Test whether your click IDs are arriving
Click one of your own live ads, copy the landing page URL, and paste it here. This tells you which of eight click identifiers arrived — and, more usefully, reminds you that the URL is only half the test. The identifier being in the address bar proves auto-tagging works. It proves nothing about whether it survived your forms and reached your CRM record, which is the part that actually fails.
Free30 minutesNo obligation
Test your click ID capture
Click one of your own live ads, copy the landing page URL, and paste it here. This tells you which click identifiers arrived — and, more usefully, reminds you that the URL is only half the test. The identifier being in the address bar proves auto-tagging works; it proves nothing about whether it reached your CRM.
Paste the landing URL from a real ad click. Everything happens in your browser. Nothing is sent anywhere.
Click ID tester · what breaks
What this tool is for — Click ID tester
- 01
Offline import isn't matching
Usually because the ID never reached the record.
- 02
You're not sure auto-tagging is on
Across every account.
- 03
Your capture code only names gclid
And you want to see what else arrives.
Click ID tester · the fix
What you get out of it — Click ID tester
Which identifiers arrived
Across Google, Meta, TikTok, Microsoft, LinkedIn and Pinterest.
A note about gbraid and wbraid
The iOS parameters most capture code misses.
An honest reminder about the real test
Which happens in your CRM, not your address bar.
Click ID tester · architecture
Why capture is the easy half — Click ID tester
Auto-tagging works or it doesn't, and that's a checkbox. Persistence is where implementations actually fail, and it fails silently.
- 1
Multi-step forms drop the parameter
Captured on step one, gone by step three, unless it's deliberately carried as a hidden field.
- 2
Iframes can't see the parent URL
A form inside an iframe never sees the query string your ad click arrived with.
- 3
Redirects strip query strings
Shorteners and login bounces do it routinely, and testing a clean path won't reveal it.
- 4
CRM lead conversion drops unmapped fields
The value is on Lead, nothing carries it to Opportunity, and no error is raised.
Click ID tester · diagnose
What this tool cannot tell you — Click ID tester
Stated up front, because a tool that implies more confidence than it has is worse than no tool. These are checks you have to run yourself.
- 01
Whether the ID reached your CRM
The check that matters. Submit a real lead through your full form and look at the record.
- 02
Whether your capture code handles all four Google parameters
It sees one click. Read the code.
- 03
Whether auto-tagging is on everywhere
One URL from one account proves one account.
- 04
Whether the ID is inside the import window
Google's offline import window is 90 days from the click.
Click ID tester · prove
How to confirm the result — Click ID tester
Against your own records, not against the tool's output.
Source of truth
your CRM records — the share carrying any click identifier
- Auto-tagging confirmed enabled on every ad account.
- All four Google parameters handled in your capture code, not just gclid.
- Identifier present on a live CRM record after a full multi-step journey.
- The share of records carrying an identifier measured rather than assumed.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked after your next site release, which is when most breaks happen.
Click ID tester · free audit
What we check in the free audit
- Whether the ID reached your CRM
- Whether your capture code handles all four Google parameters
- Whether auto-tagging is on everywhere
- Whether the ID is inside the import window
Checked against
your CRM records — the share carrying any click identifier
Free30 minutesNo obligation
Click ID tester · when not to buy
Why this isn't gated — Click ID tester
There's no email form in front of it, and that's deliberate.
- A tool you have to pay for with your contact details is a lead form wearing a costume. If this is useful, it should be useful without a transaction.
- Everything it does runs in your browser. There is no endpoint, so there is nothing for us to collect even if we wanted to — open your network tab and check.
- It will tell you when you don't have a problem. That outcome costs us a sale and happens regularly, which is the point of publishing it rather than putting it behind a call.
- If it does find something and you'd rather fix it yourself, the reference pages on this site cover the how. Hiring us is one option, not the conclusion.
Click ID tester · what we deliver
What it checks — Click ID tester
Eight click identifiers
gclid, gbraid, wbraid, fbclid, ttclid, msclkid and two more.
Google parameter coverage
Flags when only gclid is present as a prompt to check your capture code.
UTM conflict
Manual UTMs alongside a Google click ID, which can override attribution in some configurations.
The limits
Always states that URL presence isn't the test that matters.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
If the tool found something and you'd rather not fix it yourself: we repair the root cause in your existing setup and verify it on a live conversion.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Removes the class of failure rather than the instance. Money events from your own records through a first-party container on your subdomain.
- 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, with monitoring so the next break surfaces in days rather than at quarter end.
- 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
FAQ
Click ID tester questions, answered
Google click identifiers used for iOS traffic where gclid isn't available. Capture code naming only gclid loses a growing share, silently.
Auto-tagging is working. Whether the identifier survives your forms and reaches your CRM is a separate question and the one that usually fails.
No — a preview doesn't generate a real click identifier. It has to be a live click on a live ad.
The share of your CRM records that carry any click identifier. That's the ceiling on every offline conversion import you'll ever run.
Free · 30 min
Find out how many of your leads are attributable
WhatsAppFree30 minutesNo obligation
