Content.ad spreads advertiser spend across a sprawling roster of third-party publisher domains that embed native content widgets — the "you might also like" and "around the web" units tucked beneath editorial articles. For an advertiser, that reach is the draw and the exposure in equal measure. The supply chain runs deep: publishers accept programmatic fill from aggregators, aggregators pull from exchanges, and individual widget placements can swing wildly in the quality of audience they actually deliver. A campaign that looks healthy at the account level may quietly be bankrolling a handful of publisher domains whose traffic bears little resemblance to genuine reading intent. ValidVisit reads Content.ad's own tracking layer — the Campaign ID ([cid]), Ad ID ([adid]), and Domain ID ([did]) macros — and grades each arriving click on its own merits. Every click is weighed against more than 100 independent data points spanning the network it came through, the device behind it, and the way the visitor behaves, all distilled into a single 0–100 quality score; that score is then mapped straight back to the exact domain ID responsible. The outcome is a per-publisher quality picture that aggregated campaign metrics will never surface on their own.
https://yoursite.com/landing?utm_source=content-ad&utm_medium=native&vv_campaign_id=[cid]&vv_ad_id=[adid]&vv_publisher_id=[did]Native content networks present a different IVT surface than search or social. Because widget placements live inside editorial pages across thousands of domains, suspicious activity tends to pool inside a small number of publisher properties rather than spreading evenly across a campaign. A few domain IDs producing a disproportionate share of clicks relative to genuine engagement is the telltale pattern — and it is one standard attribution reporting misses entirely, because it rolls everything up at the campaign or ad level.
The forces behind this on Content.ad are rooted in publisher incentives. A domain that earns from native widget revenue has a financial reason to push click counts up whether or not a real reader is present. ValidVisit surfaces that by scoring each click holistically rather than leaning on any single tell: it looks across where the click originated, the device and connection it rode in on, and how — or whether — the visitor actually engaged with the page, then folds all of it into one 0–100 quality number. Clicks that arrive through anonymizing connections, that behave nothing like a person settling in to read, or that never genuinely load the article they supposedly landed on all push that score downward. That last case is especially diagnostic here: real article readers actually open and interact with the page, so a domain ID where a meaningful slice of sessions never behaves like a loaded, engaged visit is a strong sign the clicks aren't coming from real humans — they may be manufactured before any real page view ever happens.
Widget-arbitrage dynamics compound the picture. Some publishers in content-discovery networks keep the lights on by buying cheap traffic from third-party sources, parking it against pages that host native ad units, and collecting CPCs without delivering any audience value to the advertiser. ValidVisit's domain-level scoring makes that pattern legible in reports: the affected [did] values show depressed quality scores while click volume holds steady, a divergence that is invisible at the campaign level but obvious the moment you filter by publisher domain.
Pull your ValidVisit data grouped by [did] and weigh each domain's share of total clicks against its share of low-scoring sessions. When a publisher domain owns a lopsided fraction of poor-quality clicks while contributing only modestly to overall volume, that domain ID is your exclusion candidate — bring it to your Content.ad account team as a specific placement block request.
Traffic that hides behind residential proxies and VPNs is a recurring feature of native ad IVT, because it dresses each click up with a clean-looking IP that sails past crude origin checks. ValidVisit factors the nature of the connection into every click's quality score rather than treating an IP as trustworthy on its face. When clicks riding anonymizing connections pile up inside one or two [did] values, the source is almost certainly a single traffic operation feeding that publisher rather than organic noise scattered across the campaign.
Click farms, server farms, and scripted tooling leave clicks that simply do not move and behave like a person reading an article — the cadence, the device profile, and the engagement all come out wrong, and that pulls the quality score down. Cross-referencing those low-scoring sessions against the [did] dimension reveals which Content.ad publisher domains are absorbing a disproportionate share of automation-driven traffic, even when those clicks would shrug off a superficial IP check.
ValidVisit judges every click in part on whether the visit actually behaves like a person who opened and read the page. On a genuine editorial page, a real reader's session loads, lingers, and interacts. A domain ID where sessions arrive without ever behaving like a real, loaded page view at a notably higher rate than the rest of the campaign points to click injection or pre-render activity that never produced an actual reader. The signal is especially telling on Content.ad, where legitimate widget environments reliably involve a real, engaged page visit.
Each Content.ad macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
| Token | Content.ad macro | Maps to | Identifies |
|---|---|---|---|
| Campaign ID | [cid] | campaign_id | campaign |
| Ad ID | [adid] | ad_id | ad |
| Domain ID | [did] | publisher_id | publisher |
[cid][adid][did]Content.aditself isn’t the problem — bots and invalid traffic concentrate in a handful of its sub-sources: the publisher, site or zone, and the placement or widget within it. So we roll the score up by those Content.ad tokens, not by creative (which says nothing about whether a click was human).
Illustrative example — Content.ad traffic scored 0–100 per sub-source, worst first.
See your own Content.ad sub-sources scored this way.
Bot / invalid-traffic score broken down by:
[did]Identifier of the publisher domain/site (Content.ad 'Domain') the visitor came from. Confirmed verbatim from two independent sources: the brax.io Voluum native-tracking guide (utm_medium=[did]) and CPV Lab Pro integration docs.Every click is weighed against more than a hundred independent data points and reduced to a single, sortable 0–100 quality score.
Each data point is combined rather than checked in isolation, so a genuine human almost never trips enough of them to be flagged — and bots that beat one rarely beat the rest.
The detection model is ours and stays that way. What you get is a clear verdict on every click — not a single brittle rule you can game, and not an unexplained number you can't act on.
Every verdict maps to the campaign, publisher and placement that sent the click — so you know exactly which source to cut.
You append Content.ad's own dynamic macros — [cid], [adid], and [did] — to your destination URL as standard query parameters before the campaign goes live. When a click lands, ValidVisit reads those values straight from the arriving request, scores the click against its full set of quality data points, and records the resulting 0–100 score against that exact combination of campaign, ad, and domain ID. Nothing in the click path changes: no funnel hop, no intermediate page, no challenge dropped onto your landing page. Your destination URL behaves exactly as Content.ad expects, and ValidVisit pulls the attribution it needs from the parameters already in the URL.
Content.ad's own reporting shows delivery and spend by publisher, but it never lays a quality signal over that data. ValidVisit adds the 0–100 score — and the plain-language read behind it — that explains why a given [did] is a problem, whether the trouble is traffic arriving through anonymizing connections, clicks that behave like automation rather than people, or sessions that never act like a real page view. That distinction reshapes the conversation with your account team: instead of 'this domain has a high bounce rate,' you can say 'this domain ID shows a heavy concentration of low-quality clicks that look injected rather than genuinely read.' Targeted exclusion requests grounded in a concrete quality picture are far more actionable than spend-and-bounce data alone.
ValidVisit scores and reports — it does not push exclusions to Content.ad or any ad platform, and it never blocks a click in the path or excludes anything on its own. Scoring happens after the click has already arrived. Once your reports surface which domain IDs carry the most low-quality traffic, you take that list to your Content.ad account team and request publisher-level blocks, or apply the exclusions yourself if your account access allows it. The value is in having a scored, explainable basis for each exclusion decision rather than acting on intuition or aggregate metrics. Automated blocklist export to ad platforms is not a current capability.
See which campaigns and publishers send real, converting traffic vs bots — every click scored 0–100.
Free trial at launch · lock in early-access pricing
One script · raw IP never stored · GDPR legitimate-interest basis