Which MyBid zones send bots and invalid traffic?
Not all MyBid traffic is equal. ValidVisit scores every visit 0–100 and pins it to the exact zone that sent it — so you can tell real humans from bots and invalid clicks, worst zones first.
source in MyBidThe buyer pastes bad Source IDs into the campaign’s blacklist under Targeting & Restrictions (or lets the rule-based Optimizer auto-block sources, then reviews/unblocks them in the Blocked sources tab).
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and MyBid supports OS version, browser version, language, device type and connection type targeting. The segments we flag are segments you can exclude.
How invalid traffic slips in through MyBid zones.
MyBid runs pop, push, native and banner inventory through a single campaign editor, and every click carries a {%click_id%}, a {%source_id%} naming the traffic source behind it, and a {%creative_id%} for the unit that was served. The platform gives buyers unusually graduated control over those sources: a manual black and white list under Targeting & Restrictions, a per-source bid override in the Bid by source section, and a rule-based Optimizer that blocks sources on its own and files them in a Blocked sources tab for review. Three levers with three different costs of being wrong. What none of them supplies is the judgement about which lever a given source deserves, because the platform’s own view of a source is assembled from the outcomes you report back to it. ValidVisit measures the input rather than the outcome: every inbound visit is scored against 100+ data points spanning the network the click arrived from, the device behind it, and how the session behaves after landing, resolving to one 0–100 quality score per visit and attributing it to its {%source_id%}. That per-visit score is what separates a source sending real but disinterested pop visitors — a bidding decision — from one sending automated clicks, which is a blocking decision.
The pattern that matters most on MyBid is not a traffic shape at all, it is a feedback loop. The Optimizer improves a campaign by learning which sources produce the outcomes you send back, so its judgement is only as good as the events reaching it. When invalid clicks from a weak source touch your conversion pixel or land on a thank-you page, they register as positive signal, and the rule that was supposed to block that source can instead conclude it is performing and hold it — or the bidding can drift toward it. Automation is not required for this to bite: any source whose clicks reliably trip a shallow conversion event will look good to a system optimizing on shallow conversion events. Scoring the visit independently of the outcome is what breaks the loop, because a per-visit quality score cannot be manufactured by touching your pixel.
A second pattern is one Source ID spanning four very different formats. A MyBid source can deliver pop, push, native and banner volume, and those formats produce genuinely different session shapes from genuinely real people — a two-second pop visit is ordinary, the same two seconds on a native placement is not. A source judged against a single blended baseline will therefore look bad when its mix leans interruptive and fine when it leans native, regardless of how much invalid traffic it is actually sending. Reading the quality score, which already weighs network and device signals rather than session depth alone, is what makes a mixed-format source comparable to itself across formats.
The third is automation on interruptive inventory, where the format supplies its own cover. Pop and push clicks arrive without deliberate intent by design, so the heuristics that work on search or native — dwell, scroll, depth — condemn the entire channel if applied directly. What still separates a real low-intent visitor from an automated one is consistency: whether the connection characteristics, the device profile and the on-page activity agree with the operating system and browser the session claims to be running. MyBid reports the device, OS, browser and carrier behind its clicks, so a {%source_id%} whose declared population disagrees with how those visits actually behave is a readable signal rather than an inference.
What to watch on MyBid
This is the highest-value comparison on MyBid. Cross-reference the sources your rule-based Optimizer has left running against their ValidVisit score distribution. A {%source_id%} the Optimizer rates as performing while its visits score well below your campaign baseline is the signature of invalid clicks feeding the conversion signal — and it is precisely the case the platform cannot detect on its own, because the corrupted data is the data it is learning from.
{%source_id%}Because a MyBid source can serve pop, push, native and banner, break its scores down by the format the click came from before judging it. A source that scores acceptably on native but poorly on its pop volume is one you may want to keep with a format restriction rather than block outright. Blending the formats together hides both halves of that finding.
MyBid lets you bid down a source, blacklist it, or let the Optimizer handle it, and the score distribution tells you which fits. A source whose visits cluster at moderate scores is sending real people with weak intent — a Bid by source reduction is proportionate. One with a heavy tail of very low scores is sending automation, and a bid reduction just buys the same traffic cheaper. Reserve the blacklist for the second case.
The Optimizer’s Blocked sources tab is reviewable, and blocks made on outcome data alone can be wrong in the other direction — a source sending genuine visitors that simply did not convert on your offer. If a blocked {%source_id%} has a clean ValidVisit score history, the problem was your funnel or your targeting rather than the traffic, and unblocking it recovers inventory you were right to buy.
Pinpoint the bot publishers & placements in MyBid.
MyBid 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 MyBid tokens, not by creative (which says nothing about whether a click was human).
Bought as one MyBid line, a buy reads as a single number. Scored per sub-source, a spread like this illustration runs from 93 down to 20 — the worst is nearly all bots. That’s the leak a blended average hides.
Illustrative: MyBid traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
Bot / invalid-traffic score broken down by:
- Source ID
{%source_id%}
Per-click id: MyBid 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 MyBid sub-sources scored this way.
How ValidVisit attributes MyBid traffic
Each MyBid 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=mybid&utm_medium=pop&vv_click_id={%click_id%}&vv_publisher_id={%source_id%}&vv_creative_id={%creative_id%}| Token | MyBid macro | Maps to | Identifies |
|---|---|---|---|
| Click ID | {%click_id%} | click_id | click |
| Source ID | {%source_id%} | publisher_id | publisher |
| Creative ID | {%creative_id%} | creative_id | creative |
- MyBid macro
{%click_id%}- Maps to
- click_id
- Identifies
- click
- MyBid macro
{%source_id%}- Maps to
- publisher_id
- Identifies
- publisher
- MyBid macro
{%creative_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 sources on MyBid.
Scoring and attribution are the means — the point is cutting the MyBid 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 MyBid 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 MyBid source and zone via the network’s own tokens — so the bad traffic has an address, not just a headline percentage.
- Cut
Take the sources 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 MyBid and put your next dollar behind the traffic that converts.
MyBid traffic quality, answered.
Does ValidVisit block MyBid sources automatically, or is it manual?
It is manual. ValidVisit scores every visit and surfaces the {%source_id%} values with weak quality scores in its reports and dashboard. You then paste those Source IDs into the campaign’s blacklist under the campaign editor’s Targeting & Restrictions tab, or reduce their bids in the Bid by source section if the score profile argues for that instead. There is no automated push from ValidVisit into MyBid, and that is deliberate here: MyBid already has an automated blocker, and the value ValidVisit adds is an independent read on whether that blocker is making the right calls — which only works if the two systems stay separate.
MyBid’s Optimizer already blocks bad sources automatically. What does ValidVisit add?
A different input. The Optimizer decides from outcomes you report back — conversions, or whatever event you fire — which means invalid clicks that reach your pixel arrive as evidence that a source is working. ValidVisit scores the visit itself, before and independently of any outcome, using the network the click came from, the device behind it and how the session behaves on the page. So the two systems disagree in exactly the informative case: a source the Optimizer is holding because it appears to convert, whose visits score badly on arrival. That disagreement is the finding. Neither system replaces the other — you are comparing what a source produced against what it actually sent.
Which MyBid tokens give the most useful segmentation in ValidVisit?
The {%source_id%} carries the most weight, because it names the traffic source behind each click and it is the same unit the blacklist, the per-source bidding and the Optimizer all operate on — so the scores line up with every control you have without a translation step. The {%click_id%} gives per-click identity, ties a scored visit back to the MyBid click record, and is what a server-to-server conversion postback rides on. Adding {%creative_id%} lets you rule out the creative before you act on a source: if one unit draws weak clicks on a source while another draws valid traffic, the problem is more likely how that creative is being served than the source itself.
Detect fraud on other pop / pop-under networks
AdOperator
AdsCompass
Adsterra
DAO.ADFind the bots in your MyBid 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