Judge every MyBid visit by {%source_id%}. See which sources are teaching the Optimizer from invalid clicks before it moves budget toward them.
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).
MyBid runs pop, push, native and banner inventory through one 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 served. It gives buyers three levers over a source: a manual black and white list under Targeting & Restrictions, a per-source bid 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. None of them tells you which lever a source deserves, because the platform’s view of a source is built from the outcomes you report back. A verdict attributed to {%source_id%} measures the input instead: it 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 a feedback loop. The Optimizer learns 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 meant to block that source can instead hold it — or bidding can drift toward it. Any source whose clicks reliably trip a shallow conversion event will look good to a system optimizing on shallow conversion events. A verdict can’t be manufactured by touching your pixel, which is what breaks the loop.
A second pattern is one Source ID spanning four formats. A MyBid source can deliver pop, push, native and banner volume, and those formats produce different session shapes from real people — a two-second pop visit is ordinary, the same two seconds on a native placement is not. A source judged against one blended baseline looks bad when its mix leans interruptive and fine when it leans native, whatever it is actually sending.
The highest-value comparison on MyBid. A {%source_id%} the Optimizer treats as performing while its invalid share runs well above your campaign baseline is the signature of invalid clicks feeding the conversion signal — the case the platform can’t detect on its own, because the corrupted data is what it learns from.
{%source_id%}Break a source’s verdicts down by the format the click came from before judging it. A source judged valid on native but invalid on its pop volume may be worth keeping with a format restriction rather than blocking outright.
A source whose visits are mostly judged Valid but convert poorly is sending real people with weak intent — a Bid by source reduction is proportionate. One with a high invalid share is sending automation, and a lower bid just buys the same traffic cheaper; that is the case for the blacklist.
Blocks made on outcome data alone can be wrong the other way: a source sending genuine visitors that simply didn’t convert on your offer. If a {%source_id%} in the Blocked sources tab has a clean verdict history, the problem was your funnel or targeting, and unblocking it recovers inventory worth buying.
Invalid share broken down by:
{%source_id%}Per-click id: MyBid passes a unique click id, and ValidVisit stores it with each visit, so a verdict traces back to the click in MyBid’s own reports.
Compare bot & invalid-traffic breakdown across every ad network →See your own MyBid sub-sources judged this way.
Each MyBid macro maps to a normalized parameter, so every judged visit 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 |
{%click_id%}{%source_id%}{%creative_id%}Macros not yet checked against MyBid’s documentation. MyBid docs
The verdict works the same way on every network. ValidVisit never changes your MyBid account: you make the exclusion there yourself. How the verdict works →
Paste the Source IDs into the campaign’s Black/White Lists under the campaign editor’s Targeting & Restrictions tab, or lower their bids in the Bid by source section if the verdicts point to weak intent rather than automation. Sources the Optimizer blocked on its own are listed, and can be unblocked, in its Blocked sources tab.
A different input. The Optimizer decides from the outcomes you report back, so invalid clicks that reach your pixel arrive as evidence that a source is working. ValidVisit judges the visit itself, independently of any outcome. The two disagree in exactly the informative case — a source the Optimizer holds because it appears to convert, whose visits are judged invalid on arrival. That disagreement is the finding.
{%source_id%} carries the most weight: it names the traffic source and is the unit the blacklist, per-source bidding and the Optimizer all operate on. {%click_id%} gives per-click identity, ties a judged visit back to the MyBid click record, and is what a server-to-server conversion postback rides on. {%creative_id%} lets you rule out the creative before acting on a source.
IP, operating system and OS version, browser and browser version, language, device and carrier/connection targeting are all documented.
Weighing a blocker for pop / pop-under traffic? How ValidVisit compares to PureGuard, Adscore and Tracker bot filtering.
See which publishers and placements send real buyers vs bots — every visit judged Valid or Invalid, worst first.
Join the waitlist with just your email · 7-day trial at launch
One script · no cookies · no device IDs · raw IP never stored