Ads and pixels

Snapchat Pixel

Configure the Snapchat Pixel

Copy the pixel ID from Snapchat Ads Manager. The helper passes it to snaptr('init', ...).

npm install @c15t/integrations@alpha

src/consent-scripts.ts

import { snapchatPixel } from '@c15t/integrations/snapchat-pixel';

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

Register the scripts

Complete your framework quickstart first. Keep its Inth endpoint, policy, styles and consent UI. Remove the vendor's original script, SDK initializer or tag-manager entry, so the vendor loads only through c15t.

The vendor pages put the helper in src/consent-scripts.ts. If your framework quickstart already has a scripts array, such as the one in c15t.config.ts in the Next.js guide, add the helper to that array instead of creating a second file. The scripts export is a configuration, not an initializer. Add it to the c15t provider you already have, at the registration point for your framework below. These are edits to that provider, not a second provider.

Add the configuration to scripts in c15t.config.ts, next to next.config.ts:

import { defineConsentConfig } from 'c15t/next';
import { scripts } from './src/consent-scripts';

export default defineConsentConfig({ scripts });

Keep the rest of your config, such as mode and routePrefix, in the same call. ConsentRoot reads the config in the browser, so the layout keeps passing only state. App Router, Pages Router and static export all read the same file. See Next.js scripts and embeds.

Options

Option	Default	Behavior
`pixelId`	Required	Pixel ID passed to `snaptr('init', ...)`. The helper trims it. Empty or whitespace-only values log an error and the script does not load.
`initOptions`	None	Object passed as the third argument to `snaptr('init', ...)`, such as `user_email`. Pass user data only when your app has the permission it needs.
`trackPageView`	`true`	Queues `snaptr('track', 'PAGE_VIEW')` after `init`. Set `false` to send page views yourself.
`scriptUrl`	`https://sc-static.net/scevent.min.js`	Loader URL override. A blank value falls back to the default.

Loading and revocation

snapchatPixel uses the marketing category. Before marketing is allowed, c15t defines no snaptr function and loads nothing from Snapchat. When marketing becomes allowed, the helper queues init and PAGE_VIEW, then loads scevent.min.js.

On revocation the helper removes the script element and calls no Snapchat API, so the page reload is what stops the pixel. window.snaptr stays defined until then.

Guard your own snaptr calls

The helper sends the page view. Events your code sends, such as PURCHASE or SIGN_UP, need their own check. After revocation window.snaptr still exists, so its presence does not mean marketing is allowed. Check the permission first, then that the pixel has loaded:

src/track-purchase.ts

export function trackPurchase(marketingAllowed: boolean, orderId: string) {
	if (!marketingAllowed || typeof window.snaptr !== 'function') return;
	window.snaptr('track', 'PURCHASE', {
		client_dedup_id: orderId,
		currency: 'USD',
		price: 99,
		transaction_id: orderId,
	});
}

Pass the current marketing permission from your framework, for example useConsent('marketing') in React. Set client_dedup_id to deduplicate against the Conversions API. @c15t/integrations/snapchat-pixel also exports snapchatPixelEvent, a typed wrapper around snaptr('track', ...). It does nothing until snaptr exists and does not check permission, so apply the same guard before calling it.

Verify the Snapchat Pixel

After you allow marketing, scevent.min.js loads from sc-static.net and the pixel sends one PAGE_VIEW. If your router also sends PAGE_VIEW, check that the first page sends one, not two. Trigger one guarded event and check that its request appears. Then revoke marketing. Until the page reloads, calling trackPurchase sends nothing.

Test in a private window with an opt-in policy. Open DevTools Network, disable the cache and filter by the vendor's domain:

Load the page. No request goes to the vendor before you choose.
Click Reject, then reload. There is still no vendor request.
Open Privacy settings and allow the helper's category. The vendor script loads without a page reload.
Turn the category off again and save. c15t reloads the page, and the new page makes no vendor request.

c15t reloads on revocation because removing a script element does not stop code that already ran. The vendor's listeners, timers and queued events stay alive until the page unloads. If you set reloadOnConsentRevoked: false, stop the vendor yourself. Register a callback-only script whose onConsentChange calls the vendor's opt-out API, as shown in custom integrations, and check the permission before each of your own event calls. The reload does not delete cookies the vendor already set; see clear on revocation for your framework.

The helper sets vendor to its script ID, so once you declare that vendor a visitor can turn it off inside an allowed category. See vendor consent for your framework. The consent verification guide covers navigation, expiry and hosting checks.