Skip to main content

Zeropark Documentation

Tracking Tokens

Zeropark offers the following tokens:

Token

Description

{cid}

Sends a click ID for conversion tracking. This token is mandatory in order to keep a healthy track of your visits.

{traffic_type}

Sends POPUP / DOMAIN. It allows testing different traffic types.

{visitor_type}

Sends ADULT / NON-ADULT type of visitor.

Caution

While advertising, you need to take into account the affiliate network’s policy from which you take your offer.

{source}

Sends a source ID. It is a huge traffic source with multiple targets in it.

{target}

Sends a target ID. It is the actual sub-placement of your ad; targets belong to certain sources.

{target_url}

Sends a target URL. It is only applicable for POPUP campaigns.

{creative­_number}

Send a number of a creative.

{geo}

Sends a country code.

{campaign_id}

Sends a numeric campaign ID. The token might be particularly useful for external tracking.

{long_campaign_id}

Sends a UUID campaign ID. This token is needed for API calls.

{campaign_name}

Sends a campaign name.

{os}

Sends an operating system name.

Caution

It is not recommended to run multiple operating systems within one campaign taken into consideration their different performance.

{carrier}

Sends mobile carrier.

{device_id}

Send a device ID; for in-app campaigns, you are able to collect some device ID to target afterward that can be used to blacklist/whitelist.

{browser}

Sends a browser name for desktop or mobile traffic.

{geo}

Sends a country code.

{city}

Sends city name.

{region}

Sends region name.

{keyword}

Sends keywords attached to the visitor.

{keyword_match}

Sends keyword match type broad/exact.

{visit_cost}

Sends a cost of a visit.

HOW DOES S2S/POSTBACK TRACKING WORK?

You can add tokens to the destination URL that allows you to pass on various pieces of information. Each token must be placed after a parameter name. The parameter name is an empty basket and you can decide which values are sent to it. In our example, the empty basket is n1 and we are passing the target ID (with the {target} token) of a particular visit to it.

The parameter names (sometimes referred to as sub IDs – n1,n2, n3…) show your tracking software what kind of data you are sending. In turn, the {target} and {keyword} tokens show Zeropark what data to send (dynamic placeholders) to your tracking software. Here is an example of how these tokens would look paired with the n1 and n2 parameter names in your destination URL:

https://www.myaffiliateoffer.com/?n1={target}&n2={keyword}

If you would like to add another parameter, n3, you could do this using an ampersand (&) and following the same pattern:

https://www.myaffiliateoffer.com/?n1={target}&n2={keyword}&n3={match}

You can repeat this process till all your sub IDs are taken (these are only limited by the number of free spaces in your tracker).

Note

The n1, n2, and n3 are only examples of the parameters. If you want to set up the tracking correctly, you should find the corresponding parameter from the tracking software. There are different conventions for different tracking platforms, for example, subID, subID1, subID2. If you do not know what your parameters or subIDs are, you should contact the tracking software company to check you are set-up correctly.

postback.png
In this section: