spot / placement in TrafficJunkyValidVisit flags the bad spot / placement; turn it off in TrafficJunky's campaign.
TrafficJunky is one of the largest self-serve banner advertising networks on the open web, with an inventory built heavily on entertainment and adult publisher supply. That combination — high-volume banner impressions distributed across a wide range of publisher sites — creates real IVT exposure worth measuring. The threat is not the network itself but specific publisher sites and spot placements within its supply where automated click generation tends to concentrate. ValidVisit attaches a lightweight script to your landing page and, for every click that arrives, weighs 100+ independent data points — the network the click came from, the device sitting behind it, and the way the visitor actually behaves — into a single 0–100 quality score, then attributes that score to the exact {SiteName} and {SpotID} that generated it. The result is a clear picture of which corners of TrafficJunky's inventory are delivering genuine audiences and which are padding your click counts.
https://yoursite.com/landing?utm_source=trafficjunky&utm_medium=banner&vv_click_id={ACLID}&vv_campaign_id={CampaignID}&vv_campaign_name={CampaignName}&vv_ad_id={AdID}&vv_creative_id={BanID}&vv_publisher_id={SiteName}&vv_placement_id={SpotID}&vv_keyword={Keyword}On open banner inventory like TrafficJunky, the clearest IVT signal often has nothing to do with what the visitor does on the page — it shows up in where the click came from. Automated click generators, whether publisher-side scripts or third-party bot operators, lean on rented server farms and cloud hosting because running volume at scale is far cheaper than from a real residential connection. ValidVisit looks at the origin of every arriving click as part of its scoring, and clicks that trace back to bulk hosting infrastructure on a display campaign are a dependable sign that something other than a human did the clicking.
A second pattern specific to banner-heavy supply is proxy and VPN routing used to satisfy geo-targeting parameters. Advertisers bidding on Tier-1 geos can attract clicks that originate on cheap infrastructure but exit through residential proxy nodes in the target country, making them look geographically valid. ValidVisit factors that kind of disguised routing into the same quality score and ties each low-scoring click to its {SiteName} and {SpotID} values, giving you the specific exclusion data rather than an aggregate waste estimate.
Where the connection alone is inconclusive, behavior fills in the rest of the story. Genuine visitors load the page, linger, and interact; automated traffic tends to register the click and then go quiet. By blending more than a hundred such signals across network, device and on-page behavior into one 0–100 figure per click, ValidVisit separates clicks where a real human session followed from those where the click landed and nothing else ever happened. When {SpotID} placements show a consistent gap between click volume and the share of clicks that turn into real sessions, that placement warrants manual review and potential exclusion from your TrafficJunky campaign.
A well-distributed TrafficJunky campaign sees clicks spread across many publisher sites. When a single {SiteName} value accounts for a disproportionate share of clicks but produces little measurable post-click activity — few clicks turning into real sessions, minimal session depth — that site is a candidate for manual exclusion via TrafficJunky's site blacklist, regardless of its face-value CTR.
Quality varies considerably between spot placements even within the same publisher. ValidVisit maps every click's 0–100 quality score to its {SpotID}, letting you compare banner positions side by side. Placements where the distribution skews heavily toward low-scoring clicks — the ones traced to bulk hosting or disguised routing — warrant pausing, even if the campaign's blended score looks acceptable.
Organic display audiences reach your landing page from everyday residential and mobile connections. When a particular {SiteName} drives clicks that land disproportionately from server-farm and cloud-hosting infrastructure, it is a strong indicator of publisher-side automation rather than genuine user interest. ValidVisit surfaces this breakdown per site and per spot so you can act on the specific supply source.
ValidVisit registers whether a click actually turns into a real, active browser session. Spot placements where click counts are substantial but the share that becomes a genuine session is markedly lower indicate that many of those clicks never produced real human activity — consistent with automated click generation. Cross-reference these {SpotID} values against your session analytics to confirm the pattern before excluding.
Each TrafficJunky macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
| Token | TrafficJunky macro | Maps to | Identifies |
|---|---|---|---|
| Click ID | {ACLID} | click_id | click |
| Campaign ID | {CampaignID} | campaign_id | campaign |
| Campaign Name | {CampaignName} | campaign_name | campaign |
| Ad ID | {AdID} | ad_id | ad |
| Banner / Creative ID | {BanID} | creative_id | creative |
| Publisher Site Name | {SiteName} | publisher_id | publisher |
| Spot / Placement ID | {SpotID} | placement_id | placement |
| Keyword | {Keyword} | keyword | keyword |
{ACLID}{CampaignID}{CampaignName}{AdID}{BanID}{SiteName}{SpotID}{Keyword}TrafficJunkyitself 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 TrafficJunky tokens, not by creative (which says nothing about whether a click was human).
Illustrative example — TrafficJunky traffic scored 0–100 per sub-source, worst first.
See your own TrafficJunky sub-sources scored this way.
Bot / invalid-traffic score broken down by:
{SiteName}Name of the publisher site that triggered the ad.Bot / invalid-traffic score broken down by:
{SpotID}Identifier of the ad spot / placement position where the ad was shown.Per-click id: TrafficJunky passes a unique click id, so we also run velocity, deduplication and repeat-source checks on every click.
Compare bot & invalid-traffic breakdown across every ad network →Every click is weighed against more than a hundred independent data points and reduced to a single, sortable 0–100 quality score.
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.
The detection model is ours and stays that way. What you get is a clear verdict on every click — not a single brittle rule you can game, and not an unexplained number you can't act on.
Every verdict maps to the campaign, publisher and placement that sent the click — so you know exactly which source to cut.
The two most diagnostic macros for IVT analysis are {SiteName} (the publisher domain or site ID that served your banner) and {SpotID} (the specific ad placement within that site). Together they let ValidVisit score at the exact intersection of publisher and position. Adding {ACLID} — TrafficJunky's unique click identifier — is also useful for deduplication and for cross-referencing individual clicks in TrafficJunky's own reporting. {CampaignID} and {CampaignName} are optional if you are running multiple campaigns and want to segment IVT data per campaign in your ValidVisit dashboard.
ValidVisit is a scoring and reporting tool — it does not push exclusions to the network automatically. Once you identify publisher sites or spot placements with a consistently poor score profile (a large share of clicks from bulk hosting, few clicks forming real sessions, or both), you take that {SiteName} list into TrafficJunky's campaign settings and add those sites to your site blacklist manually. For {SpotID}-level exclusions, TrafficJunky supports spot-level blocking in its ad manager. This keeps the decision in your hands and gives you a clear audit trail for any campaign changes you make.
No. ValidVisit's script runs on your landing page after the click has already been counted by TrafficJunky's system. It does not sit in the click path, does not modify click traffic in transit, and does not interfere with TrafficJunky's own reporting or billing reconciliation. You are adding a parallel measurement layer on your side of the click — one that gives you publisher- and placement-level IVT visibility that TrafficJunky's aggregate filtering does not expose to advertisers.
See which campaigns and publishers send real, converting traffic vs bots — every click scored 0–100.
Free trial at launch · lock in early-access pricing
One script · raw IP never stored · GDPR legitimate-interest basis