Revcontent tracking tokens & macros
Revcontent sends native clicks across thousands of publisher widgets, so the same Boost campaign can perform brilliantly on one site and bleed budget on another. Appending these macros to your landing-page URL lets ValidVisit attribute every click to the exact widget / site it came from, then score that click 0-100 for traffic quality.
On Revcontent, the macro that matters most for cleanup is {widget_id}, which names the specific publisher widget the click came from, paired with {boost_id} to tie it back to the right Boost campaign. The required {conversion_uuid} is Revcontent's own click id (rc_uuid), so every visit lands with a unique fingerprint already attached, and you can add {content_id} and {adv_targets} when you want to see which creative and targeting combination is feeding a given widget. Note that Revcontent uses curly-brace macros like `{widget_id}` rather than all-caps tokens, and they go straight into your URL as query parameters, so no funnel hop or extra tracking hop is needed.
This per-widget granularity is what turns a noisy report into an action. Once each click is tied to its widget / site, ValidVisit flags the widgets sending invalid traffic and bots, and you take that list into Targeting → widget & site blacklist and block the offenders yourself. ValidVisit only reports and scores after the click arrives; it never blocks or auto-excludes anything, and the bad traffic is on the individual publisher widget, not on Revcontent. You stay in control of which sources you keep paying for.
| Token | Revcontent macro | ValidVisit param | Example |
|---|---|---|---|
| Campaign (Boost) ID *campaign | {boost_id} | vv_campaign_id | 123456 |
| Content (Creative) IDcreative | {content_id} | vv_creative_id | 7890123 |
| Widget IDpublisher | {widget_id} | vv_publisher_id | 84521 |
| Advertiser Targetsplacement | {adv_targets} | vv_placement_id | mobile |
| Click ID (rc_uuid) *click | {conversion_uuid} | vv_click_id | a1b2c3d4-5678-90ab-cdef-1234567890ab |
- Revcontent macro
{boost_id}- ValidVisit param
vv_campaign_id- Example
- 123456
- Revcontent macro
{content_id}- ValidVisit param
vv_creative_id- Example
- 7890123
- Revcontent macro
{widget_id}- ValidVisit param
vv_publisher_id- Example
- 84521
- Revcontent macro
{adv_targets}- ValidVisit param
vv_placement_id- Example
- mobile
- Revcontent macro
{conversion_uuid}- ValidVisit param
vv_click_id- Example
- a1b2c3d4-5678-90ab-cdef-1234567890ab
* required for Revcontent attribution.
https://yoursite.com/landing?utm_source=revcontent&utm_medium=native&vv_campaign_id={boost_id}&vv_creative_id={content_id}&vv_publisher_id={widget_id}&vv_placement_id={adv_targets}&vv_click_id={conversion_uuid}ValidVisit flags the bad widget / site; block them in Revcontent's targeting blacklist.
Revcontent tracking token FAQs
Which Revcontent token identifies the publisher source I should block?
{widget_id} identifies the individual widget, and combined with the site it resolves to a specific widget / site placement. That is the unit ValidVisit scores, so when a widget is sending invalid traffic you can find it by its {widget_id} and add it to your blacklist.
Do I need a funnel hop or tracking script to use these macros?
No. The Revcontent macros, including the required {boost_id} and {conversion_uuid}, are just URL query parameters. Revcontent fills them in at click time, so there is no funnel hop, pixel hop, or extra script involved.
Where do I add the macros, and where do I actually exclude bad widgets?
Add the macros to your campaign's landing-page URL on the Boost so they pass through with every click. ValidVisit then reports which widgets are sending bots and invalid traffic; you exclude them manually in Revcontent under Targeting → widget & site blacklist.
Track Revcontent clicks — and catch the fake ones.
See which Revcontent publishers and placements send real, converting traffic vs. bots.
Free trial at launch · lock in early-access pricing
One script · raw IP never stored · GDPR legitimate-interest basis