The LinkedIn Insight Tag sends a page view with the page address to LinkedIn as soon as its code runs, and LinkedIn's help pages describe no call that holds it. Website tracking complaints under the California Invasion of Privacy Act, CIPA, name it in 86 verified complaints in the 12 months to September 27, 2026. The hold that works is loading the tag only after accept.
What the LinkedIn Insight Tag sends before a visitor chooses
The LinkedIn Insight Tag is a script from LinkedIn that measures LinkedIn ads, builds audiences of site visitors to retarget, and reports conversions. LinkedIn's help center says it collects data about visits to the site, "including the URL, referrer, IP address, device and browser characteristics (User Agent), and timestamp".
It keeps identifiers on the visitor's browser as well:
- Cookies, which LinkedIn says "enable the collection of data" about visits. Its cookie table, last updated August 26, 2026, lists
li_fat_idon the site's own domain for 30 days, used for conversion tracking, retargeting and analytics. - The LinkedIn Ads ID,
li_adsid, a first-party identifier the tag generates for traffic from outside the EU, EEA, Quebec and the UK, kept in browser storage for six months. - Website Actions, which, per LinkedIn's Website Actions page, "automatically collects and tags all the actions" on the site: button clicks, page visits and form submissions, with button text and page names.
- Enhanced matching, an optional add-on that sends an email address a visitor typed into a form, hashed on the website first.
LinkedIn says it removes direct identifiers within seven days and deletes the remaining pseudonymized data within 180 days. None of this is unusual for an ad tag. What a complaint describes is the order: a request to px.ads.linkedin.com leaving the browser before the visitor answered the banner. Suitcast's free scan records that sequence, with the second each request fired.
Why website tracking complaints name the LinkedIn Insight Tag
Website tracking complaints rest on two sections of the California Penal Code. Section 631(a) reaches anyone who, "willfully and without the consent of all parties to the communication", reads or attempts to learn the contents of a communication in transit. Section 638.51 bars installing or using a pen register without a court order, and section 638.50 defines one as a device or process that records routing and addressing information, "but not the contents of a communication". Section 637.2 allows the greater of five thousand dollars per violation or three times actual damages. All four were read on leginfo.legislature.ca.gov on September 27, 2026.
On Suitcast's tracker catalog, in the 12 months to September 27, 2026, the LinkedIn Insight Tag page counts 86 verified complaints naming it, fifth among the 43 scripts the scan checks, behind Google Analytics 4 with 163, the Google Ads tag with 158, the Meta Pixel with 138 and the TikTok Pixel with 116. The catalog rates it high risk. Medical and health providers account for 6 of the 86, more than any other industry.
LinkedIn's help pages add one more reason to look. LinkedIn says it also receives data from Microsoft's UET tag, which Suitcast tracks separately as the Microsoft Advertising UET tag, named in 47 complaints in the same window. A site that holds one and not the other still sends a page view to an ad network first.
Senate Bill 690, as enrolled, would let only the Attorney General sue over section 638.51 claims arising from a website or app, and leaves section 631 claims as they are. It was presented to the Governor on September 4, 2026, and leginfo showed no later action on September 27. Check its status again before relying on it, and if a letter has already arrived, the CIPA demand letter guide covers the first week.
LinkedIn's help pages describe no consent hold
The Meta Pixel and the TikTok Pixel each have a documented call that holds events until a visitor accepts. The LinkedIn Insight Tag help pages read on September 27, 2026 describe none. What they tell the advertiser instead is: "You are responsible for ensuring you've obtained any necessary permissions or consents from your users before sharing any data with a third-party, including with LinkedIn."
So the hold is structural: the tag's code does not reach the page until the visitor clicks accept. In Suitcast's test on September 27, 2026, on a local page in Chrome with a placeholder partner ID, the base code as LinkedIn publishes it made these requests before anything was clicked:
- Two script downloads from
snap.licdn.com. - A page view to
px.ads.linkedin.com/collect, carrying the page address and a LinkedIn Ads ID the tag had just written to the browser's storage. - A redirect through
www.linkedin.com/px/li_sync, then the page view again. - A Website Actions request to
px.ads.linkedin.com/wa/, carrying the page address and the page title.
The same code wrapped in a function that runs only on accept made no request to LinkedIn in eight seconds of waiting, and made the script download and the page view the moment accept was clicked. A browser's network panel shows both results, and so does Suitcast's scan, which lists any request to snap.licdn.com or px.ads.linkedin.com before a choice as the LinkedIn Insight Tag.
Two Campaign Manager settings look like privacy switches and are not holds. Enhanced conversion tracking decides whether the tag uses first-party cookies, and LinkedIn says it works "subject to user consent in countries where it is legally required", which the site has to provide. Disconnecting the UET tag changes which data LinkedIn counts, not what the page sends.
Where your tag lives decides how to hold it
Most small business sites add the tag through a tag manager or a platform setting, and each route has its own switch. The table follows each vendor's documentation as read on September 27, 2026.
| Where the tag was added | What the documentation says | How to hold it |
|---|---|---|
| Pasted into the site's code by hand | The base code loads the script and sends a page view at once | Remove it and load it through a consent tool that injects it on accept |
| Google Tag Manager, LinkedIn's template | A tag on "Not set" performs no additional consent checks | Require ad_storage for the tag, with a trigger after the choice |
| Google Tag Manager, custom HTML | Same as the template: no checks until one is set | Require ad_storage, or move it to LinkedIn's template and do the same |
| Shopify, custom pixel | The Permission setting decides whether a pixel needs customer permission | Set Permission to Required for marketing, and turn on the banner for US visitors |
| WordPress, a header or footer plugin | The plugin prints the code on every page | Load it through a consent plugin that blocks scripts until accept |
Read the table by the first column. LinkedIn's Tag Manager template, named LinkedIn InsightTag 2.0 in the Community Template Gallery, contains no consent check in its published code, so the container's consent setting is the only thing that holds it; the Tag Manager consent guide covers the default, the requirement and the trigger in order. On Shopify, the custom pixel page says that to request consent based on the Permission setting "you need to add a cookie banner to your store", and the Shopify banner guide shows why a US store has to add the United States to it. On WordPress, the WordPress cookie banner guide covers what a consent plugin blocks.
LinkedIn's help pages also say the tag should not be installed on pages that "collect or contain Sensitive Data", naming pages where people "manage their financial accounts and transactions or medical appointments". For a dental or medical practice that advertises on LinkedIn, the booking page is off limits under LinkedIn's own terms, whatever the banner says.
How to check whether your Insight Tag waits
Test the page a customer lands on, in this order, which is the same five-minute test the cookie banner guide walks through for every script:
- Open the page in a private window with the network panel recording, and type
linkedininto the filter box. - Do not touch the banner. A request to
px.ads.linkedin.com/collectis a page view already sent. LinkedIn's own troubleshooting page tells advertisers to filter the network tab forads.linkedin.comto confirm the tag works, so a working tag shows up there straight away. - Type
licdninto the filter as well. A download fromsnap.licdn.commeans the tag's code reached the page. - Click reject, reload, and look again. A request that still appears ignores the choice.
- Fix it where the tag lives, using the table above, and repeat steps 1 to 4.
A scan does the same across several pages. The card below comes from a Suitcast report on a reserved example address: an IT services firm whose tag, pasted into the site's footer, fired on three pages before any choice and kept firing after reject on the page where visitors book a call.
The scan logs every request from the moment a page starts loading until the network goes quiet or 8 seconds pass, without clicking anything, and matches each one against the 43 scripts in its catalog. It then presses reject when a banner offers it, never accept, and watches 3 more seconds. The methodology page sets out the rules.
Keeping the tag held after the next campaign
A LinkedIn tag rarely stays the way it was fixed. A new lead campaign adds an event-specific conversion, a marketing hire pastes a fresh copy of the base code into the footer, or an agency publishes a container where the tag is back on "Not set". Each of those puts a request to LinkedIn back in front of the banner, and nobody opens the network panel afterwards.
A free scan is one dated snapshot of 5 pages. Suitcast's Monitor plan scans up to 100 pages every week, keeps every report with its PDF, and sends a weekly email naming the scripts that are new, the fixes that did not hold, and the new filings that match the site by state, industry or script. It costs $39 a month or $390 a year, less than one hour of a privacy lawyer's time. A law firm running LinkedIn lead campaigns, or an IT services company retargeting site visitors, gets the same check every week without asking anyone. An agency that runs LinkedIn ads for its clients covers five sites on Pro for $79 a month or $790 a year, with its own name on each PDF, which the agency guide describes. The pricing page compares the plans.
Limitations
This guide quotes California Penal Code sections 631, 637.2, 638.50 and 638.51 and the enrolled text of Senate Bill 690 as published on leginfo.legislature.ca.gov, LinkedIn's Marketing Solutions help center and cookie table, LinkedIn's Tag Manager template code, and Google and Shopify documentation, all read on September 27, 2026. The test used a placeholder partner ID on a local page; a live tag with conversions or enhanced matching may make more requests. Vendors change their code and documentation without notice, and whether a given tag setup breaks CIPA is a question for a lawyer and a court, not a scan. Nothing here is legal advice; the not legal advice page says what a score and a count mean.
A scan sees only what leaves a visitor's browser. Conversions sent through LinkedIn's Conversions API go from the site's server to LinkedIn and are invisible to it. The complaint counts are verified federal filings plus state filings with a public source, and a case is linked to a script only when its complaint text names it, so 86 is a floor; the dataset explains how cases are counted.
Suitcast identifies risk indicators. It is not legal advice and does not determine compliance.
Last updated September 27, 2026.