The Insight Tag is a standard ad pixel: paste it in the page, it runs on load, contacts LinkedIn, and drops identifiers. There is no built-in wait-for-consent behavior — if you did not gate it, it fires with the page, on every page, for every visitor.
The short answer
It is easy to miss because it is quiet. There is no widget, no visible change, and B2B marketers usually install it once during a campaign launch and never look again. In our own scan of 3,891 small-business sites, the LinkedIn Insight Tag was firing before consent on 327 sites — fourth behind Google's ad tags, the Meta Pixel, and Microsoft Clarity.
The fix is the same shape as any other ad pixel: hold the tag until the visitor accepts advertising cookies, using either your consent platform's script blocking or a consent requirement on the GTM tag.
Fresh incognito window, DevTools → Network, filter on licdn, banner untouched. An ungated install loads snap.licdn.com/li.lms-analytics/insight.min.js with the page and then calls a collection endpoint on px.ads.linkedin.com carrying your partner ID. Application → Cookies shows LinkedIn identifiers such as li_sugr and, for visitors with a LinkedIn session, bcookie / lidc on the .linkedin.com domain.
The confirming evidence is in Campaign Manager: your website-demographics reporting shows traffic volumes that match your total sessions rather than your consented sessions.
Two minutes in the browser, three in Tag Manager. You are establishing one fact: does anything reach LinkedIn before the visitor answers the banner?
licdn. If insight.min.js appears, the script loaded pre-consent. Filter for px.ads.linkedin.com — that is the request that actually reports the visit.collect request and look at the query string: pid is your partner ID, and the referrer and page URL travel with it. That is what was transmitted before anyone agreed to anything.li_sugr on your domain and LinkedIn cookies on .linkedin.com._linkedin_partner_id, then check your GTM container for a LinkedIn tag, and check any marketing plugin or site-builder integration that offers a one-click LinkedIn pixel. Duplicate installs are common — one gated, one forgotten.What a healthy result looks like: A gated install shows nothing on licdn.com or ads.linkedin.com until you click Accept, and then shows both.
LinkedIn's install instructions produce a raw script block with _linkedin_partner_id that goes straight into the site's header. Raw snippets execute as written, before any consent tool can intervene, unless the CMP explicitly rewrites the tag.
Installed via Tag Manager on an All Pages trigger with the default "no additional consent required", the tag fires the moment the container loads.
Auto-blocking works from a recognition list. snap.licdn.com and px.ads.linkedin.com are sometimes missing or uncategorized, and many platforms default unknown scripts to allowed.
The Insight Tag and its conversion events are often installed by different people at different times — the base tag by an agency at campaign launch, event tracking by whoever built the demo-request form. Gating one does not gate the other.
California's Invasion of Privacy Act (CIPA), Penal Code § 631, prohibits intercepting a communication without the consent of all parties. Since 2022, plaintiff firms have applied that decades-old wiretapping statute to websites — arguing that transmitting a visitor's page views and professional-audience signals to LinkedIn for ad targeting before the visitor consents is an intercepted communication. Statutory damages under § 637.2 run up to $5,000 per violation, and plaintiffs argue each affected visitor session is a separate count, which is why even small sites receive demand letters. Similar all-party-consent statutes in Pennsylvania (WESCA), Florida (FSCA), and Massachusetts have produced parallel filings.
B2B sites sometimes assume the litigation wave is a consumer-retail problem. It is not: the claims turn on whether a third party received the contents of a visitor's interaction before consent, and a B2B visitor is as much a California resident as a retail shopper.
To be precise about what a network log can tell you: a tracker firing before consent is a technical finding — it establishes when a script transmitted data, not whether any law was broken. But timing is exactly what these claims are built on, which is why fixing the timing is the practical response.
Terminology bridge
LinkedIn's documentation calls this the Insight Tag; the number in the snippet is your partner ID, and the reporting it powers is website demographics and conversion tracking. In consent language, an ad pixel belongs to the advertising / targeting category, and holding it until opt-in is prior blocking. When it fires anyway, the pattern is a consent gap: the window between page load and the visitor's answer, during which a third party already has the data.
A scan records that a request went to LinkedIn and when. It does not tell you what LinkedIn does with it, whether any specific visitor was a California resident, or whether a court would treat any of it as a violation — those are legal and factual questions well outside what a network log can answer. What the log settles is the timing, and timing is the part you control.
RegSentry loads your site in a real browser, records when each third-party tracker first contacts its server, and flags everything that fires before consent — with the fix for each one. Continuous monitoring re-runs it and emails you when something new appears.
Free real-browser scan
See every pre-consent tracker on your site — free, 30 seconds, no signup.
Real browser scan, no signup to run it. You see a summary of the findings; the full report with every tracker unlocks with your email.