TikTok Pixel

What it does. Puts the TikTok Pixel into limited data use mode for US visitors covered by an opt-out.

Consent category. None. Like the Meta and Google equivalents it reads the durable US opt-out record rather than a consent category, because opt-out rights and opt-in consent are different legal instruments.

How it works

TikTok's documented entry point is ttq.load(PIXEL_ID, { limited_data_use: true }), which only helps if you control the load call. Most sites don't, because the pixel comes from a tag manager or a theme. So the bridge uses the post-load form instead:

ttq.instance(PIXEL_ID).setLimitedDataUse(true);

That call needs the pixel ID, which is why this integration asks for one when the others don't. Without an ID there's no instance to reach, and the snippet isn't generated at all rather than shipping something that can't work.

The signal is sent at load from the stored opt-out record, then again on each consent update.

Setup

Off by default. Both the flag and the ID live in the banner theme's customFeatures:

{
  "usLimitedDataUse": {
    "tiktok": true,
    "tiktokPixelId": "CABCDEFGHIJKLMNOP"
  }
}

The ID is validated against ^[A-Za-z0-9_-]{1,64}$ before it's written into the script. An ID that doesn't match is dropped, and dropping the ID disables TikTok, so a typo turns the integration off rather than generating a broken call.

There's no dashboard control yet, so this needs a theme update through the API.

Testing

Confirm the instance exists before anything else:

window.ttq && window.ttq.instance('YOUR_PIXEL_ID')

If that's undefined the pixel hasn't loaded, and the bridge has nothing to talk to. Once it's there, check the requests to TikTok's collection endpoint from a US visitor and confirm the limited data use flag rides along.