Sending postbacks

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.

Standard event settings

myTracker provides a list of standard events to generate postbacks (for more details, refer to Postbacks):

  • Installs
  • Re-engagements
  • Re-installs
  • First payment LT/CA
  • Payment LT/CA
  • First Registration LT
  • Registration LT/CA
  • First authorization LT
  • Authorization LT/CA

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 event settings

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.

For more details on event tracking, refer to SDK documentation for iOS | Android | Unity | Flutter | Web

Setting procedure

  1. In the partner list, locate the one for postback configuration.
  2. Click Settings in the relevant partner window.
  3. On the Events sending page, select the app you need. The list of standard and custom events that support postback configuration will be loaded into the form.
  4. 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.

  5. Select sending mode for each event :
    • Send attributed — to send only postbacks related to users attracted by your partner's marketing campaign ;
    • Send all — to send postbacks related to all app users.
  6. 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).

  7. For custom events perform additional configuration steps as follows:
    • Select Application event name. Only the events that have already been tracked can be selected.
    • Specify the event name as used by your partner. This is important because your partner may be looking for the same event under a different name, for example, when a user completes an order, your app may transmit "order_complete" to the tracker, while your partner expects to receive "order_finished".
    • 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.

    • Activate Send params to include event parameters into a postback (all parameters to be transmitted need to be defined in the URL template on your partner’s Postbacks tab).
    • Select all events that require a postback using the Add event button.
  8. Press the Save button.