Postbacks

A postback is a way to notify partner about a target action being performed by a user (for example an install stemming from their campaign). These notifications are usually done in the form of HTTP requests.

For most integrated partners we've already configured postbacks — all you need to do is set the sending mode (see the Sending postbacks section).

However, sometimes ready-made postbacks are not enough:

• When you add a new partner
• When you need to send postbacks to your own or third-party analytics system

In these cases, you can create additional postbacks and use them just like the regular ones.

Add postback

Before you read on, ask your partner for documentation or a description of postback requirements.

1. Select the Campaigns > Partners menu.
2. In the list, find the partner you want and click on its title or logo.
3. Go to the Postbacks tab and click Add.
4. Fill out the form:
• Account * — the new postback will be added to the selected account. For details, see the Account section. Note:
  • If you have only one account, it'll be selected by default.
  • If you are adding a postback for an integrated partner, you can choose any account. We recommend that you contact our support team before you do this. In most cases, integrated partners already have all the necessary postbacks and you do not need to add anything.
  • If you are adding a postback for a new partner, the account to which the partner belongs will be selected automatically.
• Title * — postback name that will be shown in all future reports.

We recommend you standardize the naming scheme. This will make it easier to navigate if postbacks stack up. For example:
Partner name | install

• Event * — an install, reattribution or in-app event that triggers a postback. The list of supported events is provided below.
• URL template * — a template of the URL where the postback will be sent to (HTTP request). Postback parameters are based on standard GET-parameters http://site.com?myparam={myparam}&idfa={mt_idfa}. You can input the parameters directly to the URL or use a parameter kit for URL templates. See details in the section below.

* — required fields.

5. Click Add.

Now you can set up postbacks for all partner campaigns and add additional postbacks to a specific campaign.

URL template

A URL template is a regular URL that uses so-called macros (a special variable that MyTracker will replace with actual values before sending a postback to an integrated partner).

To create a URL template:

1. In the URL template field, type a base part of the URL (until the question mark):
   http://site.com/postback/

You can type parameters in the URL template field or add them using the following instructions

2. Click Add parameters.
3. Add all the parameters specified in the partner documentation.
   For each parameter:
   
   1. Specify a Name — this field will match the variable in the GET query.
   2. Select a Parameter type:
      • Constant — a specific value, sent to a partner without changes.
      • Tracking link parameter — if additional GET-parameters are added to the ad click URL, they can be used when sending postbacks. In the field "click url parameter name", specify the parameter name.
      • JSON — a JavaScript Object Notation object, which you can send in postbacks.
      • Platform dependent constant — platform values that will be sent to a partner without changes. Write platform values with the mtpc_ prefix in JSON object.
      • mt_* — MyTracker macros through which you can pass data that is already in MyTracker: device IDs, event parameters, user info. For a complete list, see the section MyTracker macros.
      • mtpp_* — campaign parameters. The list of parameters is loaded automatically from the partner's campaigns in MyTracker. See the section Campaign parameters.
   3. Click  Add to the right. As a result, a new parameter will appear in the URL template field, and you will see a new line for adding the next parameter.

Before saving the form, make sure that the URL template contains all the necessary parameters. Do not forget to click Add to the right of the last parameter for which you specified the name and type. Until you click, the parameter will not be added to the URL template.

4. Click  Add in the add postback form (or Save in the edit form).

Supported events

You can send postbacks for the following events:

• Installs
• New user
• Re-engagement
• Re-install
• First payment LT/CA
• Payment LT/CA
• First custom payment LT/CA
• Custom payment LT/CA
• First Registration LT
• Registration LT/CA
• First authorization LT
• Authorization LT/CA
• Custom event LT/CA

For a mobile app, you can send any postbacks listed. For web apps, only new users, re-engagements, registrations, authorizations, custom payments are valid.

Installs

An Install event is logged when a user first installs and launches an app with an embedded MyTracker SDK

An Install event occurs regardless of a Launch, but if the user never launches the app, the SDK will not be able to send the install data to the server. Hence, MyTracker will not register an install

Unique event: happens on a device only once.

Use case: for most CPI partners, install postback is a must for integration.

New user

New user is an authorized user who appeared in the project for the first time. The "New user" event occurs when MyTracker logged the first event with the user ID.

The first event can be not only registration, but also authorization, payment, etc. This is possible if the user registered in the application before the app developer connected the MyTracker SDK and configured the user ID transfer.

Unique event: happens only once.

Use case: postbacks are needed if you are optimizing the user engagement campaigns. Postbacks show the actual number of new customers, who may have installed the app on multiple devices or switched mobile and web platforms. Learn more

Re-engagement

Re-engagement is the activity before which a user has not interacted with the app within the "Inactivity window" (by default, 30 days).

Activity involves a registration, authorization, launch, website visit, in-app impression, or payment.

You can send re-engagement postbacks by device and user:

• Re-engagement^d is a notification of re-installs and re-engagement on a device.
• Re-engagement^u is a notification of returning registered users to your project. Learn more

As an example, consider the order of actions leading up to the mobile re-engagement^d:

1. A user installs an app on a device. At this point, the "time of last activity" matches the "time of install".
2. (optional) The user launches an app, registers, authorizes, visits a website, views an advertising in an app, or makes the payment. With each of such user's actions, the "last activity time" is updated and matches the time of the last user's action.
3. More than 30 days have passed since the "last activity" (30 days is the customisable value. It's called the "Inactivity window", set for each app). MyTracker has recorded no user's actions during that time.
4. MyTracker records activity → Logs re-engagement.

Non-unique event: сan happen on a device multiple times.

Use case: re-engagement postbacks are needed if you are running a remarketing campaign to connect with people who previously interacted with your app.

Re-install

A re-install means a user installed a mobile app again after removing it and being "dormant" during the "Inactivity window" (30 days by default)

The order of actions, leading up to re-installing:

1. A user installs an app on a device. At this point, the time of "last activity" matches the "time of installation".
2. (optional) The user launches the app. With each launch, the "last activity time" is updated — it becomes the same as the last launch time.
3. The user uninstalls the app.
4. More than 30 days have passed since the "last activity" (30 days — customisable value). It's called the "Inactivity window" and is set for each app). There were no launches during that time.
5. The user re-installs (and launches) the app → MyTracker logs re-install. A Re-install event occurs regardless of a Launch has followed. But if the user never launches the app, the SDK will not be able to send the re-install data to the server.

Non-unique event: сan happen on a device multiple times.

Use case: re-install postbacks are needed if you are running a remarketing campaign to connect with people who previously interacted with your app.

First payment LT/CA

First payment LT is the first payment in the entire lifetime of a user/device.
First payment CA is the first payment since the last attribution (install, re-engagement or re-install of an app).

An LT event is unique.
An CA event is not unique: it сan happen multiple times over the lifetime of a device (but only once per attribution).

Use case: postbacks on the first payment can be used in campaigns based on the CPA model, where the target event is "turning the user into a paying". They can also be used in combination with regular Install postbacks to inform a partner about the quality of the audience they bring in (provided the partner supports campaign optimization).

The LT version of events should be utilized in user acquisition campaigns, the CA version — in remarketing campaigns.

Payment LT/CA

Payment LT — any payment.
Payment CA — a payment within the current attribution period (postbacks on the current campaign will stop if reattribution is logged).

Both these Events are not unique, and сan happen multiple times over the lifetime of a user/device

Use case: postbacks on the payment can be used in campaigns based on the "percentage of income" model. They can also be used in combination with regular Install postbacks to inform the partner about the quality of the audience they are brought in (if the partner supports campaign optimization).

The LT version of the event should be utilized in user acquisition campaigns, the CA version — in remarketing campaigns.

First custom payment LT/CA

First custom payment LT is the first payment in the entire lifetime of a user/device, uploaded to MyTracker via S2S API.
First custom payment CA is the first payment since the last attribution (install, re-engagement, or re-install of an app), uploaded to MyTracker via S2S API.

For details about custom revenue, refer to the Revenue tracking section

An LT event is unique.
An CA event is not unique: it сan happen multiple times over the lifetime of a device (but only once per attribution).

Use case: postbacks on the first custom payment can be used in campaigns based on the CPA model, where the target event is "turning the user into a paying". They can also be used in combination with regular Install and Registration postbacks to inform a partner about the quality of the audience they bring in (provided the partner supports campaign optimization).

The LT version of events should be utilized in user acquisition campaigns, the CA version — in remarketing campaigns.

Custom payment LT/CA

Custom payment LT — any payment, uploaded via S2S API.
Custom payment CA — a payment within the current attribution period, uploaded via S2S API (postbacks on the current campaign will stop if reattribution is logged).

For details about custom revenue, refer to the Revenue tracking section

Both these Events are not unique, and сan happen multiple times over the lifetime of a user/device

Use case: postbacks on the custom payment can be used in campaigns based on the "percentage of income" model. They can also be used in combination with regular Install and Registration postbacks to inform the partner about the quality of the audience they are brought in (if the partner supports campaign optimization).

The LT version of the event should be utilized in user acquisition campaigns, the CA version — in remarketing campaigns.

First registration LT

First registration LT is the first registration in the entire lifetime of a device.

This postback relates to Event LT metrics named mt_registration.
Note it is postbacks on a device event, not users. It means that if a user has multiple accounts in the app, only one registration will be the first.

Unique event: happens on a device only once.

Use case: postbacks on the first registration can be used in campaigns based on the CPA model, where the target event is "the user registration". They can also be used in combination with regular Install postbacks to inform a partner about the quality of the audience they bring in (provided the partner supports campaign optimization).

Registration LT/CA

Registration LT — any registration on the device.
Registration CA — a registration within the current attribution period (postbacks on the current campaign will stop if reattribution is logged).

This postback relates to Event LT metrics named mt_registration.
Note it is postbacks on a device event, not users.

Both these Events are not unique, and сan happen multiple times over the lifetime of a device. For instance, two users or one user under different accounts can register on the same device.

Use case: postbacks on the registration can be used in combination with regular Install postbacks to inform the partner about the quality of the audience they are brought in (if the partner supports campaign optimization).

The LT version of the event should be utilized in user acquisition campaigns, the CA version — in remarketing campaigns.

First authorization LT

First authorization LT is the first authorization in the entire lifetime of a device.

This postback relates to Event LT metrics named mt_login.
Note it is postbacks on a device event, not users. It means that if a user has already authorized on other devices, authorization on a new one still is considered the first.

Unique event: happens on a device only once.

Use case: postbacks on the first authorization can be used in campaigns based on the CPA model, where the target event is "the user authorization". They can also be used in combination with regular Install postbacks to inform a partner about the quality of the audience they bring in (provided the partner supports campaign optimization).

Authorization LT/CA

Authorization LT — any authorization on the device.
Authorization CA — an authorization within the current attribution period (postbacks on the current campaign will stop if reattribution is logged).

This postback relates to Event LT metrics named mt_login.
Note it is postbacks on a device event, not users.

Both these Events are not unique, and сan happen multiple times over the lifetime of a device.

Use case: postbacks on the authorization can be used in combination with regular Install postbacks to inform the partner about the quality of the audience they are brought in (if the partner supports campaign optimization).

The LT version of the event should be utilized in user acquisition campaigns, the CA version — in remarketing campaigns.

Custom event LT/CA

These are events that are specific to an app. For example, adding to basket, test drive, and so on App developer set the names for custom events and their parameters by themselves, except for events that are pre-configured in the MyTracker SDK (registration, login, invite, and levelling up). Learn more for iOS | Android | Unity | Flutter | Web

You (your programmers) control the uniqueness of events. Depending on the logic you’ve used for an event, it can be either unique (for example, completing a game tutorial) or repeatable (adding to basket).

The difference between the LT and CA versions is exactly the same as for other events. LT events happen over the entire lifetime of an audience, and they are not affected by reattribution. CA events can only happen during the current attribution: from the moment of attribution (install, first visit, re-engagement or re-install) to the next reattribution (re-install of the app or re-engagement).

How you use these depends on the kind of an event and the thinking behind it. The main principles are the same as for the other events:

• CPA campaigns (replaсing or supplementing the regular install postbacks).
• The LT version for regular campaigns, CA — for remarketing campaigns.

Custom events are also work well for remarketing lists (for partners that support them, like Google Ads).

LT and CA events: which to choose

Rule of thumb

If you are not running remarketing campaigns, use LT events only:

• Install
• New user
• First payment LT
• Payment LT
• First Registration LT
• Registration LT
• First authorization LT
• Authorization LT
• Custom event LT

The reverse is also true. For remarketing campaigns you should use CA events:

• Re-engagement
• Re-install
• First payment CA
• Payment CA
• Registration CA
• Authorization CA
• Custom event CA

Similarity to reports

If you have already figured out the LT (LifeTime) and CA (Current Attribution) report metrics, then understanding the postback events algorithm will be a breeze. The same logic applies.

For example, if you enable the "Payment LT" postback, the number of sent postbacks will be equal to the value of the "Transactions LT" metric in reports. And if you enable the "Payment CA" postback, the number of sent postbacks will match the value of "Transactions CA" metric.

What are LT and CA

LifeTime (LT) events and report metrics represent the entire life of a device/user, starting with the first interaction with an app (install or website visit) and until the "death" of the device. Intermediate reattribution does not affect them in any way.

Current Attribution (CA) events and report metrics exist in the context of a single attribution: from the moment of attribution (install, first visit, re-engagement or re-install) to the next reattribution (re-install or re-engagement). What happens outside the current attribution does not affect CA events in any way.

If you still have questions, please contact our support team