🔀Configure your Postback URL

This page details out the datapoints that we dispatch to your Postback URL for each conversion.

In case this is new to you, we'll first discuss a few key concepts, before moving on to the Postback URL parameters. If you are familiar with what Postbacks are, you can skip to Postback Configuration.

What are "Conversions" and "Postbacks"?

Ever wondered why are these ad campaigns called "Performance Ad Campaigns"? It's because in this case, advertisers pay publishers to drive a performance goal. This goal could be an app-install, or a user-registration, a purchase, or anything else that meets a business objective for the advertiser.

Here's a simplified version of how a performance ad campaign works:

Step 1

The advertiser identifies a performance goal. For our example, let's say that the advertiser is Airbnb, and they want to run an ad campaign to drive app installs.

Step 2

Airbnb reaches out to a few publishers, and offers to pay $2 for each app install that the publishers can drive for Airbnb. Let's say NYTimes takes them up on their offer.

Now NYTimes is already promoting several apps in a similar manner. They are a data-driven organisation and want to optimise the ads they show to drive maximum revenue for themselves. Remember, in this case, NYTimes does not make any money for displaying Airbnb ads, or for getting clicks on Airbnb ads. NYTimes only makes money when a user from NYTimes clicks on an Airbnb app ad, and goes on to complete the app-install process.

So NYTimes goes back to Airbnb and asks them to call a NYTimes API each time Airbnb records an install driven by NYTimes. If Airbnb does that, NYTimes would have real-time data on how much revenue they are making from the Airbnb campaign.

Step 3

Just like NYTimes, many other publishers have a similar ask for Airbnb. To handle this in a scalable manner, Airbnb decides on onboard Appsflyer. Appsflyer is a Mobile Measurement Partner (MMP). You can read more about MMPs here.

When NYTimes now drives an app-install for Airbnb, Appsflyer's SDK in the Airbnb app will track that install, and it will call NYTimes's API like they asked.

In this example above, each time NYTimes drives an app-install for Airbnb, it is considered a "conversion". Each time Appsflyer sends data to the NYTimes's API, it is considered a "postback".

Configuring your Postback URL with Gamezop

You will have to send your Postback URL to our team when we first start working with you. For each conversion we record from the advertiser, we will make a hit to your Postback URL.

Here are the macros we support:



The value sent by you in the click-id parameter of the Gamezop Campaign Link.


The value sent by you in the site-id parameter of the Gamezop Campaign Link.


The value sent by you in the sub-1 parameter of the Gamezop Campaign Link.


The value sent by you in the sub-2 parameter of the Gamezop Campaign Link.


The value sent by you in the sub-3 parameter of the Gamezop Campaign Link.


The value sent by you in the sub-4 parameter of the Gamezop Campaign Link.


The value sent by you in the sub-5 parameter of the Gamezop Campaign Link.


The property-id value in the Gamezop Campaign Link.


The campaign-uuid value in the Gamezop Campaign Link.


The ISO 3166-1 alpha-2 country code for the country where the conversion was recorded.


Gamezop's unique identifier for that conversion. While it's not mandatory, we strongly encourage you to record this value. As explained in the Other notes section below, we reattempt postbacks in case of failed deliveries. If you record the gzp-postback-id, you will always be able to uniquely identify conversions, and will never record the same conversion more than once.

Note that the keys of the URL parameters in your Postback URL are not decided by us. As long as you use the correct macro, the postbacks will work fine.

Here's a sample Postback URL, with the macros correctly configured:


Other notes

  • When we call your Postback URL, it must respond with a 200 HTTP Response Status Code when you successfully record the data from the postback.

  • For postbacks that are not successfully delivered, we reattempt delivery every 30 minutes. If your Postback API is down when we send you a postback, we will not get a 200 HTTP response. Our system will therefore consider that postback undelivered, and we will reattempt delivery after 30 minutes. We will keep attempting postback delivery in 30-minute intervals until we get a 200 HTTP response on your Postback API.

Last updated