Campaign setup

Tracker macro converter

Every tracker names the same value differently. Look up the equivalents field by field, or paste a URL and rewrite its macros for another tracker.

Rewrite a URL

URL is written for

Rewrite for

Postback or landing URL with macros

—

Only tokens that exactly match a known macro of the source tracker are rewritten; everything else is left untouched.

Macro reference

Value	Keitaro	Binom	Voluum	RedTrack	BeMob

Macro names change between tracker versions and can be renamed in settings — always confirm against your tracker's own token reference. “—” means the tracker fills this automatically or has no direct equivalent.

Why tracker macros never line up

A tracker macro is a placeholder the tracker fills at click time — the click id, campaign, cost, geo, device and so on. There is no shared standard, so the same value is written {subid} in Keitaro, {clickid} in Binom and {clickid} in Voluum, and a Sub ID field maps only loosely between platforms. Moving a campaign or wiring a new integration means re-mapping every token by hand, and a single wrong name silently drops that value from your reports.

How the reference and the rewrite work

The table maps twenty common fields across Keitaro, Binom, Voluum, RedTrack and BeMob. The rewrite mode scans a URL for tokens in curly or square brackets, matches each against the source tracker's known macros, and swaps it for the destination tracker's equivalent — tokens it does not recognise are left exactly as they are, so custom parameters survive untouched.

Always confirm against your tracker

Macro names change between tracker versions and several can be renamed in settings, so treat this as a starting point, not gospel. The same field list also matches the presets in our Postback URL builder, so a value you map here carries straight into the postback you send the network.

Frequently asked questions

What is a tracker macro?

A placeholder like {subid} or {campaign_id} that the tracker replaces with the real value when it builds a link or fires a postback. Macros are how the click id, cost, geo and creative travel between the traffic source, your tracker and the affiliate network.

Why do the macro names differ between trackers?

There is no shared standard. Each tracker picked its own token names years ago and kept them for backward compatibility, so the same value is {subid} in Keitaro, {clickid} in Binom and {clickid} in Voluum. Moving a campaign between trackers means re-mapping every token.

How does the “rewrite a URL” mode work?

It scans the URL for tokens in {curly} or [square] brackets, matches each one against the source tracker's known macros, and swaps it for the destination tracker's equivalent field. Tokens it does not recognise are left exactly as they are.

Why does a field show “—” for a tracker?

Either that tracker fills the value automatically (Voluum computes cost from the campaign, for example) or it has no single built-in token for it and you would use a custom variable instead.

Can I trust these macro names exactly?

Treat the table as a starting point. Macro names change between tracker versions, some can be renamed in settings, and a few (Sub IDs especially) map loosely. Always confirm against your tracker's own token reference before going live.

Does the click-id field mean the same thing everywhere?

Functionally yes — it is the unique id your tracker assigns to a click and expects back in the postback. Only the token name differs: {subid}, {clickid}, {rt_clickid} and {click_id} all refer to it.

Which trackers are covered?

Keitaro, Binom, Voluum, RedTrack and BeMob — the trackers most common in iGaming media buying. The same field list also lines up with the presets in our Postback URL builder.

Is anything sent to a server?

No. The lookup table and the URL rewrite both run entirely in your browser; nothing you type is transmitted or stored.

All tools →