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.
When a goal is triggered, eligible postbacks are determined by applying the set of filters configured on each postback. The available postback filters are:
- Game - Trigger this postback for all goals attributed in this game
- Team - Trigger this postback for all goals attributed to this team
- Network - Trigger this postback for all goals attributed to this network (most common)
- Goal Type - Trigger this postback for a specific goal, this is commonly combined with the above filters. E.g. to send D5 retention goal triggers attributed to Facebook back to FB Ads for optimization.
Currently, postbacks must be reviewed and configured by Gamesight staff before they go in effect. If you would like to get a new postback in place please provide the following information to your account manager.
Verb: (GET, POST, etc)
Headers: (List any header values your endpoint expects)
Body: (Provide the format of the body of the request, for POST/PUT requests)
Filters: (What filters do you want to apply, eg "D5 goal triggers attributed to Facebook")
The macros section below provides details on the variables that are available in your postbacks.
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) -
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 -
These macros are only available to postbacks that are defined by the customer. These details cannot be shared with third parties.
Event ID that triggered the Goal -
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 -
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
Updated 2 months ago