Which 7Search PPC domains send bot traffic?
7Search PPC traffic quality by publisher source: every visit judged Valid or Invalid, with the sources worth sending to support for a blacklist.
domain in 7Search PPCThe buyer collects bad source IDs via the {source_id} URL macro or by requesting the Referrer IDs Report, then emails the list to 7SearchPPC support ("If you want to blacklist a specific domain, email our customer support team").
How bot traffic slips in through 7Search PPC domains.
7Search PPC is a self-serve ad network that began as a search engine platform and now sells text, banner, native, in-page push and popunder ads on publisher websites, on CPC or CPM pricing (popunder is CPM only). Despite the name, its text ads are not search ads: by 7Search PPC’s own description they appear on websites as people browse content, not on search results pages, and the campaign editor targets by country, device and operating system rather than by keyword. Its blog says the partners behind that traffic include RTB exchanges, directories, large private site owners and smaller ad networks, and that it cannot disclose all of their names. The {source_id} macro identifies the traffic source or publisher behind each click, which is the dimension that matters for cleaning up spend.
7Search PPC’s terms state that it does not warrant the nature, intent or quality of clicks and impressions and cannot guarantee the absence of invalid, low-quality or fraudulent traffic; advertisers are expected to monitor results and optimise. Its FAQ says publisher accounts are suspended when its algorithm detects inappropriate or bot traffic, a check that runs on 7Search PPC’s side.
What you can see yourself is limited. The advertiser Statistics page segments by date, campaign, country, state, city, device and operating system, with filters for ad format, campaign and date; the user guide lists no breakdown by source. The source reaches you through the {source_id} macro on your own URL, so a verdict attributed to {source_id} is how a source sending invalid visits becomes visible.
What to watch on 7Search PPC
{source_id}) IVT concentrationSegment your report by {source_id}. A single source driving a disproportionate share of click volume with an invalid share well above your campaign baseline is the one to act on. Collect those sources for a blacklist request before their volume swamps the rest of the buy.
A 7Search PPC campaign is created for one ad format: text, banner, native, in-page push or popunder. Pass {ad_format} alongside {source_id} so a source that appears in several of your campaigns can be compared format by format. Popunder is sold on CPM only, so there you pay per impression rather than per click.
The campaign editor targets by GEO, device (desktop/laptop, tablet, mobile) and operating system (Android, Apple, Linux, Windows). There is no source list to tick, so a source judged Invalid goes into a blacklist request, while a valid but weak segment is handled by narrowing those three settings or lowering the bid.
What 7Search PPC lets you judge by.
Invalid share broken down by:
- Source ID
{source_id}
Per-click id: 7Search PPC passes a unique click id, and ValidVisit stores it with each visit, so a verdict traces back to the click in 7Search PPC’s own reports.
Compare bot & invalid-traffic breakdown across every ad network →See your own 7Search PPC sub-sources judged this way.
How ValidVisit attributes 7Search PPC traffic
Each 7Search PPC 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=7searchppc&utm_medium=native&vv_click_id={click_id}&vv_campaign_id={campaign_id}&vv_publisher_id={source_id}| 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 |
- 7Search PPC macro
{click_id}- Maps to
- click_id
- Identifies
- click
- 7Search PPC macro
{campaign_id}- Maps to
- campaign_id
- Identifies
- campaign
- 7Search PPC macro
{source_id}- Maps to
- publisher_id
- Identifies
- publisher
Macros checked against 7Search PPC’s own documentation on 2026-10-02. 7Search PPC docs
The verdict works the same way on every network. ValidVisit never changes your 7Search PPC account: you make the exclusion there yourself. How the verdict works →
7Search PPC traffic quality, answered.
How do I blacklist a source or domain in 7Search PPC?
Not in the campaign UI: the campaign editor and user guide expose no self-serve blacklist field. 7Search PPC’s own guidance is to email its customer support team to blacklist a specific domain. Collect the bad sources from your ValidVisit report, or request 7Search PPC’s Referrer IDs Report, and email them to customer support.
Which 7Search PPC macros give the most useful segmentation in ValidVisit?
{source_id} does the most work: 7Search PPC defines it as the traffic source or publisher ID that sent the visitor. {ad_format} carries the format of the ad clicked: banner, native, popunder, in-page push or text. {click_id} gives per-click identity and {campaign_id} ties each visit to its campaign. The same macro table also documents {browser}, {country}, {state}, {city}, {device}, {os} and {cost}.
Should I blacklist every 7Search PPC source that converts poorly?
No. Weak conversions alone don’t separate a bot-heavy source from a source of real but uninterested visitors. The verdict draws that line: a source whose visits are largely judged Invalid is the one to send to support for a blacklist, while a source of valid visits that rarely convert is a bid and targeting problem you fix inside 7Search PPC.
Adskeeper
Kadam
MediaGo
MGID
NewsBreak Ads
OutbrainWeighing a blocker for native traffic? How ValidVisit compares to Opticks, PureGuard and Adscore.
Find the bots in your 7Search PPC spend.
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