Tracking Parameters Tokens

When setting up your templates (traffic source template, offer template, and so on) you might see a bunch of tracking parameters tokens. You can predefine parameters with these tokens and its values will be automatically filled. Then this "tail" will be appended to the link, so you could pass them further and further, use them on landers, offer pages, your custom scripts, and finally see the values of these parameters in your affiliate networks stats.


Here's the list of these tokens with the explanation of each.
                               

{visit.id}
The unique identifier of a click on a tracking link.
{visit.externalid}
The id which Zeustrack received from the Traffic Source. This id can be stored in the token and sent further.
{campaign.id}
The unique identifier of a campaign where a visit occurred.
{origin}
This token contains tracking info from lander to offer.
{trafficsource.name}
The name of the traffic source template.
{trafficsource.id}
The unique ID of the traffic source template.
{lander.id}
The unique identifier of a lander, where a visit occurred.
{group}
This token stores information specified in the Group field in the traffic source template. There's a special report for Groups in Zeustrack.
{placement}
This token stores information specified in the Placement field in the traffic source template. There's a special report for Placements in Zeustrack.
{keyword}
This token stores information specified in the Keyword field in the traffic source template. There's a special report for Keywords in Zeustrack.
{device.type}
E.g. Desktop, Phone
{device.brand}
E.g. Apple
{device.model}
E.g. iPhone X
{browser}
The numerical code for the browser will be placed in the link parameter, e.g. &browser={browser} will be replaced by &browser=4 if the visit comes from Safari.
Possible values:
Not detected - 0
Other - 1
Internet Explorer/Edge - 2
Firefox - 3
Safari - 4
Chrome - 5
Opera - 6
{browser.name}The human-readable name of the browser, e.g. Safari
{browserversion}
E.g. 11.1.2
{os}
The numerical code for the operating system will be placed in the link parameter, e.g. &os={os} will be replaced by &os=3 if the visit comes from macOS.
Possible values:
Not detected - 0
Other - 1
Linux - 2
macOS - 3
Windows - 4
Android - 5
iOS - 6
Windows Phone - 7
{os.name}The human-readable name for operation system, e.g. macOS
{osversion}
E.g. 10.13.6
{country}
Country code in two-symbol ISO format, i.e., US
{countryname}
Country name. E.g. United States
{city}
City of the visit. E.g. Los Angeles
{region}
Region of the visit. E.g. Central L.A.
{isp}
Internet service provider of a visit. E.g. AT&T
{connection.type}
The type of connection your users are connected with your websites. E.g. Cable/DSL, Corporate, Cellular, Dialup, Other.
{useragent}
Identifier of the web browser and operating system to the webserver.
{ip}
IP-address of a visit.
{language}
Operating system language of a visit.
{offer.name}This token is used when you need to pass the offer name to the affiliate network. You can set the value of the token in the offer settings in the Display offer name field.
{var1}, {var2}, {var3} ... {var20}
Predefined parameters with custom value. E.g. http://domain.com/visit/CAMPAIGN_ID?var1=xxx&var2=yyy&var3=zzz
{click.var:name}
This token is used only in offer links to send additional data from a lander to an aff network. E.g. let’s suppose you have landing parameter fbpixel. So you have a link from lander to offer http://{trackingdomain}/click/?origin={origin}&fbpixel={lander.param:fbpixel}. So in the offer settings, you should have a link http://trk.com/?....&sub2={click.var:fbpixel}. This way Facebook pixel id will be sent to the aff network in the sub2 parameter to track conversions.
{trackingdomain}
The domain of a tracking link.
{referer.domain}
The domain of a page from which you have a visit.