source in BidvertiserValidVisit names the bad source id (subid); block it in the Bidvertiser panel.
Bidvertiser is a long-running self-serve PPC network spanning direct-link, banner and search-feed inventory across a broad base of smaller publishers. Its optimization model is built around the source id: Bidvertiser's own guidance is to improve ROI by excluding underperforming subids, so the {BV_SRCID} token is both the dimension you analyse and the unit you act on. ValidVisit captures {BV_SRCID}, {BV_CAMPID} and {BV_ADNAME} on arrival (with the {BV_CLICKID} for conversion matching), grades each click on a 0–100 quality scale, and reports which sources carry invalid traffic — so the subids you exclude are chosen from evidence rather than from raw conversion lag alone.
https://yoursite.com/landing?utm_source=bidvertiser&utm_medium=banner&vv_campaign_id={BV_CAMPID}&vv_publisher_id={BV_SRCID}&vv_ad_id={BV_ADNAME}&vv_click_id={BV_CLICKID}Bidvertiser's long tail of smaller publishers and its search-feed inventory create two distinct IVT pressures. The first is low-quality source inventory: sources that route cheap, non-organic visitors into direct-link or banner clicks, where a share of the clicks come from automated sessions or users with no intent. Because each click carries a {BV_SRCID}, this concentrates visibly in specific sources rather than spreading evenly.
The second, relevant to the search-feed side, is patterns consistent with low-intent or automated clicking on contextual placements — sessions with near-zero dwell, arriving in tight clusters that look nothing like organic search behaviour. ValidVisit weighs each click against more than 100 independent data points — where the click originated, the device sitting behind it, and the way the visitor actually behaves on the page — and folds them into one quality score, so real people pass and machine-driven clicks stand apart. That works on cheap inventory precisely because it doesn't lean on any single behavioural cue that's naturally weak there. Every finding is attributed to the {BV_SRCID}, so a single bad source is separable from the rest of a campaign.
Rank {BV_SRCID} values by quality score and by the share of clicks landing in the suspicious/bad tier. Bidvertiser's own optimization is subid-based, so this list maps directly onto the sources you exclude.
When a source's clicks cluster around questionable network origins and devices that don't add up, that points to automated or non-organic clicking. ValidVisit ties each pattern to the {BV_SRCID} so you exclude the right sub-source.
Contextual/search-feed clicks are weighed across the full set of quality signals rather than time-on-page alone, so genuinely brief but real visits aren't mistaken for bots while automated clicking still surfaces.
Compare {BV_CAMPID} click volume against conversions; a spike in clicks without conversions usually traces to a specific source the per-subid breakdown will identify.
Each Bidvertiser macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
| Token | Bidvertiser macro | Maps to | Identifies |
|---|---|---|---|
| Campaign ID | {BV_CAMPID} | campaign_id | campaign |
| Source ID | {BV_SRCID} | publisher_id | publisher |
| Ad Name | {BV_ADNAME} | ad_id | ad |
| Click ID | {BV_CLICKID} | click_id | click |
{BV_CAMPID}{BV_SRCID}{BV_ADNAME}{BV_CLICKID}Bidvertiseritself 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 Bidvertiser tokens, not by creative (which says nothing about whether a click was human).
Illustrative example — Bidvertiser traffic scored 0–100 per sub-source, worst first.
See your own Bidvertiser sub-sources scored this way.
Bot / invalid-traffic score broken down by:
{BV_SRCID}Traffic source (subid) — the unit you block in the advertiser panel.Per-click id: Bidvertiser passes a unique click id, so we also run velocity, deduplication and repeat-source checks on every click.
Compare bot & invalid-traffic breakdown across every ad network →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.
Add ValidVisit's script to your landing page and append Bidvertiser's macros — {BV_SRCID}, {BV_CAMPID}, {BV_ADNAME} and {BV_CLICKID} — to your destination URL. The pixel captures them on arrival and stores a scored verdict per click, segmented by source and campaign, with nothing on the click path.
Yes — and it aligns with Bidvertiser's own optimization model. Because {BV_SRCID} is captured on every click, ValidVisit ranks your sources by quality and by how strongly each one trips the quality score, and you exclude the offenders yourself in the Bidvertiser advertiser panel. ValidVisit reports the evidence; the exclusion is yours to apply.
Often yes — the long tail is where both cheap reach and invalid traffic live, so the deciding factor is whether you can tell them apart. Per-source scoring lets you keep the sources delivering real clicks and exclude the ones that don't, instead of judging the whole network by its blended numbers.
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