# Ad pixels

> When Antiro judges a visitor to be a bot, the script keeps that visit away from your ad accounts, so your campaigns do not learn from fake traffic.

This is one page of the Antiro docs (https://docs.antiro.io/sdk/ad-pixels). Every page in one file: https://docs.antiro.io/llms-full.txt

## What the script does

| Platform | What happens |
| --- | --- |
| Meta | Consent is withdrawn with `fbq('consent', 'revoke')` |
| TikTok | Consent is withdrawn with `ttq.revokeConsent()` |
| Snap | `track` calls are dropped |
| Google Tag Manager | An event is pushed to `dataLayer` |

This lasts for the rest of the tab’s session. The script never grants consent, and nothing changes for other visitors.

## Google Tag Manager

Add a blocking trigger on this event to your conversion tags.

**Pushed to dataLayer**

```js
// pushed to dataLayer for a tab judged a bot
{ event: 'antiro_verdict', antiro_verdict: 'bot' }
```

## When it runs

It runs only on stores in Protect mode, where it is on by default. A custom store can switch it off on the [API keys](https://dashboard.antiro.io/dashboard/api-keys) page.

To cover the purchase event on a thank-you page, [install the script there too](https://docs.antiro.io/sdk/install#thank-you-pages).