# Meta Pixel

The c15t metaPixel helper loads the Meta Pixel only after visitors allow marketing in Inth. It sends fbq consent grant before init and revoke on withdrawal.

## Key facts

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

## Links

- [Documentation](https://c15t.com/docs/integrations/meta-pixel)
- [Meta Pixel](https://www.facebook.com/business/tools/meta-pixel)

Load the Meta Pixel only after visitors allow marketing, and send each choice through fbq consent grant and revoke.

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 pixel ID from Meta Events 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 Meta Pixel

Before marketing has permission, the c15t metaPixel helper defines no fbq function and loads nothing from Meta.

After permission, the helper queues fbq('consent', 'grant'), init and PageView. Then it loads fbevents.js.

On withdrawal, the helper keeps the pixel and calls fbq('consent', 'revoke'). If the visitor allows marketing again before the reload, it calls grant again.

## Installation

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

### Wait for permission

No request goes to Meta until the visitor accepts marketing. On withdrawal, the pixel gets fbq('consent', 'revoke').

```ts
metaPixel({ pixelId })
```

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

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

#### Add your pixel ID

The helper sends the page view of the pixel. Events from your code need a permission check of their own.

```
import { metaPixel } from '@c15t/integrations/meta-pixel';

export const scripts = [metaPixel({ pixelId: '123456789012345' })];
```

The package also exports metaPixelEvent and other typed wrappers. They do not check permission, so check it before each call.

#### Check permission before each event

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

```
export function trackPurchase(marketingAllowed: boolean, value: number) {
  if (!marketingAllowed || typeof window.fbq !== 'function') return;
  window.fbq('track', 'Purchase', { 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 pixel snippet, its noscript image and each tag manager entry for the same pixel.

## Verify your setup

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

- **Before a choice**: fbevents.js does not load, and window.fbq does not exist.

- **After you allow marketing**: fbevents.js loads, and a request to facebook.com/tr carries ev=PageView. A guarded event sends its own tr request.

- **After you withdraw marketing**: Before the reload, trackPurchase sends nothing. After the reload, the pixel stays blocked.

With client side navigation, make sure that each route change sends one page view, not two.

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

## Related guides

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

- [OpenAI Pixel](/integrations/openai-pixel)

- [Pinterest Tag](/integrations/pinterest-tag)