Dynamic Tokens

These are the Dynamic tokens that are used to track interesting data through the campaign URL and advertiser's tracking system:

• {actual_cost}: The actual CPM / CPC paid for each impression / click.

Note: Some third-party tracking solutions round or truncate very small decimal values passed in tracking URLs. When impression-based campaigns send very small cost values (for example 0.00002), certain trackers may round the number or remove leading zeros. This can cause the cost to appear as 0 or significantly lower inside the tracker, even though a valid value was sent. This behavior depends on the tracker's precision and is not a tracking issue.

• {campaign_id}: The ID of the campaign.
• {category_id}: The ID of the category detected.
• {conversions_tracking}: The unique ID generated when customer clicks on the ad.
• {cost}: The cost of the click or impression.
• {country}: The 3-character country code of the visitor.
• {email_encoded}: This token can be used to insert the emails of logged-in users into landing page URLs for all formats.

Note: {email_encoded} is available only on request. Contact your account manager to enable it.

• {ex_av}: The Age Verification Status value (0 = No Age Verification, 'Undefined'; 1 = Verified; 2 = Not Verified), which determines if the user is verified or not as long as the publisher shares this value. If the publisher doesn't share the value, then it will revert to 0 = 'Undefined'.
• {format}: The banner size. Example: 300×250.
• {keyword}: The keyword that was matched in case of campaigns targeting specific keywords. This will be empty if there is no match.
• {language}: The language of the visitor.
• {pricing_model}: The pricing model of the campaign (1 = CPC, 2 = CPM, 4 = Smart CPM, 5=CPV, 7=Smart CPC).
• {site_id}: The ID number of the site where the ad is displayed.
• {src_hostname}: The site name that the Publisher submitted for displaying ads, not including the HTTP protocol at the beginning (e.g. examplesite.com).
• {sub}: The Publisher's Sub ID.
• {tags}: The list of keywords that have been identified for that ad impression.
• {time}: The timestamp, which is used as a cache buster.
• {url}: The full URL of the site that the Publisher submitted to the Admin Panel for displaying ads, including the HTTP protocol (e.g. ).

Note: This token will not display the URL where the ad was displayed to the user; only the URL that is registered in our platform.

• {variation_id}: The ID of the variation (Banner or landing page).
• {zone_id}: The ID of the ad zone where the ad is displayed.

Using dynamic tokens in native ads and push notifications

If you are creating a campaign using native ads or push notifications in Step 2, you can add dynamic tokens that display localized text to the visitor based on their information, allowing you to target your ads more effectively.

These tokens are available for the Title and Description fields. To add a token, click the "+Add Token" button, then use the radio buttons to select how the token will be capitalized. The available tokens for this feature are the follwing:

• {country_name}: The localized country name of the visitor. e.g. España.
• {region}: The localized region name of the visitor: e.g. Cataluña.
• {city}: The localized city name of the visitor: e.g. Barcelona.
• {language_name}: The localised language of the visitor. e.g. Español
• {day}: The localised day that the visitor is visiting the site on: e.g. Lunes, Martes, Miércoles.
• {operating_system}: The operating system of the visitor: e.g. Windows 10.
• {device}: The device that the visitor is using: e.g. iPhone.
• {carrier}: The carrier that the visitor is using to access the site: e.g. Vodafone.
• {browser}: The browser that the visitor is using.

These dynamic tokens will display in the language that you set for the campaign. The language in the Variations Text Language drop-down menu next to the Distribution Algorithm. The default language is English.

Note: You can only select one language for all the variations in a campaign. For ads in different languages, you should create separate campaigns for each language.