Tracking Tokens and Parameters Explained
When you set up a creative, you specify a destination URL — the page users land on after clicking your ad. You can enhance that URL by incorporating tracking macros. A macro is a placeholder enclosed in curly braces, such as {country}. When someone clicks your ad, we automatically replace the placeholder with the actual value (for instance, the visitor's country code). This functionality helps your tracking system or landing page identify the source of each click.
How to Use a Macro
- Click the small button next to the destination URL field to open the macro list.
- Select any macro to add it to your URL.
- A macro placeholder will look like
{macro_name}and will be substituted with a real value at the time of the click.
Example:
https://yourwebsite.com/landing?country={country}&device={device_type}
For a click from a mobile user in the United States, this would translate to:
https://yourwebsite.com/landing?country=US&device=mobile
You can also combine several macros into one value, separated by a character of your choice:
https://yourwebsite.com/landing?source={pubfeed}_{subid}
Available Macros
Click & Tracking
Macro | What it's Replaced With |
|---|---|
| The unique ID assigned to each click |
| The original click ID, before any changes |
| The click ID provided by the traffic source |
| An identifier for the traffic source |
| A unique ID for the individual ad request |
| The date/time of the click (as a Unix timestamp) |
Campaign
Macro | What it's Replaced With |
|---|---|
| Your campaign ID |
| The offer ID |
| The creative (banner) ID |
| The winning bid amount for that click |
| The conversion type / pricing model |
| The matched keyword (for keyword campaigns) |
Publisher
Macro | What it's Replaced With |
|---|---|
| The publisher's account ID |
| The publisher's feed ID |
| The publisher's integration point |
| The publisher's zone / ad placement |
| The publisher's site ID |
| The remote feed ID (for RTB traffic) |
Location (Geo)
Macro | What it's Replaced With |
|---|---|
| Two-letter country code (e.g., US, GB) |
| Region or state |
| City name |
| Postal / ZIP code |
| The visitor's IP address |
| The mobile network carrier |
Device
Macro | What it's Replaced With |
|---|---|
| Device type (mobile, desktop, or tablet) |
| Device manufacturer |
| Device model |
| Operating system |
| Operating system family |
| Browser name |
| The full browser/device "user agent" text |
| The phone's advertising ID (IDFA on Apple, GAID on Android) |
App
Macro | What it's Replaced With |
|---|---|
| The app ID (for in-app traffic) |
| The app's bundle identifier (for in-app traffic) |
Search & Referrer
Macro | What it's Replaced With |
|---|---|
| The search query (for keyword/search traffic) |
| The full URL the visitor came from |
| Just the website (domain) the visitor came from |
| The IP address recorded at search time |
| The search referrer's domain |
Analytics
Macro | What it's Replaced With |
|---|---|
| The Google Analytics client ID |
Rules to Keep in Mind
Your destination URL undergoes an automatic check before you can save it. To avoid errors, adhere to these guidelines:
- Start with
http://orhttps://. Every URL must begin with one of these protocols. We recommend usinghttps://.
- Use a legitimate website address. The URL must point to a public domain (such as
yoursite.com). Local or private addresses likelocalhost,127.0.0.1, or internal IP addresses are not permitted.
- No spaces. URLs cannot contain spaces. Use
%20to represent a space instead.
- Spell macros correctly and observe capitalization. Macros are case-sensitive — for example,
{country}is valid, but{Country}or{COUNTRY}will be rejected. Only utilize macros from the provided lists. Any unknown macro (like{click_id}) will trigger an error.
- Always close your curly braces. Every
{must have a matching}. An unclosed brace such as{countryor an empty{}is not acceptable.
- Avoid leaving empty settings in the address. Each component of the URL's query (the portion after
?) needs a name. For instance,?country={country}is acceptable, but a setting without a name will be rejected.
Good news: If there’s an issue, a clear message will appear right under the field, and for common errors (like spaces, a missinghttps://, unsupported macros, or an empty{}), a one-click fix will be available.
Example of a Valid URL:
https://yourwebsite.com/offer?geo={country}&device={device_type}&click={subid}
For further assistance, please refer to our Help Center or reach out to Support.
Updated on: 31/05/2026
Thank you!
