Clean ad data
Spurn can hold back the ad pixels on your site for the visitors it finds invalid, so bots stay out of your remarketing lists and out of the data Smart Bidding and Meta's delivery learn from.
Why it matters#
On Meta you pay per impression, so no fake click is ever refunded there. The money goes a different way. When a bot loads your store, the Meta pixel and the Google tag fire page views, add to carts and sometimes conversions for it. The bot joins your remarketing lists, and the platforms learn to find more visitors like it. From then on, more of your budget goes to bots.
Blocking keeps a bot's network away from your ads. Clean ad data keeps the bot out of what your ads learn from.
Switch it on#
- In Spurn, open Sites, choose your site, then the Rules tab.
- Under Clean ad data, switch on Hold back ad pixels for bots.
It applies to new paid landings within a minute, and nothing else changes on your site. Each site has its own switch, and every site starts with it off. It comes with every paid plan. Admins and owners can change it.
There is nothing to install: it works through the Spurn tag already on your pages. Server hits, the Cloudflare Worker and the tracking template can't reach the ad tags in a visitor's browser, so a site needs the tag for this.
What the tag does#
When Spurn's instant verdict on a paid landing is invalid, the tag:
Fires the audience events your site is set up for first, so your exclusion audiences keep filling:
SpurnInvalidTrafficto Meta,spurn_invalidto Microsoft, and the Google Ads exclusion audience conversion.Tells each ad tag on the page to stop collecting for this visitor:
Tag What Spurn sends What it does Google tag and Google Tag Manager gtag('consent', 'update', { ad_storage: 'denied', ad_user_data: 'denied', ad_personalization: 'denied' })Google tags set no ad cookies, add no one to remarketing lists and send no user data for advertising Meta pixel fbq('consent', 'revoke')The pixel sends nothing more for this visitor Microsoft UET uetq.push('consent', 'update', { ad_storage: 'denied' })UET reads and writes no ad cookies for this visitor Remembers it for the rest of the paid session (30 idle minutes), and does step 2 again at the start of every later page, before your page's own later events: product views, add to cart, checkout and purchase.
On a page with Google Tag Manager but no gtag function, Spurn puts the same consent command on the dataLayer the way gtag does, so GTM reads it. If a tag is not on the page, Spurn skips it.
Only invalid counts. Spurn never touches a visitor it judged valid, suspicious or pending, and it never grants consent: it only ever takes it away. A false positive costs as little as possible: one visitor's pixels, for one visit.
Bot traffic no ad platform charged for, such as a replay of your ad's link from a data centre, is held back too. It still fires your pixels when it loads the page. Holding it back is not a block on your ad platforms, so it never adds an exclusion.
What it can't cover#
- The first page view. Your ad tags usually fire as the page loads, before Spurn's verdict comes back, which takes about 100 ms. Spurn stops everything after that: later pages, add to cart, checkout events and conversions.
- Shopify's own Google and Meta channel apps. They run in Shopify's sandboxed pixel runtime and follow Shopify's customer privacy setting, which Spurn does not change. Tags in your theme or in Google Tag Manager are covered.
- Server-side events. The Meta Conversions API sent from your store's server, server-side Google Tag Manager and conversions uploaded from a server never pass through the visitor's browser, so Spurn cannot see them.
- A consent banner that grants consent again. If your banner updates consent to granted later on the same page, that undoes it for the rest of that page. Spurn applies the denial again on each later page.
Use it in Google Tag Manager#
Alongside the consent update, the tag pushes an event and sets a flag:
window.dataLayer.push({ event: 'spurn_guard' })
window.spurn.guarded // true
On later pages of the session, spurn_guard comes before spurn_verdict.
Tags that read consent mode need nothing more. To hold back a tag that doesn't, such as a custom HTML pixel:
- Variables, then New, then JavaScript Variable. Global Variable Name:
spurn.guarded. Save it asspurn_guarded. - Triggers, then New, then Custom Event. Name it
Spurn - pixels held back. Event name:.*, with Use regex matching on. - This trigger fires on Some Custom Events:
spurn_guardedequalstrue. - Open the tag and add
Spurn - pixels held backunder Exceptions.
See GTM and pixel events for the verdict event and more recipes.
See it working#
- Clicks. Open an invalid click. If its pixels were held back, the Blocking card says Pixels held back.
- Overview. With the switch on, the overview shows how many bot visits were kept out of your ad data in the period.
- In the browser. On a guarded visit, Google Tag Assistant shows
ad_storage,ad_user_dataandad_personalizationas denied after Spurn's update, andwindow.spurn.guardedistruein the console.
Privacy#
Spurn reads no consent state and sends nothing extra anywhere. It only tells the tags already on your page to collect less, for visitors it is confident are not people.