Ads and pixels

LinkedIn Insight Tag

Configure the LinkedIn Insight Tag

Copy the partner ID from LinkedIn Campaign Manager under Data, Signals manager, Insight Tag. Remove the original Insight Tag snippet and its <noscript> tracking image.

npm install @c15t/integrations@alpha

src/consent-scripts.ts

import { linkedinInsights } from '@c15t/integrations/linkedin-insights';

export const scripts = [linkedinInsights({ id: 'YOUR_PARTNER_ID' })];

Register the scripts

Complete your framework quickstart first. Keep its Inth endpoint, policy, styles and consent UI. Remove the vendor's original script, SDK initializer or tag-manager entry, so the vendor loads only through c15t.

The vendor pages put the helper in src/consent-scripts.ts. If your framework quickstart already has a scripts array, such as the one in c15t.config.ts in the Next.js guide, add the helper to that array instead of creating a second file. The scripts export is a configuration, not an initializer. Add it to the c15t provider you already have, at the registration point for your framework below. These are edits to that provider, not a second provider.

Add the configuration to scripts in c15t.config.ts, next to next.config.ts:

import { defineConsentConfig } from 'c15t/next';
import { scripts } from './src/consent-scripts';

export default defineConsentConfig({ scripts });

Keep the rest of your config, such as mode and routePrefix, in the same call. ConsentRoot reads the config in the browser, so the layout keeps passing only state. App Router, Pages Router and static export all read the same file. See Next.js scripts and embeds.

Options

Option	Default	Behavior
`id`	Required	Partner ID. The helper trims it, sets it as `_linkedin_partner_id` and appends it to `_linkedin_data_partner_ids`. Empty or whitespace-only values log an error and the script does not load.
`scriptSrc`	`https://snap.licdn.com/li.lms-analytics/insight.min.js`	Loader URL override. A blank value falls back to the default.

Loading and revocation

linkedinInsights uses the marketing category. Before marketing is allowed, c15t sets no LinkedIn globals and loads nothing from LinkedIn. When marketing becomes allowed, the helper sets the partner ID globals, defines the lintrk queue, then loads insight.min.js.

On revocation the helper removes the script element and calls no LinkedIn API, so the page reload is what stops the tag. window.lintrk stays defined until then.

Guard your own lintrk calls

The Insight Tag tracks page views itself. Conversions your code sends through lintrk('track', ...) need their own check, because window.lintrk still exists after revocation. Check the permission first, then that the tag is set up:

src/track-signup.ts

export function trackSignup(marketingAllowed: boolean) {
	if (!marketingAllowed || typeof window.lintrk !== 'function') return;
	window.lintrk('track', { conversion_id: 1234567 });
}

Pass the current marketing permission from your framework, for example useConsent('marketing') in React. Use the conversion ID from your LinkedIn conversion. @c15t/integrations/linkedin-insights exports no event wrapper.

Verify the LinkedIn Insight Tag

After you allow marketing, insight.min.js loads from snap.licdn.com, and window._linkedin_data_partner_ids in the console contains your partner ID. Trigger one guarded conversion and check that its request to LinkedIn appears. Then revoke marketing. Until the page reloads, calling trackSignup sends nothing.

Test in a private window with an opt-in policy. Open DevTools Network, disable the cache and filter by the vendor's domain:

Load the page. No request goes to the vendor before you choose.
Click Reject, then reload. There is still no vendor request.
Open Privacy settings and allow the helper's category. The vendor script loads without a page reload.
Turn the category off again and save. c15t reloads the page, and the new page makes no vendor request.

c15t reloads on revocation because removing a script element does not stop code that already ran. The vendor's listeners, timers and queued events stay alive until the page unloads. If you set reloadOnConsentRevoked: false, stop the vendor yourself. Register a callback-only script whose onConsentChange calls the vendor's opt-out API, as shown in custom integrations, and check the permission before each of your own event calls. The reload does not delete cookies the vendor already set; see clear on revocation for your framework.

The helper sets vendor to its script ID, so once you declare that vendor a visitor can turn it off inside an allowed category. See vendor consent for your framework. The consent verification guide covers navigation, expiry and hosting checks.