When to use?
Designed to deliver conversion information to a third party, at the time we detect a conversion, postbacks can be set up for any campaign.
After you set up a campaign, a postback for a campaign, any attribution for that group triggers the callback. The call to the appointed URL passes on data stored at the time of the click in a customizable format.
To match any use case and connect with many third parties we’ve made this feature highly customizable.
- Ability to send fixed values like an affiliate ID.
- Ability to use incoming (extra) parameters, like a clickid, userid or transactionid.
- Option to send out an incoming value under a different parameter name.
- 3 parameters available.
- Data can be sent as JSON object in a POST request, URLencoded in a GET request or simply saved for manual exporting. We also support postbacks to the facebook conversions API.
Configuring postbacks
- Go to the Postback setup page.
- Click the Create postback button in the top-right corner or the edit button in the table to edit an existing postback configuration.
- Give your postback a name, so you can find it back later.
- Select a postback type, this specifies the way we will callback a conversion to your system.
- Set postback url as instructed by the receiving party of the postbacks.
- Select the campaign link you want to apply this postback to. You can only attach the postback to one link.
- To use a parameter the Outgoing column needs to be filled, plus either the Incoming or Fixed value field.
- Hit the save button and you’re done!
Parameter Incoming
This field is filled if you add extra key-value parameters to the Steam Data Suite tracking url (in addition to the existing parameters). The field should contain the name of the parameter you use in the trackingurl to send the additional value. The value will be send out with the Postback call under the name defined in Outgoing below.
Parameter Outgoing
This determins the key used for sending the key-value pair. This allows you to effectively rename a parameter key from how it comes in, to how it is send out.
Parameter Fixed value
Sometimes a key-value pair is the same for every conversion Postback in a campaign/channel. In that case you can fill in the parameter fixed value field instead of the parameter incoming field.
Facebook converions API
We provide general solutions for postbacks, like HTTP POST requests, but in some cases this isn’t enough. Currently, we provide a custom solution for the Facebook conversions API. When setting up a postback, you can select the FB Conversions API type. After you select this postback type, two new fields will appear, Pixel ID and Access token. These values are necessary for us to provide the conversion to the API. You do not need to enter a URL in the postback configuration when using the Facebook conversions API!
In order to get the Pixel ID and Access token, you need to setup an event in Facebook, this can be done from the facebook events manager. From this page, you need to click on “Connect a New Data Source” button in the left-hand menu. Then, you will be asked what data source to connect, you need to select “web”. You do not need to enter a website and can move on without entering one.
The data source should now be setup. To find the Pixel ID, select the newly created data source and select “settings”, you should see the Pixel ID there. After you got the Pixel ID, scroll down to “Conversions API”, there should be a section called “Set up manually”. In that section, click the “Generate access token” button, this will show an access token. Store it safely, as Facebook will not show it again!
Then pass the Pixel ID and access token to us through the Postback setup page and you should be good to go!