Gamesight has a robust postback (webhook) system that provides real-time notifications of new attributed installs. These postbacks can be sent to Ad Networks, BI platforms, or other external services that would want to be notified of new attributed goals.
Postbacks are sent as HTTP requests to an external web server, most frequently GET or POST requests.
Postbacks are only available for triggered Goals. Postbacks for clicks/impressions are not supported.
To setup postbacks for a particular network, navigate to the tracker page and click on the
Postbacks tab. Top level network trackers will have a postback created automatically for your primary conversion goal. You can add additional goals as triggers for this postback or create a new postback for those goals.
Many networks have postbacks enabled that only require you to configure a few parameters. But if you want a fully custom postback that will send goal data back to an internal BI system, you can do so by clicking
Add Postback and selecting
Custom URL from the select. This will reveal an input for the HTTP method and URL where you would like us to send your goal data. When filling out the parameters you can select from a list of macros that we will replace with information about the touchpoint, event, and goal.
When postbacks are created they are scoped to the same Game, Team, and Network as the tracker.
When setting up a new postback there are many macros that are available. Macros are dynamic values or variables that you can request
These macros are available on all postbacks.
|The Touchpoint ID that was attributed to the Goal (either Click or Impression ID) - |
|Either the |
|The type of touchpoint attributed - |
|Time the touchpoint was triggered - |
|Sub 1 value from tracking link - ||-|
|Sub 2 value from tracking link - ||-|
|Sub 3 value from tracking link - ||-|
|Sub 4 value from tracking link - ||-|
|Sub 5 value from tracking link - ||-|
|The Click ID that was attributed to the Goal. Empty if touchpoint was an Impression - |
|The Impression ID that was attributed to the Goal. Empty if touchpoint was a Click - |
|Timestamp that the Goal was created at - |
|The Goal Type ID that triggered with postback - |
|The type of trigger that occurred - |
|A unique ID for this specific postback request. Can be useful for deduplication or as a primary key for postback logs - |
|Event ID that triggered the Goal - |
|User ID for the Event that triggered the Goal - |
|Hashed version of the User ID for the Event that triggered the Goal - |
|Game ID for the Event that triggered the Goal - |
|Type of the Event that triggered the Goal - |
|Platform included with this event - |
|The JSON encoded list of external IDs passed with this event payload - |
|The Country detected for this Event, based on IP geolocation - |
|The Revenue amount passed with this event - |
|The Revenue currency passed with this event - |
|Timestamp of the Event that triggered the Goal - |
|The revenue amount associated with this Goal - |
|The revenue currency associated with this Goal. Currently this is always normalized to USD - |
|Whether this goal is attributed or unattributed|
|Touchpoint's Game ID - |
|Touchpoint's Team ID - |
|Touchpoint's Network - |
|Touchpoint's Campaign - |
|Touchpoint's Ad Group - |
|Touchpoint's Ad - |
|Touchpoint's Team Name* - |
|Touchpoint's Network Name* - |
|Touchpoint's Campaign Name* |
|Touchpoint's Ad Group Name* |
|Touchpoint's Ad Name* -|
|Touchpoint's Session ID - |
* Touchpoint names for platforms with Tracker Hierarchy Mirroring (Facebook, Google CM, etc) may not be present at the time of postback for the first few hours after a new campaign goes live (our systems pull down new campaign names from external platforms every few hours). If a name is not set for the Tracker, these fields will fallback to the ID (eg touchpoint.campaign_name will be the same as touchpoint.campaign).
Additional parameters can be made available during Network Tracker configuration. These fields are generally used to define values like security keys or other client-specific Network parameters. All of these Macros are of the form
All query parameters present in the Touchpoint that triggered the postback are available for use as postback Macros. You can access these fields through the
The postback system also supports several transforms that will adjust the value of the postback macro before replacing it into your postback request.
|JSON encodes the parameter. This is useful if you are writing postbacks into a JSON object to ensure that any special characters are properly escaped|
|URL encodes the parameter with plusses. This is useful if your postback accepts values like names and you would like to ensure any special characters are properly escaped|
|JSON encodes the parameter, then URL encodes the resulting value|
You can view the Postback Log for each individual postback that you have set up in Gamesight for your Network Trackers.
From the Tracker Configuration page, click on the Tracker that you want to view your postbacks for. Next, click the Postbacks tab and click on the postback that you want to view logs for - followed by clicking the "View Logs" button as shown below.
Using the Filters tab, you can set a specific time range for your search. Using the Display tab, you can add additional columns of data such as the User ID, Game ID, Request Headers, Request Body, etc. as shown below.
Updated 5 months ago