# LinkedIn Insight Tag

The c15t linkedinInsights helper loads the LinkedIn Insight Tag only after visitors allow marketing in Inth. On withdrawal, c15t removes the tag and reloads the page.

## Key facts

- **Tool:** LinkedIn Insight Tag
- **Category:** Advertising
- **Consent categories:** Marketing
- **Setup method:** c15t package
- **Package:** @c15t/integrations

## Links

- [Documentation](https://c15t.com/docs/integrations/linkedin-insights)
- [LinkedIn Insight Tag](https://business.linkedin.com/advertise/ads/insight-tag)

Measure LinkedIn campaigns and conversions only after visitors allow marketing. The Insight Tag stays off the page until then.

Inth keeps the consent record of each choice, with the visitor’s country and the policy that applied.

[Start for free](/dashboard/sign-up)

## Before you start

You need an Inth project that connects to your app, c15t in that app and your partner ID. Find it in LinkedIn Campaign Manager under Data, Signals manager, Insight Tag.

New to c15t? Complete the quickstart for your framework first. Keep its Inth endpoint, policy, styles and consent UI.

[Open the quickstart for your framework](https://c15t.com/docs/frameworks)

## How consent works with the LinkedIn Insight Tag

Before marketing has permission, the c15t linkedinInsights helper sets no LinkedIn globals and loads nothing from LinkedIn.

After permission, the helper sets the partner ID globals, defines the lintrk queue and loads insight.min.js. The tag tracks page views itself.

The helper sends no consent signal to LinkedIn. On withdrawal, c15t removes the script element and reloads the page. window.lintrk stays until the reload.

## Installation

The LinkedIn Insight Tag has one load mode in c15t. The helper waits for marketing permission.

### Wait for permission

No request goes to LinkedIn until the visitor accepts marketing. On withdrawal, c15t reloads the page.

```ts
linkedinInsights({ id })
```

An opt-out policy or no policy gives optional categories permission before a choice. Then the LinkedIn Insight Tag loads on the first page. This guide uses an opt-in policy.

## Setup steps

#### Install the integration package

Add the helpers next to c15t. An import alone does not start the LinkedIn Insight Tag.

```
pnpm add @c15t/integrations
```

#### Add your partner ID

Pass the partner ID as id. The helper handles the globals and the lintrk queue.

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

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

The package has no event wrapper for LinkedIn. Send conversions with lintrk, behind a permission check.

#### Check permission before each conversion

window.lintrk still exists after withdrawal. So check the current marketing permission first, for example with useConsent('marketing') in React.

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

### Register it with your existing setup

#### Next.js

Add scripts to c15t.config.ts, next to next.config.ts. Keep the rest of your config, such as mode, in the same call. App Router, Pages Router and static export read the same file.

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

export default defineConsentConfig({ scripts });
```

#### TanStack Start

Pass scripts to the ConsentRoot in your root route. Import helpers in the route module, not in a server function: script configurations carry callbacks.

```
import { scripts } from '../consent-scripts';

<ConsentRoot state={consent} scripts={scripts}>
```

#### React

Add scripts to the options of your ConsentProvider, next to mode. Keep the banner, dialog and preferences link inside the provider.

```
import { scripts } from './consent-scripts';

<ConsentProvider options={{ mode, scripts }}>
```

#### Nuxt

Register scripts under the c15t key in app.config.ts. Keep them out of nuxt.config.ts, which reaches the browser as JSON and drops the helper callbacks.

```
import { scripts } from '../src/consent-scripts';

export default defineAppConfig({
  c15t: { scripts },
});
```

#### Vue

Pass scripts to the c15tVue plugin call you have now. The plugin starts one script loader when the app mounts.

```
import { c15tVue, manifest } from 'c15t/vue/vue-plugin';
import { scripts } from './consent-scripts';

app.use(c15tVue, {
  mode: manifest(),
  scripts,
});
```

#### Astro

Add scripts to the client entrypoint, which the integration finds on its own. Keep helpers out of astro.config.mjs: its options are serialized into the page.

```
import type { C15tClientOptionsExtension } from 'c15t/astro';
import { scripts } from './consent-scripts';

export default { scripts } satisfies C15tClientOptionsExtension;
```

#### Svelte

Pass scripts as a prop to the ConsentProvider you have now. The provider owns the loader and disposes it on unmount.

```
<script lang="ts">
  import { ConsentProvider, manifest } from 'c15t/svelte';
  import { scripts } from './consent-scripts';
</script>

<ConsentProvider mode={manifest()} {scripts}>
  <!-- Your app and consent UI -->
</ConsentProvider>
```

#### SvelteKit

Add scripts to the ConsentRoot in the root layout. Import helpers in the layout component, not in +layout.server.ts: a server load cannot send functions to the browser.

```
<script lang="ts">
  import { ConsentRoot } from 'c15t/svelte';
  import { scripts } from '../consent-scripts';

  let { children, data } = $props();
</script>

<ConsentRoot state={data.consent} {scripts}>
  {@render children()}
</ConsentRoot>
```

#### HTML: Paste the vendor’s snippet behind consent

The helpers need a bundler. On a page with the c15t script tag, paste the vendor’s own snippet instead and keep it inert until visitors allow its category. Helper options, such as loadMode, do not apply.

```
<script type="text/plain" data-c15t-category="marketing">
  // The vendor's snippet, unchanged
</script>
```

#### JavaScript

Pass scripts to init() from @c15t/browser, next to your mode. With createConsentRuntime, pass scripts to it instead.

```
import { init, manifest } from '@c15t/browser';
import { scripts } from './consent-scripts';

const consent = init({
  mode: manifest(),
  scripts,
});
```

Remove the original Insight Tag snippet and its noscript image.

## Verify your setup

Use a private window with an opt-in policy. Open DevTools Network and filter by licdn. Then test the three states.

- **Before a choice**: No request goes to LinkedIn, and no LinkedIn globals exist.

- **After you allow marketing**: insight.min.js loads from snap.licdn.com, and window.\_linkedin\_data\_partner\_ids holds your partner ID. A guarded conversion sends its request.

- **After you withdraw marketing**: Until the reload, trackSignup sends nothing. After the reload, the tag stays blocked.

Use the conversion ID of your LinkedIn conversion in place of the example value.

[Open the full LinkedIn Insight Tag guide](https://c15t.com/docs/integrations/linkedin-insights)

## Related guides

- [LiveIntent](/integrations/liveintent)

- [Meta Pixel](/integrations/meta-pixel)

- [Microsoft UET](/integrations/microsoft-uet)