MediaGo tracking tokens & macros
${TRACKING_ID} is the macro that makes MediaGo attribution possible — it is the unique click identifier MediaGo drops into your landing page URL and expects back on any server-to-server postback. Paired with ${CAMPAIGN_ID}, it lets ValidVisit tie every visit to a specific campaign and score it 0-100 for bot and invalid-traffic risk before you decide anything about spend. Add a handful of these macros once to your destination URLs and MediaGo fills in the real values automatically on each click, no extra tracking hop required.
Cross-check any macro against the network’s official documentation. MediaGo official docs →
MediaGo writes its macros in an all-caps, dollar-brace syntax — ${CAMPAIGN_ID}, ${TRACKING_ID}, ${SITE_ID} — a format that is easy to mistype if you are used to the plain curly-brace or square-bracket conventions other native networks use, so copy them exactly as MediaGo's placement tool generates them. Two tokens are required: ${CAMPAIGN_ID} to anchor the visit to a campaign and ${TRACKING_ID}, MediaGo's per-click identifier used for server-to-server postback matching. The token worth watching closest is ${SITE_ID}, which names the actual publisher placement running your native ad — the unit one level below the campaign where quality actually varies. ${AD_ID} and ${ASSET_ID} identify the specific ad and creative asset clicked, useful if a campaign is running several creative variants at once, and ${CAMPAIGN_NAME} just carries a human-readable label through for reporting rather than a raw numeric ID.
Native placements on MediaGo run inside publisher content feeds, and feed quality swings a lot from one site to the next — a widget buried in a low-effort content farm behaves nothing like one sitting in a legitimate publisher's article page. Once ${SITE_ID} is attached to every visit, ValidVisit can separate those two outcomes instead of averaging them into one campaign-level number that hides which placements are actually worth the spend. Nothing ValidVisit finds gets applied automatically inside MediaGo, though — the platform's role stops at detecting, scoring, and attributing each visit, plus surfacing which site IDs are driving invalid traffic. Turning that into fewer wasted impressions is on you: log into your MediaGo dashboard, pull the flagged ${SITE_ID} values, and exclude those placements from the campaign yourself. ValidVisit hands you the evidence; MediaGo's own controls are where the exclusion actually happens.
MediaGo macro → ValidVisit param
| Token | MediaGo macro | ValidVisit param | Example |
|---|---|---|---|
| Campaign ID *campaign | ${CAMPAIGN_ID} | vv_campaign_id | 123456 |
| Campaign Namecampaign | ${CAMPAIGN_NAME} | vv_campaign_name | spring_sale |
| Ad IDad | ${AD_ID} | vv_ad_id | 7891011 |
| Site IDpublisher | ${SITE_ID} | vv_publisher_id | 84521 |
| Tracking ID (Click ID) *click | ${TRACKING_ID} | vv_click_id | a1b2c3d4e5 |
| Asset ID (Creative)creative | ${ASSET_ID} | vv_creative_id | 7890123 |
- MediaGo macro
${CAMPAIGN_ID}- ValidVisit param
vv_campaign_id- Example
- 123456
- MediaGo macro
${CAMPAIGN_NAME}- ValidVisit param
vv_campaign_name- Example
- spring_sale
- MediaGo macro
${AD_ID}- ValidVisit param
vv_ad_id- Example
- 7891011
- MediaGo macro
${SITE_ID}- ValidVisit param
vv_publisher_id- Example
- 84521
- MediaGo macro
${TRACKING_ID}- ValidVisit param
vv_click_id- Example
- a1b2c3d4e5
- MediaGo macro
${ASSET_ID}- ValidVisit param
vv_creative_id- Example
- 7890123
* required for MediaGo attribution.
Ready-to-use MediaGo tracking URL
https://yoursite.com/landing?utm_source=mediago&utm_medium=native&vv_campaign_id=${CAMPAIGN_ID}&vv_campaign_name=${CAMPAIGN_NAME}&vv_ad_id=${AD_ID}&vv_publisher_id=${SITE_ID}&vv_click_id=${TRACKING_ID}&vv_creative_id=${ASSET_ID}Append these params to your landing-page URL — MediaGo fills the macros at click time, so every visit arrives attributed and ready to score. No funnel hop.
The buyer adds each bad site’s site_id/domain to the campaign’s block list (op=0 block / op=1 unblock), max 100 sites per API call; tools like TheOptimizer automate this into dynamic global blacklists per campaign.
MediaGo tracking token FAQs
Which MediaGo macro identifies the specific publisher placement?+
${SITE_ID}. It resolves to the exact site or widget serving your native ad, which is the value you look up in ValidVisit and then exclude inside MediaGo's own placement controls once it shows a pattern of invalid traffic.
Why does MediaGo use dollar-sign macros instead of plain curly braces?+
That is simply MediaGo's own templating convention — ${CAMPAIGN_ID}, ${TRACKING_ID}, and the rest use an all-caps, dollar-brace format. Copy them exactly as MediaGo generates them in its campaign tool; a mistyped brace means the parameter never gets filled in.
Do I need ${TRACKING_ID} even if I am not running server-to-server postbacks?+
Yes — add it anyway. ${TRACKING_ID} is MediaGo's per-click identifier and the token ValidVisit relies on to tell individual visits apart, so it is required for attribution and scoring regardless of whether you also use postbacks.
Score every MediaGo click — and find the fake ones.
See which MediaGo 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