# Pinterest Tag

The c15t pinterestTag helper loads the Pinterest Tag only after visitors allow marketing in Inth. It sends pintrk setconsent true and false as the choice changes.

## Key facts

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

## Links

- [Documentation](https://c15t.com/docs/integrations/pinterest-tag)
- [Pinterest Tag](https://business.pinterest.com/)

Load the Pinterest Tag only after visitors allow marketing. On withdrawal, setconsent false stops events and clears the first party storage of Pinterest.

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 the numeric tag ID from Pinterest Ads Manager.

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 gets to the Pinterest Tag

Before marketing has permission, the c15t pinterestTag helper defines no pintrk function and loads nothing from Pinterest.

After permission, the helper queues load, pintrk('setconsent', true) and a page visit. Then it loads core.js.

On withdrawal, the helper keeps the tag and calls pintrk('setconsent', false). Pinterest says that this stops events and clears its first party storage.

If the visitor allows marketing again before the reload, the helper calls setconsent true.

## Installation

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

### Wait for permission

No request goes to Pinterest until the visitor accepts marketing. On withdrawal, the tag gets setconsent false.

```ts
pinterestTag({ tagId })
```

An opt-out policy or no policy gives optional categories permission before a choice. Then the Pinterest 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 Pinterest Tag.

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

#### Add your tag ID

The helper sends the page visit. Events from your code, such as checkout or lead, need a permission check of their own.

```
import { pinterestTag } from '@c15t/integrations/pinterest-tag';

export const scripts = [pinterestTag({ tagId: '2613654212508' })];
```

The package also exports pinterestTagEvent. It does not check permission, so check it before each call.

#### Check permission before each event

window.pintrk still exists after withdrawal. Put product details in line\_items, and set event\_id to match the Conversions API event.

```
export function trackCheckout(marketingAllowed: boolean, orderId: string) {
  if (!marketingAllowed || typeof window.pintrk !== 'function') return;
  window.pintrk('track', 'checkout', {
    currency: 'USD',
    event_id: orderId,
    order_id: orderId,
    value: 99.99,
    line_items: [{ product_id: '1414', product_quantity: 1 }],
  });
}
```

### 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 Pinterest base code and its noscript image. That image fires without JavaScript, so c15t cannot hold it back.

## Verify your setup

Use a private window with an opt-in policy. Open DevTools Network and filter by pinimg. Pinterest Tag Helper also helps here.

- **Before a choice**: core.js does not load, and window.pintrk does not exist.

- **After you allow marketing**: core.js loads from s.pinimg.com, and Tag Helper shows the page visit. Tag Helper also records a guarded event.

- **After you withdraw marketing**: Until the reload, trackCheckout sends nothing.

Pinterest reports conversions only for its 20 event types. It uses other event names to build audiences.

[Open the full Pinterest Tag guide](https://c15t.com/docs/integrations/pinterest-tag)

## Related guides

- [Reddit Pixel](/integrations/reddit-pixel)

- [Snapchat Pixel](/integrations/snapchat-pixel)

- [The Trade Desk](/integrations/the-trade-desk)