# X Pixel

The c15t xPixel helper loads the X Pixel only after visitors allow marketing in Inth. X has no consent API, so c15t removes the script and reloads the page.

## Key facts

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

## Links

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

Count X ad conversions only after visitors allow marketing. The X Pixel stays off the page until then, and withdrawal reloads the page.

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

Conversion event IDs look like tw-xxxx-xxxx. They are not the same as the pixel ID.

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

## How consent works with the X Pixel

Before marketing has permission, the c15t xPixel helper defines no twq function and loads nothing from X.

After permission, the helper queues twq('config', pixelId), then loads uwt.js. X has no API to update consent, so the helper sends no consent signal.

On withdrawal, c15t removes the script element and calls no X API. So the page reload stops the pixel. window.twq stays until then.

## Installation

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

### Wait for permission

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

```ts
xPixel({ pixelId })
```

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

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

#### Add your pixel ID

The helper passes the pixel ID to twq('config'). Conversion events come from your code.

```
import { xPixel } from '@c15t/integrations/x-pixel';

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

The package also exports xPixelEvent. Before the first grant, it does nothing. It does not check permission, so check it before each call.

#### Check permission before each conversion

window.twq still exists after withdrawal. Set conversion\_id to deduplicate the event.

```
export function trackPurchase(marketingAllowed: boolean, orderId: string) {
  if (!marketingAllowed || typeof window.twq !== 'function') return;
  window.twq('event', 'tw-xxxx-xxxx', {
    conversion_id: orderId,
    currency: 'USD',
    value: 99.99,
  });
}
```

### 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 X Pixel 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 ads-twitter. Then test the three states.

- **Before a choice**: uwt.js does not load, and window.twq does not exist.

- **After you allow marketing**: uwt.js loads from static.ads-twitter.com. A guarded event sends its own request to X.

- **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 X Pixel guide](https://c15t.com/docs/integrations/x-pixel)

## Related guides

- [AdRoll](/integrations/adroll)

- [Amazon Ads](/integrations/amazon-ads)

- [LinkedIn Insight Tag](/integrations/linkedin-insights)