LinkedIn Insight Tag Not Working? Fix Unverified Status

The LinkedIn Insight Tag is a small script that runs on every page of your site. It powers conversion tracking, website retargeting and website demographics in Campaign Manager. When it isn't working, you usually see one of two things. Either the tag shows "Unverified" in Campaign Manager, or the tag is active but conversions stay at zero.

This guide covers both, starting with the most common causes.

First, understand the tag status

LinkedIn shows the Insight Tag's status in Campaign Manager. At the time of writing, you find it by opening your ad account, clicking Measure in the left menu, then Signals manager and the Insight Tag. LinkedIn moves menus from time to time, so look for "Signals manager" or "Insight Tag" if the path differs. The statuses mean:

Status	Meaning
Active	A signal was received in the past seven days
No recent activity	The last signal was more than seven days ago
Unverified	No signal has ever been received

"Unverified" right after installation is normal. The status only changes after someone visits a page with the tag, and LinkedIn says it can take up to 24 hours to switch to Active. Visit a tagged page yourself, then check again the next day. LinkedIn's status definitions are in its article on Insight Tag source status.

Step 1: Check the partner ID

The Insight Tag identifies your account with a partner ID near the top of the snippet:

_linkedin_partner_id = "1234567";
window._linkedin_data_partner_ids = window._linkedin_data_partner_ids || [];
window._linkedin_data_partner_ids.push(_linkedin_partner_id);

If you manage several ad accounts, this is the most common problem. LinkedIn says that if the partner ID on your page doesn't match the partner ID in your account, your conversions won't collect a signal. The tag can be running perfectly and still report to a different account.

Compare the number in your site's code with the partner ID shown in the Insight Tag section of the ad account you advertise from. If they differ, replace the snippet with the one from the correct account.

Step 2: Check that the code wasn't changed

LinkedIn says to place the JavaScript on the page exactly as you copied it from Campaign Manager, because edited code often causes problems. Two issues come up again and again:

• Curly quotes. Copying the snippet through an email, document or chat tool can turn straight quotes into curly ones. The browser can't run JavaScript with curly quotes, and the console shows a syntax error.
• A partial paste. Some site builders cut off long snippets or strip <script> tags. View the page source and confirm the whole snippet is there, including the script that loads insight.min.js.

The tag should go on every page, usually just before the closing </body> tag or in your site's global footer.

Step 3: Check blocked domains, CSP and ad blockers

The tag loads its script from snap.licdn.com and sends data to px.ads.linkedin.com. LinkedIn's troubleshooting guide says to make sure neither is blocked.

• Content Security Policy. If your site sends a CSP header, the console shows "Refused to load" or "Refused to connect" for a blocked LinkedIn domain. Add the domains to the matching directives. See CSP blocking pixels.
• Ad blockers and privacy extensions. These often block LinkedIn's tag. Test in a private window with extensions disabled. Otherwise you may see a broken tag on your machine that works for most visitors.
• Corporate networks. Some company firewalls and DNS filters block ad domains. If you test from an office network, try from another connection too.

Step 4: Check consent settings

If your site uses a cookie consent tool, the Insight Tag may be held until the visitor accepts marketing or advertising cookies. LinkedIn states that opt-in consent is required from residents of the EU, EEA and Switzerland for targeting based on third-party data, and that each publisher is responsible for its own GDPR compliance.

When you test, use a fresh private window and accept all cookies. If the tag fires only after you accept, it's working as intended. If it never fires, check that LinkedIn is assigned to a consent category the visitor can actually accept. Also check that your consent tool isn't blocking the script even after consent is given.

Step 5: Check your tag manager setup

If you deploy the tag through Google Tag Manager or another tag manager, LinkedIn recommends using its official integration for that tool. For GTM, that's LinkedIn's Insight Tag template. Then check:

• The tag fires on all pages, not only on a single trigger.
• The container version with the tag is published, not just saved in a workspace.
• The partner ID field in the template holds the right ID.

GTM's Preview mode shows whether the tag fired on each page. If Preview won't connect, see GTM Preview mode not working.

Step 6: Fix conversions that won't track

If the tag is Active but a conversion shows zero or stays Unverified, the problem is the conversion setup. Conversions have their own status. In Campaign Manager, open Measure and then Conversion tracking. Find the conversion and open its settings. LinkedIn's guide to troubleshooting Insight Tag conversions covers each method.

Page-load conversions (URL rules)

These count a conversion when someone loads a URL that matches your rule. Most failures come from a rule that doesn't match the real URL. Examples are a rule for /thank-you when the page is /checkout/thank_you, or an "exact match" rule when the URL carries an order number or query string. Load the real confirmation page and compare its URL with the rule, character by character.

Event-specific conversions

These fire when your code calls lintrk with the conversion's ID, for example on a button click or form submission:

window.lintrk('track', { conversion_id: 12345678 });

Check that the conversion_id matches the conversion in Campaign Manager. Check that the call runs after the Insight Tag base code. Also check that it runs when the action actually succeeds. A call on a form's submit button fires even when validation fails. A call placed after a redirect may never run.

Campaign association

A conversion only appears in campaign reporting if it's associated with the campaigns you're looking at. Open the conversion's settings and review the campaign section. A conversion created after a campaign launched isn't always added to it.

Step 7: Deduplicate with the Conversions API

If you also send conversions through LinkedIn's Conversions API, you need a shared event ID so a conversion isn't counted twice. LinkedIn's developer documentation describes this setup:

• Create a conversion rule for each data source: one for the Insight Tag, one for the Conversions API.
• For event-specific conversions, pass an event_id with the lintrk call, for example window.lintrk('track', { conversion_id: 12345678, event_id: 'order_100457' }).
• For page-load conversions, set window._linkedin_event_id before the Insight Tag base code runs.
• Send the same ID as the event ID in the matching Conversions API event.

When both arrive with the same ID, LinkedIn keeps the Insight Tag copy and discards the API copy. In reporting, you see both conversions in the breakdown. When deduplication works, the Insight Tag conversion usually has the higher count.

How to verify the fix

1. Network tab. Open a tagged page with developer tools open. Filter the Network tab for ads.linkedin.com. LinkedIn says these requests should return status code 302. A blocked or missing request means the tag isn't sending.
2. A browser extension. The Pixel Helper extension is one way to see which pixels and events fire on a page, including the LinkedIn tag and any lintrk calls.
3. Tag status. After a visit, check that the Insight Tag shows Active within 24 hours.
4. Conversion status. Complete the conversion action yourself, then check that the conversion moves to Active. LinkedIn suggests contacting its support if a conversion is still Unverified after 24 hours while the code is visibly on the page.

For a general method that works across platforms, see how to check pixels on any website.

FAQ

How long does it take for the Insight Tag to verify?

The status changes after the tag receives its first signal, which needs a visit to a tagged page. LinkedIn says this can take up to 24 hours after the visit.

Why did my tag change from Active to "No recent activity"?

LinkedIn hasn't received a signal in more than seven days. The tag was usually removed or broken by a site redesign, a theme change, a new consent tool or a CSP change. Check the page source first.

Can I use one Insight Tag for several ad accounts?

The tag reports to the partner ID in its code. If you use several ad accounts, the tag on the site must match the account where you want the data. Check how your accounts share the tag in Campaign Manager before you install a second one.

Why is my conversion count lower than my form submissions?

LinkedIn only counts conversions it can attribute to LinkedIn ad interactions within your attribution window. Visitors who block the tag or decline consent aren't counted either. Adding the Conversions API recovers some of these events.