How to check 7Search PPC traffic quality: every visit scored 0–100 and pinned to the search sub-source that sent it — worst first, with the evidence to act on.
domain in 7Search PPCThe buyer collects bad sub-source IDs via the {subid} URL macro or the referrer-IDs report, then emails the list of domains to 7SearchPPC support, who apply the blacklist account-side ("If you want to blacklist a specific domain, email our customer support team").
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and 7Search PPC supports OS and device type targeting. The segments we flag are segments you can exclude.
See which 7Search PPC publishers, placements and sub-sources send real clicks versus bots, attributed via 7Search PPC’s own tracking tokens and scored 0–100 per source.
7Search PPC 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 7Search PPC tokens, not by creative (which says nothing about whether a click was human).
7Search PPC traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
Bot / invalid-traffic score broken down by:
{source_id}Per-click id: 7Search PPC 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 7Search PPC sub-sources scored this way.
Each 7Search PPC 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=7searchppc&utm_medium=search&vv_click_id={click_id}&vv_campaign_id={campaign_id}&vv_publisher_id={source_id}&vv_ad_id={ad_format}| Token | 7Search PPC macro | Maps to | Identifies |
|---|---|---|---|
| Click ID | {click_id} | click_id | click |
| Campaign ID | {campaign_id} | campaign_id | campaign |
| Source ID | {source_id} | publisher_id | publisher |
| Ad Format | {ad_format} | ad_id | ad |
{click_id}{campaign_id}{source_id}{ad_format}Every visit 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 visit — 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.
Every 7Search PPC click is weighed against 100+ independent data points spanning the network it came from, the device behind it and how the visitor behaves — combined into a single 0–100 quality score so real humans pass and bots stand out.
Yes. Using 7Search PPC's own tracking tokens, ValidVisit attributes each scored click to the publisher, placement and sub-source, so invalid traffic is pinned to the exact sub-source — which you can then exclude manually in 7Search PPC.
No. Detection runs from one lightweight script — no extra hop, no link rewriting, no change to your 7Search PPC destination URLs.
See which campaigns and publishers send real, converting traffic vs bots — every visit scored 0–100.
Free trial at launch · just your email
One script · raw IP never stored · GDPR legitimate-interest basis