MGID postback URL setup for S2S conversion tracking

MGID S2S conversion tracking works by returning MGID's {click_id} value and a goal name to MGID's postback URL after a confirmed conversion. Tracked has no built-in MGID integration. You can still run the path through a custom traffic source. Tracked captures the MGID click ID on the campaign URL, receives the affiliate network's postback, and sends a server-to-server request to the postback URL MGID generates for your account.

Two identifiers do the work, and they must stay separate. MGID's {click_id} identifies the ad click. Tracked's {click.id} identifies the offer click the network returns. The click ID parameter reference lists the keys other traffic sources use.

What does the MGID postback URL look like?

MGID's postback setup guide shows this example:

https://a.mgid.com/postback/client_ID?c={externalid}&e=test_event&r={payout}

MGID describes each part this way:

Part	Meaning	Required
client_ID	Your unique MGID account identifier, in the path	Yes
c	The MGID click ID your tracker stored from {click_id}	Yes
e	The conversion goal name; MGID fills it from the goal you create	Yes
r	Revenue, shown only in your account's selected currency	No

{externalid} and {payout} in that example are another tracker's tokens, not MGID macros. MGID says you must replace them with your own system's macros. Copy the URL MGID generates for your campaign rather than typing the example by hand.

MGID allows up to three conversion goals per campaign: a main goal and two additional goals. Its setup checklist says each goal needs its own postback link and that {click_id} is mandatory for postback tracking.

The two-click-ID path

MGID ad → campaign URL with mgclid={click_id} → Tracked landing page
                                    ↓
                             /click/N offer action
                                    ↓
             network saves the Tracked offer-click ID
                                    ↓
             sale postback → Tracked /postback
                                    ↓
   Tracked fills c={click_id}&e={event} → a.mgid.com/postback/...

The first postback is inbound: the network tells Tracked about a sale. The second is outbound: Tracked tells MGID. Either one can fail while the other succeeds, so test them separately.

Step 1: Create MGID as a custom platform in Tracked

Open Platforms and choose New Platform. Name it "MGID". Set Click ID Parameter to the query parameter Tracked should read, for example mgclid. The name is yours to choose; this guide uses mgclid as an illustration.

Under Tracking Macros, add a macro whose param matches that Click ID Parameter. Set its value token to MGID's macro, {click_id}. Without an explicit token, Tracked's generated URL emits a generic placeholder instead of MGID's macro.

Your campaign URL then carries:

https://YOUR_TRACKED_CAMPAIGN_URL?mgclid={click_id}

MGID's guide uses sub_id={click_id} as its example. Either works, as long as the parameter name matches Tracked's Click ID Parameter. Use one click-ID parameter only. A preview click shows the literal {click_id}; only a delivered MGID click proves the macro expanded.

Step 2: Connect the page and the offer

Point the landing page's offer action at a tracked /click/N slot. The prelander tracking guide covers that handoff. Add {click.id} to the network field that stores an external ID:

https://advertiser.example/offer?sub1={click.id}

sub1 is illustrative. Then configure the network postback to Tracked:

https://YOUR_TRACKED_DOMAIN/postback?click_id=NETWORK_MACRO_FOR_TRACKED_ID&payout=NETWORK_PAYOUT_MACRO

The capitalized values are placeholders, not working tokens. Typed secondary events currently record zero payout in Tracked. The postback URL guide covers fields, responses, and retries.

Step 3: Create the goals in MGID

MGID's documented flow:

1. Create or edit the campaign and open Conversion tracking.
2. Select Postback in the Tracking settings tab.
3. Add a goal name. MGID accepts only Latin letters and numbers. Add up to three goals.
4. Check the conversion counting option. MGID counts unique conversions by default.
5. Choose Manual setup, add the {click_id} parameter to the tracking link, and click Get Postback URL.
6. Save the campaign.

Copy each generated URL. Record the exact e value in each one. That value is what Tracked must send for that goal.

Step 4: Add the postback template in Tracked

Edit the MGID platform and open Conversion Postback. Enable it and choose Custom URL template as the postback format. Tracked's template tokens are {click_id}, {event}, {payout}, {currency}, {order_id}, and {timestamp}.

Paste MGID's generated URL and replace its tracker tokens with Tracked tokens:

https://a.mgid.com/postback/YOUR_CLIENT_ID?c={click_id}&e={event}&r={payout}

Watch the name clash. In the ad URL, {click_id} is MGID's macro. In this template, {click_id} is Tracked's token for the stored MGID click ID. Keep the method as GET, matching MGID's example. Tracked only accepts HTTPS endpoints for custom templates.

Replace every placeholder from MGID's sample. Tracked fills an unknown token with an empty value, so a leftover {externalid} sends a blank c.

Step 5: Map each conversion to an MGID goal

Tracked resolves {event} in this order:

1. Campaign setting. The campaign's conversion step shows an MGID event name field: "Use the exact event name from MGID. Leave blank to disable." Enter the main goal's exact e value. Typed events appear under Additional events.
2. Platform event mapping. On the platform, map standard Tracked events, such as lead or purchase, to the exact MGID goal names.
3. No match. Tracked skips the outbound postback and logs it as having no event mapping. It does not guess.

The conversion-event mapping guide explains why network labels need a deliberate mapping. {payout} sends the recorded payout, or 0 when none was recorded. Decide whether MGID's r should carry your affiliate payout before reading MGID's ROI columns.

Step 6: Test both handoffs

MGID's test conversion guide uses the ad preview:

1. Open the campaign's ads, hover over a creative, and click the eye icon.
2. Click an ad in the preview and complete your funnel.
3. In Tracked, confirm the arrival shows a real MGID click ID, not {click_id}.
4. Confirm the conversion lands on the original offer click with the expected payout.
5. Open the Logs page and filter to postbacks. Check the sent URL and MGID's response.
6. In MGID, check the Test conversions column under the matching goal.

MGID says to check after 5–15 minutes, and that a conversion may take up to an hour to appear. An HTTP response from MGID is a transport receipt, not proof of attribution.

Common MGID postback failures

Symptom	Likely cause	What to check
No conversion in Tracked	Network never returned the Tracked offer-click ID	The offer URL and the delivered inbound postback
Outbound skipped, "missing platform or click id"	{click_id} was not captured	Ad URL parameter name versus Tracked's Click ID Parameter
Outbound skipped, "no event mapping"	Campaign field blank and no platform mapping	The MGID event name and platform event mapping
MGID shows nothing under a goal	e does not match the goal exactly	The generated MGID URL versus the sent URL in Logs
Blank c in the sent URL	A leftover non-Tracked token in the template	Replace {externalid} with {click_id}

The postback troubleshooting guide covers inbound failures in depth.

Where Tracked is today

What works today:

• Custom platform capture. A custom platform reads its Click ID Parameter and stores the value as the platform click ID.
• Custom outbound postback. A Custom URL template sends a GET or POST to an HTTPS endpoint, filled with the six documented tokens. Attempts and responses appear in the Logs page.

What is missing:

• No built-in MGID integration. Tracked has no MGID preset, prefilled endpoint, or goal suggestions. You enter the template and goal names yourself. The integration types guide explains why a postback is not a native integration.
• No MGID spend sync. Tracked has no MGID account connection, so MGID cost does not flow into campaign profit. Compare spend in MGID.
• Not production-verified for MGID. Unlike Taboola and NewsBreak, this path is not a verified provider path. Run the test above before scaling.
• Attribution. Tracked records what it sent and the response. MGID's counting rules decide whether a conversion appears.

Frequently asked questions

What is MGID's click ID macro?

{click_id}. MGID fills it when a visitor clicks the ad. Add it to your tracking link under one parameter name, such as sub_id={click_id} or mgclid={click_id}. MGID says it is mandatory for postback tracking.

Which parameters does the MGID postback URL require?

Only c and e. c carries the stored MGID click ID and e carries the goal name. r is optional revenue. The client ID sits in the URL path.

Can I send more than one MGID conversion stage?

Yes, up to three goals per campaign: a main goal and two additional goals. Each goal has its own e value. In Tracked, map each conversion type to the matching goal name.

Does Tracked have a native MGID integration?

No. You use a custom platform with a custom postback URL template. Spend sync and a built-in MGID preset are not available.

Start free and set up an MGID campaign.

Sources

Checked October 24, 2026.

• MGID Help Center, Postback setup
• MGID Help Center, Available tracking options in MGID Ads
• MGID Help Center, Conversion tracking: setup checklist
• MGID Help Center, Test conversion flow in MGID Ads