7Search PPC brands itself as a search network, but the macro set tells a broader story: the same four tokens cover search, native, push, pop, and banner inventory all running through one account. That's an unusual spread for something with 'PPC' in the name, and it means a click landing on your page could have come from a search results page or a pop unit with equally little to distinguish them by default. Appending the four macros below fixes that, giving ValidVisit the source and format needed to attribute and score each visit 0-100.
Cross-check any macro against the network’s official documentation. 7Search PPC official docs →
{click_id} is the required macro, 7Search PPC's unique click identifier and the value ValidVisit needs present to attribute a visit to anything at all. {source_id} is the publisher-level token, naming the actual property or partner that sent the click, and it's the id you'll eventually sort quality by. {campaign_id} ties the click back to your specific buy. The one worth pausing on is {ad_format} — because 7Search PPC spans five different formats under one macro set, {ad_format} is what tells you which of them actually produced a given visit, and without it a search click and a pop click look identical in your reports. All four are plain URL parameters on your landing page link, filled in by 7Search PPC's ad server before the click reaches you, with no extra tracking script required.
Format breadth is exactly why a single quality score for '7Search PPC' as a whole is close to meaningless — search traffic and pop traffic have different baseline behavior, different bot patterns, and different acceptable click volumes, and blending them into one number just averages away the signal. Splitting scores by {source_id} and {ad_format} together is what lets you see, for instance, that a source performing fine on native is quietly producing garbage on push. From there, though, ValidVisit's role ends at the report: it never pauses a source or a format for you, so cutting a bad {source_id} or excluding a format from your buy is something you go do directly inside 7Search PPC's campaign settings.
| Token | 7Search PPC macro | ValidVisit param | Example |
|---|---|---|---|
| Click ID *click | {click_id} | vv_click_id | abc123xyz |
| Campaign IDcampaign | {campaign_id} | vv_campaign_id | 123456 |
| Source IDpublisher | {source_id} | vv_publisher_id | pub_42 |
| Ad Formatad | {ad_format} | vv_ad_id | 456789 |
{click_id}vv_click_id{campaign_id}vv_campaign_id{source_id}vv_publisher_id{ad_format}vv_ad_id* required for 7Search PPC attribution.
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}Append these params to your landing-page URL — 7Search PPC fills the macros at click time, so every visit arrives attributed and ready to score. No funnel hop.
The 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").
Because 7Search PPC also runs native, push, pop, and banner inventory alongside search, not just PPC search results. {ad_format} tells you which of the five actually served a given click, which a search-only macro set wouldn't capture.
{click_id}. It's the network's unique click identifier, and ValidVisit needs it on the URL to attribute the click at all; {source_id}, {campaign_id}, and {ad_format} add the context that makes the score actionable.
No. ValidVisit scores and reports on {source_id} and {ad_format} combinations, but pausing or excluding a source is a manual step you take inside your own 7Search PPC dashboard.
See which 7Search PPC publishers and placements send real buyers vs. bots.
Free trial at launch · just your email
One script · no cookies · no fingerprinting · raw IP never stored