Native traffic source
Track MGID with UTMCAP
MGID is a native traffic source. Below are the macros UTMCAP fills in for it, the tracking URL it builds, and what happens to cost and conversions.
Your tracking URL
This is the URL UTMCAP builds for a MGID campaign. Yours has your own tracking domain and campaign in place of the example — copy it from the campaign, not from here.
https://track.example.com/spring-sale?sub1=${CLICK_ID}&sub2=${CAMPAIGN_ID}&sub3=${TEASER_ID}&sub4=${WIDGET_ID}&sub5=${SOURCE_ID}&sub6=${SITE_ID}&sub7=${CLICK_PRICE}&sub8=${GEO}&cost=${CLICK_PRICE}What each macro records
MGID replaces each macro with the real value when the ad is clicked, and UTMCAP stores it in the matching field — so reports can be grouped by campaign, placement or device.
| Field | What it records | MGID macro |
|---|---|---|
| sub1 | Click ID | ${CLICK_ID} |
| sub2 | Campaign ID | ${CAMPAIGN_ID} |
| sub3 | Teaser ID | ${TEASER_ID} |
| sub4 | Widget ID | ${WIDGET_ID} |
| sub5 | Source ID | ${SOURCE_ID} |
| sub6 | Site ID | ${SITE_ID} |
| sub7 | Click Price | ${CLICK_PRICE} |
| sub8 | Geo | ${GEO} |
Worth knowing
Dollar-brace, all caps. MGID reports the click price, so a campaign can be costed per click.
Macros from MGID’s own documentation.
How conversions get back to MGID
Postback URL comes from Postback Setup in your MGID account; the click id goes in its c parameter.
In UTMCAP, {external_id} is MGID’s own click ID and {payout} is what the conversion paid — they are filled in when each conversion is sent.
Set it up in three steps
- 1. Add MGID as a traffic source in UTMCAP and choose its template — the macros above are filled in for you.
- 2. Create a campaign with that source, and copy its tracking URL.
- 3. Paste it into MGID as the ad’s click or destination URL.
Every field of the traffic source form is explained in the traffic sources guide.
Point a domain at us and run a click through it.
The free plan takes a hundred thousand clicks a month and no card. If it does not do what you need, you have lost twenty minutes.