Pop / Pop-underPushBanner / DisplayNative

Pop / Pop-under channel · judged Valid or Invalid

Which TrafficHunt ad spaces send bot traffic?

TrafficHunt traffic quality by ad space: every pop, push and banner visit judged Valid or Invalid before your test budget runs out on the bad ones.

Not ready? Estimate your invalid clicks →

validvisit · traffichunt cut-list

Exclude the bad ad space / referring domain in TrafficHunt

The buyer excludes the bad referring domains under Referers (TrafficHunt’s own push walkthrough builds its whitelist and blacklist there), lets the CPA optimizer stop Adspaces that fail their test budget, and asks support or the account manager to cut a specific [adspace] ID.

Where: Campaign targeting: Referers (include or exclude domains) and IP Ranges (include or exclude addresses and ranges); the CPA optimizer (CPA Goal plus a Cost per Adspace test budget) stops Adspaces automatically; no manual per-ad-space blacklist field is documented publicly

Controls in TrafficHunt’s campaign settings

✓ IP lists✓ OS✓ Browser✓ Language✓ Device✓ Connection

TrafficHunt macros mapped to report columns

2026-10-02

macros checked against TrafficHunt’s own docs

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 TrafficHunt ad spaces.

TrafficHunt is a self-serve network selling push, popunder, in-page push, banner, LastClick, email and native traffic, priced CPC for push and native and CPM for pop, banner and direct traffic, with a $50 minimum daily budget. Its unit of supply is the AdSpace: TrafficHunt documents [source_id] as the AdSpace ID the traffic came from, and its own CPA optimizer tests and stops traffic one Adspace at a time. ValidVisit captures [adspace], [camp_id] and [banner] on arrival, with [txn_id] as the click ID, and judges every visit Valid or Invalid with its evidence, giving each ad space its own invalid share.

Popunder ads open behind the user’s active window, so the format itself does nothing to filter automated page-loads. The pressure lands unevenly: one ad space can run mostly valid while another on similar inventory is dominated by automation, and a campaign average blurs the two together.

TrafficHunt’s CPA optimizer handles part of this on conversions alone: set a CPA Goal and a Cost per Adspace test budget, and in TrafficHunt’s example any Adspace with fewer than two conversions inside that budget is stopped. That catches dead spaces, but only after each spends its test budget, and conversions cannot tell a space full of bots from one full of real people on a slow-converting offer. A verdict per visit, attributed through [adspace], separates those two cases from the first visits instead of waiting on conversions.

What to watch on TrafficHunt

Ad space ([adspace]) invalid share

Rank [adspace] values by invalid share. A space well above your campaign baseline is a cut candidate before its test budget runs out.

Verdicts beside the CPA optimizer

When the optimizer stops an Adspace for too few conversions, check its invalid share. A mostly invalid space confirms the stop; a mostly valid one points at the offer or landing page instead.

CPC and CPM formats apart

Push is bought per click, pop and banner per thousand impressions. Run them as separate campaigns so [camp_id] keeps them apart, and read each ad space’s invalid share against how you pay for it.

02 / VERDICTS

What TrafficHunt lets you judge by.

Placement / widget

Invalid share broken down by:

Ad Space [adspace]

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

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

See your own TrafficHunt sub-sources judged this way.

03 / ATTRIBUTION

How ValidVisit attributes TrafficHunt traffic

Each TrafficHunt 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 TrafficHunt, ready for ValidVisit

https://yoursite.com/landing?utm_source=traffichunt&utm_medium=pop&vv_click_id=[txn_id]&vv_campaign_id=[camp_id]&vv_placement_id=[adspace]&vv_creative_id=[banner]

All TrafficHunt tracking tokens →

Token	TrafficHunt macro	Maps to	Identifies
Transaction/Click ID	`[txn_id]`	click_id	click
Campaign ID	`[camp_id]`	campaign_id	campaign
Ad Space	`[adspace]`	placement_id	placement
Banner (creative name)	`[banner]`	creative_id	creative

Transaction/Click ID

TrafficHunt macro: [txn_id]
Maps to: click_id
Identifies: click

Campaign ID

TrafficHunt macro: [camp_id]
Maps to: campaign_id
Identifies: campaign

Ad Space

TrafficHunt macro: [adspace]
Maps to: placement_id
Identifies: placement

Banner (creative name)

TrafficHunt macro: [banner]
Maps to: creative_id
Identifies: creative

Macros checked against TrafficHunt’s own documentation on 2026-10-02. TrafficHunt docs

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

FAQ

TrafficHunt traffic quality, answered.

How do I exclude traffic sources in TrafficHunt?

TrafficHunt documents three levers. In campaign targeting, Referers lets you include or exclude domains (its own push walkthrough uses this to whitelist strong sources and blacklist weak sites), and IP Ranges includes or excludes addresses and ranges. For ad spaces, the CPA optimizer stops any Adspace that misses its test budget. Its public pages do not document a manual per-ad-space blacklist field; ask support or your account manager.

Where does conversion tracking go?

Under Tracking Codes in the account menu, TrafficHunt gives you a postback link keyed on [txn_id], and it says [txn_id] must be in every tracking link of every campaign. The CPA optimizer only switches on once a postback is configured, and ValidVisit records the same [txn_id] on each visit, so a verdict and a conversion line up on one click.

Can I dispute invalid traffic with TrafficHunt?

TrafficHunt’s advertiser terms accept a report of fraud leads no later than 7 days after the billing period ends, listing the fraud click IDs, why each was classed as fraud, and the deduction requested; after that window its own stats stand. ValidVisit files nothing with TrafficHunt; each Invalid visit keeps its [txn_id] and evidence for your own report.

Does TrafficHunt filter bots for advertisers?

Its publisher terms say it will not pay publishers for impressions or clicks it deems invalid or fraudulent, and its blog tells advertisers to monitor each source individually. Its public pages do not describe an advertiser-side bot filter, so the per-visit check is yours to run.