What Is CHEQ? – Definition and How It Works
Learn what CHEQ does, why click fraud and ad verification differ from bot blocking, and how to recognise it.
CHEQ is a go-to-market security platform focused on invalid traffic: click fraud, fake conversions, and bot contamination of marketing analytics. It classifies visitors to protect ad spend and data quality, not usually to block access.
1. A Different Objective
Most anti-bot products protect content or transactions. CHEQ protects measurement and spend.
| Bot management | Invalid traffic detection | |
|---|---|---|
| Protects | Content, accounts | Ad budget, analytics accuracy |
| Typical action | Block, challenge | Tag, exclude, report |
| Cares about | Can this client be trusted? | Should this visit count? |
| Visible to visitor | Often | Rarely |
| Placement | Edge, before content | Alongside analytics tags |
The consequence: CHEQ's presence usually does not mean you will be blocked. It means your visit may be classified as invalid and excluded from the site's reporting.
2. Why Invalid Traffic Matters to Sites
A site paying for advertising wants to know which clicks were real. Bot traffic inflates click counts, corrupts conversion rates, and wastes budget on impressions no person saw.
So the product's job is separating human visits from automated ones for accounting purposes, and feeding that back into ad platforms and analytics.
3. Identifying It
| Class | Signal |
|---|---|
| URL | script loaded from a CHEQ tag domain |
| Content | CHEQ-related script references |
| Window | globals defined by the tag |
| Payload | telemetry posts to a CHEQ endpoint |
| Cookie | tag-set identifiers |
It loads like an analytics tag rather than an edge defence — typically alongside other marketing scripts, not as a gate in front of the page. That placement is itself the identifying characteristic.
4. What It Collects
Broadly the same client-side surface as any fingerprinting product — browser and device characteristics, automation artefacts, interaction behaviour, address reputation, and referrer and campaign context.
The campaign context is distinctive: invalid-traffic detection cares which ad or source delivered the visit, because that is the unit being protected.
5. Implications for Collection Work
You are probably not blocked. If a page loads and content is present, the tag has not gated anything.
Your visits pollute someone's analytics. This is the honest consideration. A crawler hitting pages carrying marketing tags inflates that site's traffic figures and, if it touches ad-tracked landing pages, can register as invalid clicks.
That is a real cost imposed on the site, and it argues for two things:
- Do not crawl ad landing pages or click through advertisements. Following an ad link is a chargeable event for someone.
- Strip or avoid campaign parameters rather than requesting URLs with
utm_*and click identifiers, which is what makes a visit look like a campaign response.
Blocking the tag reduces the pollution. In a browser context, blocking analytics and ad scripts means the tag never fires — which is both faster for you and cleaner for them.
6. Blocking Marketing Tags Is Usually Right
BLOCK_HOSTS = ("doubleclick.net", "googletagmanager.com", "google-analytics.com",
"facebook.net", "hotjar.com", "clarity.ms")
def route(r):
if any(h in r.request.url for h in BLOCK_HOSTS) or r.request.resource_type in {"image", "font", "media"}:
return r.abort()
return r.continue_()
page.route("**/*", route)
This is the rare case where the polite choice and the efficient choice coincide: fewer requests, less bandwidth, faster pages, and no contamination of the site's measurement.
7. What Not to Conclude
CHEQ's presence is not a statement that a site objects to crawling — it is a statement that the site buys advertising. Many sites with CHEQ have entirely open content and a permissive robots.txt.
Conversely, being classified as invalid traffic is not a block and produces no error. There is nothing to detect from your side, which is precisely why the consideration is ethical rather than technical.
8. Summary
CHEQ detects invalid traffic to protect advertising spend and analytics accuracy, loading as a marketing tag rather than as an edge gate, and classifying visits rather than blocking them.
Its presence rarely obstructs collection — but crawling pages that carry it pollutes the site's measurement and, on ad-tracked URLs, can register as invalid clicks, so avoid advertisement links and campaign parameters and block marketing tags in browser contexts, which is faster for you and cleaner for them.