# OpenAI Pixel

The c15t openaiPixel helper loads the OpenAI ChatGPT Ads Measurement Pixel only after visitors allow marketing in Inth. It sends oaiq consent on each change.

## Key facts

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

## Links

- [Documentation](https://c15t.com/docs/integrations/openai-pixel)
- [OpenAI Pixel](https://developers.openai.com/ads)

Measure ChatGPT ad conversions only after visitors allow marketing. The OpenAI Pixel starts with consent off and turns it on in the same step.

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. Find it on the conversions tab in OpenAI 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 OpenAI Pixel

Before marketing has permission, the c15t openaiPixel helper defines no oaiq queue and loads nothing from OpenAI. Measurement alone does not load the pixel.

After permission, the helper queues oaiq('consent', false), init and oaiq('consent', true). Then it loads oaiq.min.js. The first call overrides the default consent of the SDK.

On withdrawal, the helper keeps the SDK and calls oaiq('consent', false). OpenAI drops events sent while consent is off and does not replay them.

The helper sends no page view or conversion. So every event comes from your code.

[Read the OpenAI measurement pixel docs](https://developers.openai.com/ads/measurement-pixel#send-user-data)

## Installation

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

### Wait for permission

No request goes to OpenAI until the visitor accepts marketing. On withdrawal, the pixel gets oaiq('consent', false).

```ts
openaiPixel({ pixelId })
```

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

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

#### Add your pixel ID

c15t passes user on as it is. Normalize and hash identifiers yourself, as the OpenAI user data rules describe.

```
import { openaiPixel } from '@c15t/integrations/openai-pixel';

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

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

#### Check permission before each event

window.oaiq still exists after withdrawal. amount is an integer in the currency's minor unit, such as cents for USD.

```
export function trackOrder(marketingAllowed: boolean, orderId: string) {
  if (!marketingAllowed || typeof window.oaiq !== 'function') return;
  window.oaiq(
    'measure',
    'order_created',
    { type: 'contents', amount: 2599, currency: 'USD' },
    { event_id: orderId }
  );
}
```

### 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 standalone OpenAI snippet. The helper creates the oaiq queue and sets up the pixel itself. Reuse event\_id on the server event to remove duplicates.

## Verify your setup

Set debug: true while you test. Use a private window with an opt-in policy, and open DevTools Network. Then test the three states.

- **Before a choice**: No request goes to bzrcdn.openai.com, and window.oaiq does not exist.

- **After you allow marketing**: oaiq.min.js loads. A guarded event reaches https://bzr.openai.com/v1/sdk/events and shows in Event Stream in Ads Manager.

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

For a Content Security Policy, allow bzrcdn.openai.com in script-src. Add bzr.openai.com and bzrcdn.openai.com in connect-src and bzr.openai.com in img-src.

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

## Related guides

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

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

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