7Search PPC tracking tokens & macros
7Search PPC carries 'search' and 'PPC' in its name, but the macro set tells a broader story: the same four tokens cover text, banner, native, in-page push, and popunder inventory all running through one account, and the network says itself that its text ads are not search ads. That's an unusual spread for something with 'PPC' in the name, and it means a visit landing on your page could have come from a text ad or a popunder 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 judge each visit Valid or Invalid, with its evidence.
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, the traffic source or publisher ID that sent the visitor, 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 text-ad click and a popunder visit 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 invalid share for '7Search PPC' as a whole is close to meaningless — the formats are bought differently (popunder on CPM only, the others on CPC or CPM), and blending them into one number just averages away the signal. Splitting verdicts 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 in-page push. From there, though, ValidVisit's role ends at the report: it never pauses a source or a format for you, and 7Search PPC's campaign editor has no self-serve blacklist field, so cutting a bad {source_id} means emailing it to 7Search PPC's customer support, while dropping a format means pausing that campaign yourself.
7Search PPC macro → ValidVisit param
| 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 |
- 7Search PPC macro
{click_id}- ValidVisit param
vv_click_id- Example
- abc123xyz
- 7Search PPC macro
{campaign_id}- ValidVisit param
vv_campaign_id- Example
- 123456
- 7Search PPC macro
{source_id}- ValidVisit param
vv_publisher_id- Example
- pub_42
* required for 7Search PPC attribution.
Ready-to-use 7Search PPC tracking URL
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}Append these params to your landing-page URL — 7Search PPC fills the macros at click time, so every visit arrives attributed and ready to judge. No funnel hop.
See which 7Search PPC sources send bots.
- Every visit judged Valid or Invalid, worst source first.
- Attributed through the 7Search PPC tokens above, down to the placement.
- Works beside your tracker, with nothing added to the click path.
What 7Search PPC tokens let you break bots down by
- Source ID
Carries a per-click id, stored with each visit so a verdict traces back to the click.
- IP exclusionnot offered
- Device targetingdocumented
- OS targetingdocumented
- Browser targetingnot offered
- Connection typenot offered
- Languagenot offered
Tokens last verified against 7Search PPC’s docs on 2026-10-02.
The 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").
7Search PPC tracking token FAQs
Why does 7Search PPC need an ad-format macro if it's a PPC network?+
Because 7Search PPC sells five formats — text, banner, native, in-page push, and popunder — not just pay-per-click text ads, and popunder is sold on CPM only. {ad_format} tells you which of the five actually served a given visit, which a click-only macro set wouldn't capture.
What's required for ValidVisit to attribute a 7Search PPC visit?+
{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 verdict actionable.
Does ValidVisit exclude bad sources on 7Search PPC automatically?+
No. ValidVisit judges and reports on {source_id} and {ad_format} combinations, but excluding a source is a manual step: 7Search PPC's campaign editor has no blacklist field, so you email the sources to its customer support team.
Tracking tokens for other native networks
Judge every 7Search PPC visit — and find the fake ones.
See which 7Search PPC publishers and placements send real buyers vs. bots.
Join the waitlist with just your email · 7-day trial at launch
One script · no cookies · no device IDs · raw IP never stored