This article gives you an insight on tracking and a destination URL role in that. The destination URL allows you to track conversions and monitor the campaign’s performance. The simple example below visualizes how the tracking works; so, let’s take a look at the humble homing pigeon.


Example:

A pigeon is sent to a destination with a message tied to its leg. If the pigeon makes it to the destination successfully, it flies back to it’s home with a new message-response.

Postback URLs work in a similar way. The pigeon’s home is the campaign in Zeropark, the pigeon is the visit, where the first message it is carrying is the user ID, the destination is the landing page – and the new message as the click ID. When it arrives back home, the conversion is counted in your account.


Along with the mentioned user’s click ID, {cid} in our system, there is a bunch of other dynamic placeholders (called tokens), to keep a track of additional information regarding one particular visit. A full list of available tokens in Zeropark you can find in the Available Tokens section.
Server-to-Server Tracking
You can add tokens to the destination URL  that allow you to pass on different pieces of information. Each token must be placed after a parameter. The parameter 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 {target} of a particular visit to it.

The parameters (or sub IDs – n1,n2, n3…) show Zeropark where you want to send the data in your tracking software. In turn, the {target} and {keyword} tokens show Zeropark what data to send (dynamic placeholders). Here is an example of how those tokens would look placed in parameter n1 and n2 in your destination URL:

http://www.myaffoffer.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:

http://www.myaffoffer.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).

Zeropark Info: You have to use tokens and (Server-to-Server) postback URL in order to monitor your performance. The tracking itself is a crucial part of performance marketing and it is a prerequisite for getting an Account Manager assigned.

 

Zeropark Note: The n1, n2, and n3 are only examples of the parameters. If you want to set up the tracking correctly, you should find 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 sub IDs are, you should contact the tracking software company to check you are set-up correctly.

 

Tracking Conversions

 

If you would like to track your conversions within the Zeropark platform, follow these steps:

  1. Add the {cid} token to your destination URL.
    Zeropark Note: Keep in mind that parameter should be recognizable by your tracking platform.

  2. Copy the postback URL generated by Zeropark.
  3. And add it to the Traffic source set-up in your tracking platform.
  4. Append the {cid} parameter to the URL in the tracking platform to pass the conversion ID from your tracking software to Zeropark.
  5. You can also append the payout with the parameter payout to track the profits within the platform.

 

Tracking Platform
If you are new to tracking, we highly recommend you using our own proprietary tracking system, Voluum. How can you benefit from that?

  • Manage your Zeropark campaigns within Voluum dashboard
  • See all your changes immediately on your Zeropark account
  • Quickly set and change your campaign bids, set custom bids by keyword, target, source, and country
  • You don’t need to use postback URLs or tracking pixels, as your data from Voluum will be sent to Zeropark based on your client ID
  • Tracking of Zeropark events is free
  • As your enrollment bonus, you will get one month free 😉

 

If only possible, try to avoid Google Analytics as the discrepancies are quite high due to the database mismatches, tag firing & JavaScript errors on your side. It might happen that landing pages take around 5-7s to load which prevents your Google Analytics JavaScript from firing hence there won’t be any visit recorded on your end (even though we have delivered that visit).

Available Tokens

Zeropark offers the following tokens:

   Token    Description
   {target}Sends a target ID ; it is the actual subplacement of your pop-up; targets belong to certain sources
   {source}Sends a source ID; it is a huge traffic source with multiple targets in it.
   {keyword}Sends keywords attached to the visitor
   {match}Sends a keyword that got you the visit; it is applicable only for keyword campaigns
   {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; for more advanced users it allows to test different traffic types
   {geo}Sends a country code; it is the most commonly used for testing an offer in a multi-geo campaign
   {visitor_type}Sends ADULT / NON-ADULT

Zeropark Info: While advertizing, you need to take into account the affiliate network’s policy from which you take your offer.
   {campaign_id}Sends a numeric campaign ID; the token might be particuraly useful for external tracking & API users
   {long_campaign_id}Sends a UUID campaign ID
   {campaign_name}Sends a campaign name
   {os}Sends an operating system name

Zeropark Info: It is not recommended to run multiple operating systems within one campaign taken into consideration their different performance.
   {device_id}Send a device ID; for in-app campaigns you are able to collect some device ID to target afterwards that can be used to blacklist / whitelist
   {browser}Sends a browser name for desktop traffic
   {target_url}Sends a target URL; it is only applicable for POPUP campaigns