Sending postbacks

Postbacks let you inform partners of various events related to your app (installation, purchase, etc.) and synchronize data with your external analytics systems.

MyTracker offers a flexible postback configuration. You can configure regular and custom events separately and send data on all users or only those "brought in" by your partner.

Regular event settings

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

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

For a mobile app, you can send any regular postbacks. For web apps, you only need re-engagements, registrations, authorizations, and custom payments.

To send regular event postbacks:

  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 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.
    For Payment events select the mode: Send all or Verified only.
  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. Press the Save button.

Custom event settings

Custom events are certain events that are specific to an app. For example, adding to cart, reaching a new level in a game, etc.

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 the SDK documentation for iOS | Android | Unity | Flutter | Web, and S2S API

To send custom event postbacks:

  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 regular 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 custom 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. Select Application event name. Only the events that have already been tracked can be selected. The untracked events you can enter manually.
  8. 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 "COMPLETE" to the tracker, while your partner expects to receive "FINISH".
  9. The list of fields may depend on the selected partner:

    • For some partners, such as myTarget, you do not need to enter Partner event name, because the partner accepts the same names you send to MyTracker.
    • For other partners, such as Google Ads, event names are pre-set. Thus, you can select an event name used by your partner from a list or select CUSTOM and enter any other Event name.
  10. Add +event parameter to clarify the conditions for sending a postback. For example, you can send a "level up" postback only if the "level" parameter is "10".

    For each parameter, specify a value using the operators Equals or select the operator Exists if the parameter can be with any value.

  11. In this step, you set the conditions for sending a postback. The list of parameters that will be passed to the partner should be defined in advance in the postback template. For details, refer to the URL template section.

  12. Select all events that require a postback using the Add event button.
  13. Press the Save button.