# TikTok Pixel

The c15t tiktokPixel helper loads the TikTok Pixel only after visitors allow marketing in Inth. It calls ttq grantConsent and revokeConsent as the choice changes.

## Key facts

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

## Links

- [Documentation](https://c15t.com/docs/integrations/tiktok-pixel)
- [TikTok Pixel](https://business.tiktok.com/)

Measure TikTok ad results only after visitors allow marketing. c15t grants and revokes TikTok consent as the choice changes.

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 TikTok Pixel ID.

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 TikTok Pixel

Before marketing has permission, the c15t tiktokPixel helper defines no ttq queue and loads nothing from TikTok.

After permission, the helper sets up ttq the way the TikTok base code does. It queues ttq.grantConsent() and ttq.page(), then loads events.js.

On withdrawal, the helper keeps the pixel and calls ttq.revokeConsent(). By default, c15t also reloads the page.

If the visitor allows marketing again before the reload, the helper calls ttq.grantConsent().

## Installation

The TikTok Pixel has one load mode in c15t. The helper waits for marketing permission.

### Wait for permission

No request goes to TikTok until the visitor accepts marketing. On withdrawal, the pixel gets revokeConsent.

```ts
tiktokPixel({ pixelId })
```

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

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

#### Add your pixel ID

The helper adds the pixel ID to the loader URL as sdkid. It also sends the page view.

```
import { tiktokPixel } from '@c15t/integrations/tiktok-pixel';

export const scripts = [tiktokPixel({ pixelId: 'YOUR_PIXEL_ID' })];
```

The package exports no event wrapper. Your ttq.track and ttq.identify calls need a permission check.

#### Check permission before each event

window.ttq still exists after withdrawal. So check permission first, and then check that the pixel is ready.

```
export function trackPurchase(marketingAllowed: boolean, value: number) {
  if (!marketingAllowed || typeof window.ttq?.track !== 'function') return;
  window.ttq.track('CompletePayment', { currency: 'USD', value });
}
```

### 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 TikTok base code, so it cannot load the pixel without consent.

## Verify your setup

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

- **Before a choice**: events.js does not load, and window.ttq does not exist.

- **After you allow marketing**: A request to analytics.tiktok.com/i18n/pixel/events.js carries your pixel ID as sdkid. The pixel sends one page event.

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

Pass the current marketing permission from your framework, for example useConsent('marketing') in React.

[Open the full TikTok Pixel guide](https://c15t.com/docs/integrations/tiktok-pixel)

## Related guides

- [Vector](/integrations/vector)

- [X Pixel](/integrations/x-pixel)

- [AdRoll](/integrations/adroll)