Free LinkedIn Insight Tag Checker
Check whether your website sends LinkedIn tracking requests. Scan up to four pages in a real browser and see what changes after accepting a supported cookie banner.
Installed and firing are different things.
A snippet in your source proves neither. This reports what was observed leaving the browser, and states plainly what it did not test.
- Whether the Insight Tag script loads
- Whether a collection request is sent, and answered
- Partner IDs observed on the wire, per page
- Whether the tag waits on a consent banner
- LinkedIn cookies created, and when
Free scan and downloadable report. No email or installation. An independent tool by WonLoop; not affiliated with LinkedIn.
Which pages should we check?
Add at least one public URL. Include your form, thank-you or booking page to check the places where visitors become leads. The scan opens pages; it does not submit forms.
Homepage only is a valid scan. It just answers a smaller question.
Free scan and downloadable report. No email required.
Your URLs are held for one hour to run the scan, then discarded. We log the domain and the outcome, nothing else. No IP, no email required to see results.
Findings
Nothing has been scanned, so nothing here is a finding about your site.
See a real LinkedIn tag check
We scanned WonLoop’s homepage and tracking-review page on 10 September 2026 at 04:35 UTC. Both loaded. No Insight Tag script or LinkedIn collection request was observed on either visit.
This is a dated example from our own site, not a client result or a scan of your website. No recognised consent banner appeared, so an acceptance comparison was not performed.
What the report tells you
- Script loaded
- The browser requested the Insight Tag library.
- Request observed
- A tracking request was sent. Its response is reported separately.
- Partner ID
- The ID observed in the request. Compare it with your account.
- After acceptance only
- A request appeared only during the separate acceptance visit.
These are explanations of possible results. An observed request does not prove that Campaign Manager attributed a conversion.
Compare CPA with CRM cost per lead
Use the same date range and lead definition for all four numbers. 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.
Enter both counts for the same period and lead definition. A difference between totals does not establish tracking loss.
Both figures are arithmetic on your inputs, labelled an estimate. The scan above watches one visit per page, 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
Is this a LinkedIn pixel checker?
Yes. The LinkedIn Insight Tag is often called the LinkedIn pixel. This checker looks for its script, tracking requests, partner IDs and cookies during page visits. You do not need an extension or access to Campaign Manager to run the scan.
How do I check whether my Insight Tag is firing?
Add a public page URL and select Scan my pages. Open the page’s findings to inspect the script request, collection request and response. If your conversion requires a click or form submission, test that action separately. LinkedIn’s troubleshooting guidance explains how to inspect the tag manually.
What if the LinkedIn Insight Tag is not detected?
Check the page URL, intended tag coverage and consent result first. A tag may load on another page or wait for an action this scan does not perform. Review the installation and reproduce the visit in your browser before changing the tag.
Why are conversions missing when the tag is detected?
Loading the base tag does not establish that a particular conversion action occurred or was attributed. Check the conversion rule, the action that triggers it and the associated campaigns in Campaign Manager. See LinkedIn’s conversion troubleshooting guide.
What can the scan actually see?
Each URL is opened in a real browser with no stored cookies, and every request the page makes is recorded. That shows whether the Insight Tag script loaded, whether a collection request went to LinkedIn, whether a response came back, which partner IDs were on those requests, and which LinkedIn cookies were created. Where a consent banner we recognise appears, a second, separate visit accepts it and the two are compared.
Can I just scan my homepage?
You can, and the findings will say they cover only the page they read. A homepage tag tells you something fires 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 an observed request mean my tracking is fine?
No. It means the browser attempted to send data during that visit. Responses are reported separately. It does not mean Campaign Manager attributed a conversion, and it says nothing about events that fire when a form is submitted rather than when a page loads — the scan visits pages, it does not fill anything in. Whether your reporting matches reality still needs Campaign Manager and your CRM side by side.
Why does a consent result never say I’m compliant?
Because we only test the accept path. We load the page once without touching the banner, then again accepting it, and report what differed. We never click decline, so we make no claim about what happens when a visitor refuses — and none of it is legal advice. Banners are also frequently shown by region, so one that does not appear for our scanner may still appear for your visitors.
Do you store the URLs or email me the results?
Your URLs are held for one hour so the scan can run, then discarded. What we keep is the domain and the outcome of each check — no IP, no full addresses, and no cookie values, ever. No email is required to see results. Download the report after your scan, or book a tracking review to discuss the findings.
Why does the estimator need my CRM number?
The CRM count lets you compare cost per lead with Campaign Manager cost per conversion. Use the same dates and lead definition. Leave it blank and the comparison stays empty; a difference between totals alone does not prove tracking loss.
Take the findings into your tracking review
The scan shows browser activity. A review connects that evidence to Campaign Manager and your CRM.
A scan that observes every request still only describes the conditions we tested: one browser, no ad blocker, no stored history, no form submitted. It cannot tell you how many real events never arrived. That number comes from comparing what Campaign Manager recorded against what your CRM holds, which is the twenty-minute check, not this page.
Opening your pages in a real browser
As a first-time visitor, with no stored cookies and nothing filled in. Every request each page makes is recorded.
This closes itself when the scan finishes. Close it now to watch the pages fill in behind.