Skip to content

Keep bots out of your ad data

When Spurn judges a visitor invalid, your Google tag, Meta pixel and Microsoft UET stop collecting for them for the rest of the session. Bots stay out of your remarketing lists, and your bidding doesn’t learn to buy more of them.

Why bot data costs you money

Smart Bidding and Meta’s delivery learn from your page views, add-to-carts and conversions. When bots trigger them, the platforms go looking for more visitors like the bots.

On Meta, this is the lever that matters

Meta bills per impression, so there is no fake click to claim back. Keeping bots out of your pixel, and out of your audiences, is how you stop paying to reach more of them.
  • Your overview shows Meta budget reaching bots (estimate), which is never refundable
  • On Growth and up, flagged visitors also join the exclusion audience your ad sets leave out
Meta Ads integration

On Google, bidding learns from shoppers

A bot that adds to cart or fires a conversion teaches Smart Bidding to bid up the traffic it came from. With clean ad data on, an invalid visitor sets no ad cookies, joins no remarketing list and sends no user data for ads from the browser.
  • Works with gtag.js and with Google Tag Manager
  • Only invalid verdicts count. Valid and suspicious visitors are never touched
Google Ads integration

What happens on an invalid verdict

It is one switch on each site’s Rules: “Hold back ad pixels for bots”. It is off until you turn it on, and Spurn never grants consent on anyone’s behalf.

  1. 1

    Spurn’s exclusion events fire first, so the visitor still joins the audiences your campaigns exclude.

  2. 2

    Google tag and Google Tag Manager: a Consent Mode update denies ad storage, ad user data and ad personalisation for this visitor.

  3. 3

    Meta pixel: consent is revoked, so the pixel sends nothing more for this visitor.

  4. 4

    Microsoft UET: ad storage is denied.

  5. 5

    Spurn remembers it for the paid session, so every later page applies the same hold before its own events fire.

What it covers, and what it can’t

It works on the tags in your pages. It cannot reach what fires before Spurn’s verdict, or what never passes through the browser.

It covers

  • The Google tag and Google Tag Manager, through a Consent Mode update
  • The Meta pixel, by revoking consent for that visitor
  • Microsoft UET, by denying ad storage
  • Every later page of the paid session, before that page’s own events

It can’t cover

  • The first page view. Ad tags usually fire before Spurn’s verdict comes back, about 100 ms later. Everything after it is covered.
  • Shopify’s own Google and Meta channel apps. They 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 from your store’s server, server-side Tag Manager, and conversions uploaded from a server.
  • A consent banner that grants consent again later in the session. Spurn applies the hold again on each later page.
The clean ad data guide

On every paid plan

Clean ad data is a tag behaviour with no platform cost, so it comes with every paid plan from Starter.

FeatureFreeStarterGrowthProAgency
Verdict for every paid visitor
Clean ad data

Stop paying for clicks that never shop

Start on the free plan: 1,000 paid clicks a month and the Google Ads health check, no card. Paid plans begin with a 14-day trial.