LinkedIn Insight Tag Partner ID Finder – Where to Check Your Website Tag

Use our LinkedIn Insight Tag ID Finder to locate your Partner ID, verify tracking, and check if your LinkedIn tag is firing.

19 October 2026

Pixel Detection · LinkedIn Ads Partner ID · Insight Tag · Conversion Tracking

Quick Answer

  • LinkedIn Partner IDs are numeric values tied to Insight Tags.
  • Search website code for _linkedin_partner_id or pid=.
  • Do not confuse Partner ID with LinkedIn Conversion ID.
  • A tag found in source does not prove it fired in the browser.
  • Check the Partner ID again in Campaign Manager → Signals Manager.

A LinkedIn Insight Tag can be present on a website and still leave an advertiser with an important question: which LinkedIn ad account is this tag actually sending data to?

The answer usually starts with the Partner ID. It is the numeric identifier LinkedIn generates for an Insight Tag and uses to associate website signals with the appropriate LinkedIn advertising setup.

But a useful LinkedIn Insight Tag ID finder needs to go beyond finding one number. Modern implementations may load through Google Tag Manager, wait for consent, contain multiple Partner IDs, or use separate Conversion IDs for events. This guide shows how to tell those cases apart.

The Important Distinction

Finding a LinkedIn Partner ID tells you which Insight Tag is configured. It does not automatically tell you whether a lead, demo request, purchase, or signup conversion is being tracked correctly.

Partner ID verification and conversion-event verification are two different checks.

Three LinkedIn Signals Worth Checking Separately

A complete Insight Tag audit should distinguish configuration, browser activity, and conversion activity.

PID

Partner ID

Identifies the Insight Tag destination

collect

Runtime Request

Shows the browser attempted to send LinkedIn data

CID

Conversion ID

Identifies a specific event conversion

LinkedIn Tag Verification Map

Partner ID Campaign Manager Website Code Conversion ID Runtime Check GTM Multiple IDs Consent Mistakes FAQs

What Is a LinkedIn Insight Tag Partner ID?

When LinkedIn creates an Insight Tag, it generates a unique numeric Partner ID for that tag. The number connects signals coming from the website with the LinkedIn advertising setup using that Insight Tag.

Example Partner ID

1234567

Unlike some advertising pixels, the Partner ID does not need a platform prefix such as AW- or G-. It is normally a numeric value.

Where to Find Your Partner ID in LinkedIn Campaign Manager

The cleanest way to confirm that a website Partner ID belongs to your advertising setup is to compare it with the value LinkedIn shows inside Campaign Manager.

1

Open the correct ad account

Sign in to LinkedIn Campaign Manager and select the advertising account you want to verify.

2

Open Signals Manager

Use the Measure menu and open Signals Manager.

3

Open Insight Tag

Select your Insight Tag from the available signal sources.

4

Choose the tag-manager option

Open I will use a tag manager. LinkedIn displays the Partner ID so you can copy it and compare it with the website implementation.

Three Places a LinkedIn Partner ID Can Appear on a Website

Searching only one code pattern can miss an implementation. Check these three signals.

Location 1 · JavaScript Configuration

A traditional LinkedIn Insight Tag can expose the Partner ID in the page code.

_linkedin_partner_id = "1234567";

Location 2 · Partner ID Array

The same implementation can place the number inside LinkedIn's partner-ID array.

window._linkedin_data_partner_ids.push(_linkedin_partner_id);

Location 3 · LinkedIn Collection URL

A LinkedIn image or collection request can carry the Partner ID as the pid parameter.

https://px.ads.linkedin.com/collect/?pid=1234567&fmt=gif

Fastest First Check: Scan the Website with TagChief

If you do not want to search HTML manually, start with TagChief's LinkedIn Insight Tag checker.

TagChief analyses the publicly accessible page and looks for known LinkedIn tracking signatures and detectable pixel IDs. This makes it useful for a first-pass check on your own site, a client site, or another public landing page.

If the expected Partner ID is not visible, do not immediately conclude that the tag is absent. Tag managers, consent controls, conditional scripts, and runtime loading can require a browser-level check.

Partner ID vs LinkedIn Conversion ID

This is the distinction most likely to cause confusion during a LinkedIn conversion audit.

Identifier Example Purpose
Partner ID 1234567 Identifies the Insight Tag / signal destination
Conversion ID 15708492 Identifies a particular conversion event

For event-specific conversion tracking, LinkedIn can use a call similar to:

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

Practical rule: Partner ID answers “Which Insight Tag?” Conversion ID answers “Which specific conversion action?”

Installed, Firing, Active, and Converting Are Not the Same Thing

A common tracking mistake is treating all four states as equivalent.

Evidence What It Means What It Does Not Prove
Tag code found Insight Tag code is present Browser sent a LinkedIn request
Collection request observed Tag fired in that browser session A specific conversion fired
Source shown as Active LinkedIn has received signal from the website Every conversion action works correctly
Conversion event observed Specific event tracking fired LinkedIn ultimately attributed a campaign conversion

How to Verify the Partner ID at Runtime

If you need stronger evidence than a source-code search, use your browser's developer tools.

1

Open Developer Tools

Open the Network panel before loading the page you want to test.

2

Reload the page

Allow the page and its tag-management scripts to execute.

3

Filter for LinkedIn domains

Look for requests involving snap.licdn.com, px.ads.linkedin.com, or other LinkedIn tracking endpoints.

4

Inspect the pid value

When a LinkedIn collection request contains pid=, compare that Partner ID with the value from Campaign Manager.

Static Scan vs Runtime Check

Method Best For Main Limitation
TagChief scan Fast public tag and ID discovery Runtime-only tags may require browser testing
View Source Finding embedded scripts and numeric IDs Does not prove code executed
Browser Network Confirming requests actually leave the browser Only represents the tested session and consent state
Campaign Manager Confirming LinkedIn has received the source signal Active status alone does not test every conversion

Finding the Partner ID When LinkedIn Is Installed Through Google Tag Manager

A site can show a Google Tag Manager container in its raw HTML while keeping the LinkedIn Partner ID inside the published GTM configuration.

LinkedIn's current Google Tag Manager instructions use the LinkedIn InsightTag 2.0 template from the Community Template Gallery. The template contains a dedicated Partner ID field.

Current GTM Check

If you own the GTM container, inspect the LinkedIn InsightTag 2.0 tag and compare its Partner ID field with the Partner ID shown in LinkedIn Campaign Manager.

If you do not have GTM access, use runtime network requests instead. The browser can expose the Partner ID in LinkedIn requests even when the value was not present in the original HTML response.

What If You Find Multiple LinkedIn Partner IDs?

Multiple Partner IDs are possible. Do not automatically label them as duplicate-tag errors.

Old Implementation

A previous Insight Tag may remain after the business switches advertising setups.

Several Ad Setups

Different teams, brands, regions, or agencies may have introduced separate LinkedIn tags.

Intentional Multi-PID Setup

LinkedIn's current GTM template can accept more than one Partner ID.

Duplicate Deployment

The same tracking logic may have been installed directly and through a tag manager.

Record each distinct Partner ID, identify which account or tag it belongs to, and then determine whether every implementation is intentional.

A Shared Insight Tag Does Not Necessarily Mean Multiple Partner IDs

LinkedIn allows an Insight Tag to be shared across eligible ad accounts. This is useful when several accounts should use the same website signal source for conversion tracking or website retargeting.

For an auditor, that means account structure cannot always be inferred simply by counting Partner IDs. One shared Insight Tag may support more than one LinkedIn advertising workflow.

A LinkedIn tag checker can produce different results before and after a visitor makes a consent choice.

For example, a site's consent-management setup may allow the LinkedIn script to appear only after the visitor accepts advertising or marketing cookies.

Test State Possible Result What to Do
Before consent No LinkedIn request observed Record the initial state
After consent Insight Tag loads and sends pid Confirm expected consent behaviour

Do Not Test Only the Homepage

Competitor tag-checking workflows increasingly test several pages because one homepage cannot represent the entire B2B lead journey.

Landing Page

Does LinkedIn tracking load when paid traffic arrives?

Lead Form

Is the site-wide tag available when the visitor submits a lead?

Thank-You Page

Does the confirmation path load or trigger the intended conversion?

Booking Page

Does tracking survive when users move into scheduling or another domain?

Why “Active” in LinkedIn Is Not an Instant Test Result

After installation, LinkedIn checks whether the associated website loads and sends signal to the Insight Tag source.

LinkedIn notes that domain validation can take anywhere from a few minutes to 24 hours after the page is visited.

Audit implication: if a newly installed Partner ID is visible and a runtime request is firing, a temporarily inactive source status does not by itself prove the implementation failed.

Partner ID Is Not the Same as a LinkedIn Browser Identifier

The Partner ID identifies the Insight Tag destination. It should not be confused with browser-level identifiers or cookies LinkedIn may use as part of measurement.

LinkedIn currently recommends enabling enhanced conversion tracking where appropriate because first-party signals can improve conversion measurement and website-audience capture when browser restrictions reduce third-party cookie availability.

For a simple Partner ID audit, you do not need to decode those identity signals. The useful check is whether the expected PID is configured and whether the browser sends the expected LinkedIn request.

How to Verify an Event-Specific LinkedIn Conversion

After confirming the Partner ID, use a second workflow for the conversion itself.

1

Confirm the base Partner ID

Make sure website traffic is being sent through the expected Insight Tag.

2

Trigger the real action

Complete the demo request, signup, button click, download, or other action used for the conversion.

3

Look for the Conversion ID

Inspect event code or network activity for the Conversion ID associated with the intended action.

4

Match it with Campaign Manager

Verify that the observed Conversion ID belongs to the conversion action you intended to test.

One Limitation When Testing Buttons Inside Iframes

LinkedIn supports event-based tracking for actions such as button clicks. However, LinkedIn notes that buttons displayed inside iframes do not appear in its Website Actions list.

If a high-value demo, booking, or signup action happens inside an embedded third-party iframe, do not assume Website Actions will automatically surface that button. Test the conversion implementation separately.

Do Not Install the Insight Tag Everywhere Without Reviewing Page Content

LinkedIn requirement: LinkedIn warns advertisers not to place the Insight Tag on pages that collect or contain certain sensitive data. This can be especially relevant to consumer health and financial-service experiences.

A Better LinkedIn Insight Tag Audit Workflow

Stage Method Question Answered
1. Discovery TagChief Is a public LinkedIn tag or ID detectable?
2. Account Match Campaign Manager Does the PID match the expected Insight Tag?
3. Runtime Browser Network Did the browser actually send LinkedIn data?
4. Consent Test Before vs after consent Does tracking behave as intended?
5. Conversion Test Conversion ID Did the intended event-specific conversion fire?
6. Reporting Check LinkedIn Is LinkedIn receiving and processing the expected source?

Find the LinkedIn tag and Partner ID first

Use TagChief for a fast public scan, then move to runtime and conversion testing only when deeper verification is needed.

Check LinkedIn Tag →

Common LinkedIn Partner ID Finder Mistakes

Confusing Partner ID with Conversion ID

The Partner ID identifies the base Insight Tag. A Conversion ID identifies an event-specific conversion.

Stopping at snap.licdn.com

Finding LinkedIn's script proves the library is referenced, but you should still identify the PID and check runtime behaviour.

Assuming source code means firing

JavaScript can exist in the HTML without sending a request during the session you care about.

Ignoring consent

A tag may intentionally wait until the visitor provides the required marketing consent.

Testing only the homepage

B2B conversions often happen on forms, booking pages, thank-you pages, and embedded tools.

Treating Active as fully verified

An active source shows LinkedIn received signal. It does not confirm every conversion rule works.

Calling every extra PID a duplicate

Multiple Partner IDs can exist intentionally. Investigate ownership and purpose before removing anything.

LinkedIn Insight Tag Partner ID Audit Checklist

☐ Scan the public page with TagChief.

☐ Record every detected Partner ID.

☐ Search for _linkedin_partner_id.

☐ Search collection URLs for pid=.

☐ Compare PID with Campaign Manager.

☐ Check LinkedIn runtime requests.

☐ Test before and after consent.

☐ Review GTM InsightTag 2.0 if used.

☐ Separate Partner ID from Conversion ID.

☐ Test the actual conversion action.

☐ Test important pages, not only home.

☐ Confirm each additional PID is intentional.

Find the Partner ID before debugging the conversion

Start with TagChief to identify visible LinkedIn tracking signals, match the PID with Campaign Manager, and then test runtime behaviour and Conversion IDs when deeper validation is required.

Scan LinkedIn Insight Tag →

Frequently Asked Questions

What is a LinkedIn Insight Tag Partner ID?

It is the numeric identifier LinkedIn generates for an Insight Tag so website signals can be associated with that tag.

Where can I find the LinkedIn Partner ID?

Check Campaign Manager → Measure → Signals Manager → Insight Tag → I will use a tag manager.

How do I find a LinkedIn Partner ID in website code?

Search for _linkedin_partner_id and inspect LinkedIn collection URLs for a pid parameter.

Is Partner ID the same as Conversion ID?

No. Partner ID identifies the Insight Tag. Conversion ID identifies an event-specific conversion action.

What does pid mean in a LinkedIn tracking request?

The pid parameter contains the LinkedIn Partner ID associated with the tracking request.

Can a website have multiple LinkedIn Partner IDs?

Yes. Multiple implementations can be intentional or caused by separate teams, old tags, different accounts, or duplicate deployment.

Can GTM hide the LinkedIn Partner ID from page source?

Yes. The raw page can expose the GTM container while LinkedIn configuration loads dynamically from inside the container.

How do I know the Insight Tag actually fired?

Inspect browser network activity for LinkedIn tracking requests rather than relying only on code found in page source.

Why does the tag fire only after accepting cookies?

The site's consent-management configuration may delay advertising trackers until the visitor provides the required consent.

Does Active status prove conversions are working?

No. Active status confirms LinkedIn has received source signal. Individual conversion actions still need their own verification.

How long can LinkedIn tag validation take?

LinkedIn says domain validation can take from a few minutes up to 24 hours after the tagged page is visited.

Can TagChief find a LinkedIn Insight Tag?

Yes. TagChief scans public website HTML for known LinkedIn tracking signatures and detectable IDs. Runtime-only implementations may require an additional browser check.

← All posts