Which MediaGo publishers send bots and invalid traffic?
Not all MediaGo traffic is equal. ValidVisit scores every visit 0–100 and pins it to the exact publisher that sent it — so you can tell real humans from bots and invalid clicks, worst publishers first.
site in MediaGoThe buyer adds each bad site’s site_id/domain to the campaign’s block list (op=0 block / op=1 unblock), max 100 sites per API call; tools like TheOptimizer automate this into dynamic global blacklists per campaign.
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and MediaGo supports OS, browser and device type targeting. The segments we flag are segments you can exclude.
How invalid traffic slips in through MediaGo publishers.
MediaGo serves native placements across a wide open supply of publisher sites, and every click it sends carries a ${SITE_ID} identifying the exact site the placement ran on, plus a ${TRACKING_ID} tying that session back to your campaign record. That site-level transparency is the useful part, because the quality spread across an open native supply is wide: established publishers sit in the same auction as long-tail sites and content-farm operators, and all of them surface under the same sponsored-content wrapper. The buyer-side problem is that the native format supplies its own cover — a placement inside credible editorial surroundings reads as legitimate regardless of how the visitor arrived on that page. ValidVisit approaches the split differently: every inbound visit is measured against 100+ independent data points spanning the network the click came from, the device behind it, and how the visitor actually behaves once the page loads, and all of that collapses into a single 0–100 quality score for that one visit. Real readers clear the bar; automated and arbitraged sessions surface against it. Because the score is per-visit and attributed to its ${SITE_ID}, you can tell a site whose audience is merely disengaged from one whose click volume has a structural invalid-traffic problem — a distinction that decides whether you lower a bid or block the site outright.
Invalid traffic on MediaGo is shaped by how open native supply is acquired, not by the native format itself. The dominant pattern is arbitrage-driven inflation: a publisher buys cheap visitors through display, push or pop inventory, uses those arrivals to build native impression volume, and a share of the resulting sponsored-content clicks come from visitors with no interest in the offer — or from automated sessions that exist only to generate click revenue. Those sessions arrive through a real browser on a real publisher URL, which is exactly why address-based filtering alone rarely separates them. ValidVisit reads the network origin of each arriving click as part of its scoring, and that is where arbitrage tends to give itself away: sites running this pattern frequently route traffic through residential proxy pools to disguise a datacenter or server-farm origin, and that routing leaves a mark across the wider signal set well before any single filter would flag it.
A second pattern is automation that does not move like a person. A meaningful share of invalid native clicks comes from tooling and stripped-down browser builds that behave nothing like a reader once the click lands — the connection characteristics, the device profile, and the on-page activity fail to line up with a human on the operating system and browser the session claims to be using. MediaGo reports the OS and browser family behind a click, so a site whose declared device mix disagrees with what the visits actually do on the page is a readable signal rather than an inference.
A third and quieter pattern is low-intent human traffic reading as engaged. Visitors pushed onto arbitrage publisher pages from pop or extra-hop buys will interact with a native unit reflexively. ValidVisit separates this from automation: the session looks human across the network and device signals, but its depth and the texture of its engagement read as involuntary arrival rather than genuine interest. The remedy differs — a ${SITE_ID} dominated by automation warrants blocking, while one carrying real but low-intent humans may only warrant a lower bid.
What to watch on MediaGo
${SITE_ID}Segment your ValidVisit report by MediaGo’s ${SITE_ID} token. Sites contributing a disproportionate share of click volume alongside low quality scores are the primary signal of placement-level arbitrage. A single ${SITE_ID} whose score profile sits well below your campaign baseline is a candidate for the campaign block list before its volume starts shaping how the campaign optimizes.
For each site, check whether a weak score is driven mostly by where the click came from on the network side or by how it behaved after landing. A ${SITE_ID} whose low scores trace almost entirely to its traffic origin points to a structural sourcing problem — the publisher is acquiring sessions through proxy or datacenter routes. One where the weakness appears mainly in on-page behaviour suggests a smaller automated operation, which a bid reduction may address without losing the inventory.
${ASSET_ID} on the same siteIf one creative on a given ${SITE_ID} draws a disproportionately low-quality click share while another on the same site draws valid traffic, the cause is more likely site-side automation hitting placements indiscriminately than anything about the creative. Ruling out the creative explanation first keeps you from blocking a site that is actually fine.
Automated click activity on native supply often concentrates outside the hours a real content audience is reading. A high-volume ${SITE_ID} scoring well below your baseline in quiet windows but looking valid at peak is showing you a time signature worth carrying into your review before you decide to block.
Pinpoint the bot publishers & placements in MediaGo.
MediaGo itself 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 MediaGo tokens, not by creative (which says nothing about whether a click was human).
Bought as one MediaGo line, a buy reads as a single number. Scored per sub-source, a spread like this illustration runs from 86 down to 20 — the worst is nearly all bots. That’s the leak a blended average hides.
Illustrative: MediaGo traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
Bot / invalid-traffic score broken down by:
- Site ID
${SITE_ID}Identifier of the publisher site/placement where the click was served.
Per-click id: MediaGo passes a unique click id, so we also run velocity, deduplication and repeat-source checks on every visit.
Compare bot & invalid-traffic breakdown across every ad network →See your own MediaGo sub-sources scored this way.
How ValidVisit attributes MediaGo traffic
Each MediaGo macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
https://yoursite.com/landing?utm_source=mediago&utm_medium=native&vv_campaign_id=${CAMPAIGN_ID}&vv_campaign_name=${CAMPAIGN_NAME}&vv_ad_id=${AD_ID}&vv_publisher_id=${SITE_ID}&vv_click_id=${TRACKING_ID}&vv_creative_id=${ASSET_ID}| Token | MediaGo macro | Maps to | Identifies |
|---|---|---|---|
| Campaign ID | ${CAMPAIGN_ID} | campaign_id | campaign |
| Campaign Name | ${CAMPAIGN_NAME} | campaign_name | campaign |
| Ad ID | ${AD_ID} | ad_id | ad |
| Site ID | ${SITE_ID} | publisher_id | publisher |
| Tracking ID (Click ID) | ${TRACKING_ID} | click_id | click |
| Asset ID (Creative) | ${ASSET_ID} | creative_id | creative |
- MediaGo macro
${CAMPAIGN_ID}- Maps to
- campaign_id
- Identifies
- campaign
- MediaGo macro
${CAMPAIGN_NAME}- Maps to
- campaign_name
- Identifies
- campaign
- MediaGo macro
${AD_ID}- Maps to
- ad_id
- Identifies
- ad
- MediaGo macro
${SITE_ID}- Maps to
- publisher_id
- Identifies
- publisher
- MediaGo macro
${TRACKING_ID}- Maps to
- click_id
- Identifies
- click
- MediaGo macro
${ASSET_ID}- Maps to
- creative_id
- Identifies
- creative
How the detection works.
Data points → one score
Every visit is weighed against more than a hundred independent data points and reduced to a single, sortable 0–100 quality score.
Many angles, combined
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.
Proprietary, not a black box
The detection model is ours and stays that way. What you get is a clear verdict on every visit — not a single brittle rule you can game, and not an unexplained number you can’t act on.
Pinned to the source
Every verdict maps to the campaign, publisher and placement that sent the click — so you know exactly which source to cut.
How ValidVisit helps you cut fraud and bad sites on MediaGo.
Scoring and attribution are the means — the point is cutting the MediaGo traffic that wastes your spend. Here’s how ValidVisit gets you a list you can act on.
- Score
See what’s actually landing
You buy MediaGo clicks; what arrives are visits. ValidVisit scores each one 0–100 so real humans stand out from bots and invalid traffic — one script, no funnel hop, no fingerprinting.
- Attribute
Pin the fraud to its source
Every scored visit is tied to the exact MediaGo site and zone via the network’s own tokens — so the bad traffic has an address, not just a headline percentage.
- Cut
Take the sites off your buy
You get the worst offenders as a ready-to-use list plus postbacks to your tracker — so you can exclude them in MediaGo and put your next dollar behind the traffic that converts.
MediaGo traffic quality, answered.
Does ValidVisit block MediaGo sites automatically, or is it manual?
It is manual. ValidVisit scores every visit and surfaces the ${SITE_ID} values carrying weak quality scores in its reports and dashboard. You take those site IDs and add them to the campaign’s block list — either in the MediaGo dashboard’s campaign site report, or programmatically through the platform’s Sites Block Management API, which blocks and unblocks sites per campaign in batches of up to 100. There is no automated push from ValidVisit into MediaGo. The workflow is: score in ValidVisit, identify the problem ${SITE_ID}, block it in MediaGo. That keeps the decision in your hands and avoids cutting a site over an isolated spike rather than a structural problem.
MediaGo optimizes on the conversions I send back — won’t it route around bad sites on its own?
Only if the signals it is optimizing on are valid. When invalid clicks from a weak site reach your conversion pixel or your thank-you page, they register as conversion-adjacent events in the platform’s feedback loop, and the optimization can respond by sending MORE budget toward that site rather than less. ValidVisit sits outside that loop: it gives you a per-click quality score you own independently, so you can see which sites are corrupting the signal and block them before the algorithm learns from bad data.
Which MediaGo tokens give the most useful segmentation in ValidVisit?
The ${SITE_ID} is the highest-leverage token, because it maps to the publisher site behind each click and it is the same dimension you act on in MediaGo’s own block list — so ValidVisit’s quality scores line up against the platform’s site reporting without a translation step. The ${TRACKING_ID} gives per-click identity and ties each scored visit back to a specific MediaGo click record, which is also what carries a server-to-server conversion postback. Adding ${CAMPAIGN_ID} and ${ASSET_ID} lets you confirm whether a weak pattern is site-wide or specific to how one creative is being served there, which changes whether you block or rebid.
Detect fraud on other native networks
AdNow
Adskeeper
KadamFind the bots in your MediaGo spend.
See which publishers and placements send real buyers vs bots — every visit scored 0–100, worst first.
Free trial at launch · just your email
One script · no cookies · no fingerprinting · raw IP never stored