Signal CheckerFind out what LinkedIn can actually see.
Every other free tool grades your LinkedIn campaigns or confirms a tag exists. This one checks the signal itself: whether the LinkedIn Insight Tag reaches the pages where conversions actually happen, whether more than one partner ID is firing, whether a consent banner gates it, and what the gap between Campaign Manager and your CRM is costing you.
It reads page source, and only page source.
It cannot see what the browser blocks, and it says so rather than guessing.
- Insight Tag presence, per URL
- Coverage on form, thank-you and booking pages
- Conflicting partner IDs
- Consent-gated tag loading
- The reported-versus-true CPA gap
No account, no login, no email. The scan requests each page the way a visitor’s browser would and reads what comes back.
The conversion URLs are the product
A tag on your homepage proves nothing. The pages that matter are the ones where a visitor becomes a lead. Give us those and the scan can tell you whether LinkedIn ever sees the event.
Homepage only is a valid scan. It just answers a smaller question.
We log the domain checked, nothing else. No IP, no email required to see results.
Findings
Source scan · not run yetno URLs supplied — nothing scanned
Your CPA isn’t your CPA
Four numbers from Campaign Manager and your CRM. The arithmetic runs in your browser and nothing is sent anywhere.
Enter monthly clicks and conversions to see the rate the guarantee is measured in.
Without a CRM number we will not invent one for your account. This is the published range for browser-pixel-only setups; the twenty-minute check replaces it with your figure.
Both figures are arithmetic on your inputs, labelled an estimate. The scan cannot see events the browser blocked, so a real baseline still has to be exported from Campaign Manager.
Enter spend and both conversion counts to see the two CPAs side by side.
Questions about the scan
What can the scan actually see?
Page source and any tag manager container it can read: the Insight Tag snippet, partner IDs, and whether the tag sits behind a consent condition. It does not run your JavaScript, so a single-page app or a tag injected after interaction returns inconclusive rather than a failure.
Can I just scan my homepage?
You can, and the verdict will say it covers only the page it read. A homepage tag tells you the snippet is installed somewhere; it cannot tell you whether the event fires where a visitor becomes a lead. The form, thank-you and booking pages are the ones that decide what LinkedIn optimizes toward.
Does a clean result mean my tracking is fine?
No. It means the browser-side setup looks intact. Everything this tool checks happens in the browser, and the browser is exactly where events go missing. A clean scan and a broken measurement layer are entirely compatible.
Do you store the URLs or email me the results?
We log the domain checked, nothing else. No IP, and no email required to see results. If you want the findings written up, email [email protected] — nothing on this page asks for an address first.
Why does the estimator need my CRM number?
Because the gap is the whole point, and only your CRM knows how many of those conversions were real leads. Leave it blank and you get the published loss band instead of a number about your account — which is honest, but far less useful.
This tool cannot see the thing that costs you the most
Every check on this page runs in the browser. So does every event you are losing.
A perfect scan tells you the tag is installed correctly. It cannot tell you how many events never arrived — nothing running in the browser can. That number comes from comparing what Campaign Manager recorded against what your CRM holds, which is the twenty-minute check, not this page.