MediaGo tracking tokens & macros

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 macro list spells them and paste them into the Tracking field on the Create Ad Set page. 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 carries the id of the publisher site 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.

MediaGo buys placements from publishers across the open web, and its own controls work at site level: daily reports in the site dimension, plus block lists per campaign and per account. Once ${SITE_ID} is attached to every visit, ValidVisit can report an invalid share for each site instead of averaging them into one campaign-level number that hides which sites are actually worth the spend. Nothing ValidVisit finds gets applied automatically inside MediaGo, though — the platform's role stops at detecting, judging, and attributing each visit, plus surfacing which site IDs are driving invalid traffic. Turning that into fewer wasted impressions is on you: pull the flagged ${SITE_ID} values and add those sites to MediaGo's block list, at campaign or account level, yourself. ValidVisit hands you the evidence; MediaGo's own controls are where the exclusion actually happens.