Zeropark Documentation

Tracking

Abstract

Use this guide to learn how to set up tracking and get access to more in-depth data, granular reports and many traffic optimization options.

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 1. 

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 allows you to pass on different 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,n2n3…) 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.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:

https://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).

Note

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.

Note

Zeropark Note: The n1n2, 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 subidsubid1subid2. 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

  1. In a campaign edit form, add the {cid} token to your destination URL (obtained from your tracking platform) and pair it with a tracking platform parameter name, if they are not already included.

    Note

    Zeropark Note: Keep in mind that the parameter name should be recognizable by your tracking platform.

  2. In the Conversion tracking section select a tracker that you are going to use from the list of trackers. This configures the necessary tracking tokens in a traffic source postback URL automatically. If your tracker is not on the list, you will have to configure them manually according to the instructions provided by your tracker's documentation or support.

  3. Copy the postback URL, that was generated by Zeropark, to the clipboard.

    Note

    Zeropark Note: If a tracker you use is Voluum, you don't have to copy the postback URL, as the conversion tracking will be configured automatically when you submit a Voluum campaign URL as a destination link in Zeropark.

  4. Select, if you want to track revenue automatically or manually

    • Auto: This option is available when passing cost information from a tracker is configured. If you have selected a tracker from the list, this is already configured. If you have selected the Other option, you will have to configure this manually according to your tracker's documentation or support.

    • Manual: Select the CPA value.

    conversiontracking1.png
  5. Paste the copied postback URL to your traffic source setup in your tracking platform. Usually, the appropriate section is called Traffic source postback URL or Reporting conversions to traffic source.

  6. Append the tracking platform token, that is used to store Zeropark's click ID value, at the end of the traffic source postback URL. Typically, it is called something like {externalid}.

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 two weeks for 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

{creative­_number}

Send a number of a creative.

Note

Zeropark Note: For Voluum, this token has to be matched with the custom variable 7.

{visit_cost}

Sends a cost of a visit.

{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 type of visitor.

Note

Zeropark Note: 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.

{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.

Note

Zeropark Note: 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 or mobile traffic.

{target_url}

Sends a target URL; it is only applicable for POPUP campaigns.