Pop / Pop-under

Pop / Pop-under channel · judged Valid or Invalid

Which Yeesshh zones send bot traffic?

ValidVisit judges every Yeesshh visit Valid or Invalid and pins it to the zone that sent it, worst first.

Not ready? Estimate your invalid clicks →

validvisit · yeesshh cut-list

Exclude the bad pubfeed.subid in Yeesshh

The buyer pastes the bad combinations into the campaign’s blacklist field in "TQ & Analytics", one per line in the format pubfeed.subid (e.g. 72179.69641); a Whitelist-Only mode accepts the same format, and an optional auto-blacklister blocks any feed SubID that reaches N clicks with zero conversions.

Where: Identify bad sources in Dashboard > Reports > Reports by Campaign with breakdown by "feed"; then Edit Campaign > scroll to the "TQ & Analytics" section, which holds the Blacklist / Whitelist-Only fields

Controls in Yeesshh’s campaign settings

✓ OS✓ Browser✓ Language✓ Device✓ Connection

Yeesshh macros mapped to report columns

sub-source levels judged

no-hop

one script, nothing added to the click path

Valid / Invalid

a verdict on every visit

01 / SIGNAL

How bot traffic slips in through Yeesshh zones.

Yeesshh is a pop / pop-under channel — exactly where invalid traffic concentrates. See which Yeesshh publishers, placements and sub-sources send real clicks versus bots, attributed via Yeesshh’s own tracking tokens and judged Valid or Invalid per source.

02 / VERDICTS

What Yeesshh lets you judge by.

Publisher / site / zone

Invalid share broken down by:

Publisher Feed ID {pubfeed}

Placement / widget

Invalid share broken down by:

Publisher Feed SubID {subid}

Per-click id: Yeesshh passes a unique click id, and ValidVisit stores it with each visit, so a verdict traces back to the click in Yeesshh’s own reports.

Compare bot & invalid-traffic breakdown across every ad network →

See your own Yeesshh sub-sources judged this way.

03 / ATTRIBUTION

How ValidVisit attributes Yeesshh traffic

Each Yeesshh macro maps to a normalized parameter, so every judged visit is pinned to the right campaign, creative and publisher.

validvisit · tracking url

Tracking URL for Yeesshh, ready for ValidVisit

https://yoursite.com/landing?utm_source=yeesshh&utm_medium=pop&vv_click_id={conversion}&vv_publisher_id={pubfeed}&vv_placement_id={subid}&vv_ad_id={banner}&vv_keyword={keyword}

All Yeesshh tracking tokens →

Token	Yeesshh macro	Maps to	Identifies
Click ID	`{conversion}`	click_id	click
Publisher Feed ID	`{pubfeed}`	publisher_id	publisher
Publisher Feed SubID	`{subid}`	placement_id	placement
Ad ID	`{banner}`	ad_id	ad
Keyword	`{keyword}`	keyword	keyword

Click ID

Yeesshh macro: {conversion}
Maps to: click_id
Identifies: click

Publisher Feed ID

Yeesshh macro: {pubfeed}
Maps to: publisher_id
Identifies: publisher

Publisher Feed SubID

Yeesshh macro: {subid}
Maps to: placement_id
Identifies: placement

Ad ID

Yeesshh macro: {banner}
Maps to: ad_id
Identifies: ad

Keyword

Yeesshh macro: {keyword}
Maps to: keyword
Identifies: keyword

Macros not yet checked against Yeesshh’s documentation. Yeesshh docs

The verdict works the same way on every network. ValidVisit never changes your Yeesshh account: you make the exclusion there yourself. How the verdict works →

FAQ

Yeesshh traffic quality, answered.

How does ValidVisit detect invalid Yeesshh traffic?

Every Yeesshh visit is checked against 100+ independent data points spanning the network it came from, the device behind it and the page it loaded. One thing a real visitor cannot produce makes it Invalid; otherwise it is Valid, with its evidence either way.

Can I see which Yeesshh publishers send bots?

Yes. Using Yeesshh's own tracking tokens, ValidVisit attributes each judged visit to the publisher, placement and sub-source, so invalid traffic is pinned to the exact sub-source — which you can then exclude manually in Yeesshh.

Does it require a funnel hop on my Yeesshh links?

No. Detection runs from one lightweight script — no extra hop, no link rewriting, no change to your Yeesshh destination URLs.