Ad network tracking macros explained: what tokens are and how to map them to sub-IDs

11 min readUpdated Nov 20, 2026

Ad network tracking macros explained: what tokens are and how to map them to sub-IDs

Ad network tracking macros are placeholders in your landing page URL that the network replaces with real values at click time — the site your ad appeared on, the creative that served, the campaign ID, the device type. A macro looks like {site_id} or ${SUBID} and arrives at your tracker as a plain string you can store and report on. If you don't use them, every click from a network looks identical and you have no way to cut a losing placement. This guide explains what tokens actually are, shows the exact macro syntax for the major native and push networks, and walks through mapping each one into sub1–sub5 so your tracker — Adtraxo or otherwise — can report on placements, creatives and sources separately.

What are ad network tracking macros, exactly?

A tracking macro is a variable the ad network owns. You put it in the destination URL when you build the campaign; the network substitutes a value when a real user clicks. The token itself means nothing to the network's ad server — it's a lookup key into the data it already holds about that impression.

Two things happen when a click fires:

  1. The network reads your landing page URL, finds every recognised macro, and swaps it for the value attached to that impression.
  2. The browser requests the resulting URL. Your tracker sees a query string full of real values — ?sub1=example-widget.com&sub2=1234567&sub3=desktop — and records them against the click.

From that point on, every conversion attributed to that click inherits the same sub-ID values. That's the whole mechanism: macros in, sub-IDs out, reporting on top.

Two rules trip people up constantly:

  • Only macros the network documents will resolve. Invent {placement} on a network that calls it {publisher_id} and you'll get the literal text {placement} in your report, or nothing at all.
  • Macros must survive URL encoding. If you wrap your destination in another redirect or a third-party link shortener, check the encoding — braces and dollar signs get mangled more often than you'd think.

Macros vs tokens vs parameters: the vocabulary

Vendors use the words interchangeably and it causes real confusion when you're following a setup doc.

  • Macro — the placeholder in your URL ({site}).
  • Token — the same thing, usually the word push and native networks prefer. PropellerAds calls them macros; Taboola's help centre says macros; MGID says macros; RichAds uses both.
  • Parameter — the query-string key the value lands in (sub1=). Your tracker owns this side.
  • Sub-ID — the tracker-side slot (sub1 through sub5) that stores the parameter.

So the sentence "map the macro to a sub-ID" means: take the network's {site_id} token, put it in the destination URL as sub1={site_id}, and tell your tracker that sub1 is where placement data lives.

Why sub-IDs are the right destination for macros

Every serious tracker gives you a handful of generic slots rather than network-specific fields. That's deliberate — it means one tracker handles every network without a custom integration per source. The trade-off is you have to decide, once, what each slot means and stick to it.

A convention that works across native and push:

  • sub1 — placement identity: publisher site, widget, zone, or feed. The thing you blacklist.
  • sub2 — creative identity: campaign ID, creative ID, teaser ID, banner ID.
  • sub3 — device or platform: mobile/desktop, OS, browser, connection type.
  • sub4 — geo or language, if the network exposes it and you run multi-geo.
  • sub5 — anything source-specific you want for a single network, like a keyword or a bid type.

Keep sub1 as placement on every network, always. The moment sub1 means "site" on PropellerAds and "creative" on MGID, your cross-network reporting becomes unreadable and you'll rebuild it in a month.

In Adtraxo, sub-IDs sub1–sub5 are a Pro feature, and they're what feed the per-campaign geo and device breakdowns and the fraud detection rules. On the Free plan you get basic stats but not sub-ID capture — worth knowing before you plan a 40-placement split test.

Network-by-network macro syntax

Below is the macro set you'll actually use for placement and creative tracking. Always confirm against the network's current docs before you launch — networks rename and deprecate tokens.

PropellerAds

PropellerAds uses brace-style macros and exposes zone and campaign data directly.

  • {zone_id} — the publisher zone. This is your blacklist unit. Map to sub1.
  • {campaign_id} — the campaign. Map to sub2.
  • {creative_id} — the creative. Map to sub2 if you're not using campaign ID, or sub5.
  • {ad_type}, {browser}, {os} — device context. Map to sub3.
  • {country} — geo. Map to sub4.

A working destination URL looks like:

https://track.example.com/click?camp=prop_01&sub1={zone_id}&sub2={creative_id}&sub3={os}&sub4={country}

Zone-level data is the whole game on PropellerAds — the zone blacklist guide shows how to turn sub1 into a cut list.

RichAds

RichAds exposes similar tokens but the naming differs slightly, and creative-level reporting is where most of the value sits.

  • {site_id} or the source token — placement. Map to sub1.
  • {campaign_id}, {creative_id}, {banner_id} — map to sub2.
  • {device}, {os}, {browser} — map to sub3.

Full walkthrough, including the postback side, is in RichAds tracking setup: postbacks and creative IDs for push campaigns.

MGID

MGID's placement granularity is widget-level, and that's what you want in sub1 — not the publisher site alone. A single publisher can carry several widgets with wildly different performance.

  • {widget_id} — the widget. Map to sub1.
  • {teaser_id} — the creative. Map to sub2.
  • {campaign_id} — map to sub5 if you need it separately.

See MGID tracking setup: passing widget and teaser IDs into your tracker for the exact parameter names, and MGID widget blacklist for the decision rules once data is flowing.

Taboola

Taboola uses curly-brace macros too, but the publisher and site tokens are the ones that matter for blocking.

  • {site} or {site_id} — the publisher site. Map to sub1.
  • {campaign_id}, {campaign_item_id} — map to sub2.
  • {platform}, {device} — map to sub3.

Taboola's click IDs are also what you pass back in the postback so conversions land against the right campaign item — covered in Taboola conversion tracking for affiliates. And once sub1 is populated, how to find and block the Taboola publisher sites that waste your budget becomes a mechanical exercise.

How to map macros to sub-IDs: step by step

  1. Decide your sub-ID convention before you build anything. Write it down. sub1 = placement, sub2 = creative, sub3 = device, sub4 = geo, sub5 = spare. Every network, every campaign.
  2. Create the tracking link in your tracker. In Adtraxo, create the campaign, set the destination URL to your offer or landing page, and note the click URL it generates.
  3. Append the macros to the click URL in the network's campaign builder, using the syntax for that network. Keep the parameter names (sub1=) identical across networks; only the macro in the value changes.
  4. Open the network's preview or test tool. Every one of these networks lets you preview the resolved URL. Check that the braces are gone and real values appear. If you see a literal {site_id}, the macro name is wrong.
  5. Fire one test click yourself from a clean browser and open the click in your tracker's click log. Confirm the sub1 value matches the placement you clicked from.
  6. Set up the postback. Copy your tracker's postback URL and paste it into the network's conversion tracking field, replacing the network's click-ID macro where the template requires it. Postbacks are Pro-only in Adtraxo — the Free plan won't record server-side conversions.
  7. Wait for data, then report by sub1. Give it enough clicks to mean something before you judge a placement. A placement with three clicks and zero conversions tells you nothing.

Worked example: a PropellerAds push campaign, end to end

Say you're running a sweepstakes offer across 12 geos on PropellerAds with four creatives.

Tracker link:
https://track.example.com/click?camp=push_sweep_q4

Destination URL in PropellerAds:
https://track.example.com/click?camp=push_sweep_q4&sub1={zone_id}&sub2={creative_id}&sub3={os}&sub4={country}

Postback in PropellerAds:
https://your-propellerads-postback-url?click_id={click_id}&payout={payout}
With your tracker's postback template substituted for the click ID.

After a few days you open the report grouped by sub1. Three zones account for most of the spend and none of the conversions. You blacklist those three in PropellerAds and move the budget to the two zones producing conversions at a lower cost. Then you group by sub2 and find one creative carrying the whole campaign — the push ad creative testing guide covers how to judge creatives by conversions rather than click-through.

None of that is possible without the macros. With them, it's a fifteen-minute report.

Common macro mistakes and how to catch them

The macro resolves to nothing. The click arrives with sub1= empty. Usually the macro name is wrong for that network, or the network doesn't populate it for that traffic type. Check the resolved URL in the preview tool.

The literal macro text arrives. You see sub1={site_id} in your report. The network didn't recognise the token — wrong braces, wrong name, or the parameter got double-encoded by a redirect in between.

Click counts don't match. The network reports more clicks than your tracker. That's usually bots, prefetching, or users who bounced before your page loaded. The click discrepancy guide explains the causes; Adtraxo's arrival snippet — a one-line script on your landing page, available on any plan — tells you which clicks actually loaded the page in a real browser, which separates "clicked and left" from "never arrived".

Sub-IDs overwrite each other. You put the creative macro in sub1 on one campaign and the site macro in sub1 on another. Your report is now a mix of two data types. This is why the convention matters.

Fraud hides in the sub-ID data. A single zone producing clicks at an implausible rate, or many clicks from one IP, shows up as an outlier in sub1. Adtraxo's fraud detection — IP velocity, datacenter IP, bot user agents, uniqueness conflicts, invalid referers — flags these on Pro, and you can act on the zone directly.

Where the tracker fits, and where the network stops

The network knows what it served and who clicked. It does not know what happened after the click unless you tell it. That gap is the entire reason for a tracker in the middle: it stores the macro values, attributes the conversion, and reports on the combination.

If you're setting up several networks at once, how to track native and push ad campaigns: a network-by-network setup guide covers the shared conventions so you're not rebuilding your sub-ID scheme per source. Adtraxo handles the click capture, sub-ID storage, postback conversion recording and per-campaign geo/device breakdowns in one place, with custom tracking domains so your links sit on your own domain rather than a shared one — which also reduces the chance of a network or browser treating your redirect with suspicion.

A note on cost, since it comes up: as of October 2026, Voluum's cheapest plan is $119/month billed annually, RedTrack's Solo plan is $169/month billed monthly or $118/month billed annually, ClickMagick Starter is $79/month billed monthly or $66/month billed annually, and BeMob has a free plan with paid plans from $49/month. Prices change, so check each vendor's page. Tools like Binom and Keitaro have their own licence pricing — go to their pricing pages directly. Adtraxo Pro is $27/month at the founding rate (rising to $47 for new accounts; existing subscribers keep $27), with unlimited links, clicks and domains, fraud detection, A/B split testing, sub-IDs sub1–sub5, country analytics and S2S postback conversions, plus a 30-day money-back guarantee and cancel-any-time. The Free plan gives 10 tracking links, 5,000 recorded clicks a month, 1 custom domain and basic stats, no card required.

Frequently asked questions

What is the difference between a tracking macro and a sub-ID?

A macro is the network-side placeholder — {site_id} — that the network replaces with a real value at click time. A sub-ID is the tracker-side slot — sub1 through sub5 — where that value is stored. You connect them by putting the macro in the destination URL as a parameter value: sub1={site_id}.

Do all ad networks use the same macro syntax?

No. PropellerAds, RichAds, MGID and Taboola all use brace-style macros, but the token names differ — MGID exposes widget IDs, Taboola exposes

Track your affiliate campaigns for free

Clicks, conversions, fraud detection — all in one tracker.

Get started free →

Not ready for an account? Get the Tracking Domination Playbook — free, just your email.