Postbacks let you inform partners of various events related to your app (installation, purchase, etc.) and synchronise data with your external analytics systems.
myTracker offers flexible postback configuration. You can configure standard and custom events separately and send data on either all users or only those "brought in" by your partner.
myTracker provides a list of standard events to generate postbacks (for more details, refer to Postbacks):
For a mobile app, you can send any standard postbacks. For web apps, you only need re-engagement, registration, and authorization events.
Configuring standard events is as simple as selecting the Sending mode (send all data or just attributed data); for more details, refer to the instructions below.
Custom events are certain events that are specific to an app. For example, adding to cart, reaching new level in a game, etc.
Custom event settings include selectable Sending mode, Event name, and Send params options (for example, for "product added to basket" you can send "identifier" and "number of items"). For more details, refer to the instructions below.
Note that only the events that have been already tracked, i. e. transmitted from your app to myTracker, can be configured.
If you have doubts about which events require postbacks, review the list of supported events and recommendations regarding their implementation, discuss the matter with your partner, or contact our support.
Most partners support only one mode, Send attributed. However, some, for example, myTarget, Google Ads, are set up to receive data related to all of your app users in Send all mode (usually, this is required for remarketing list generation).
myTarget does not require event names used by your partner; all you need to do is enter Application event name.
In Google Ads, event names are pre-set. Thus, you can select an event name used by your partner from a list or enter any other name and select CUSTOM.