Postbacks are not yet available for VK Mini Apps. Learn more
Regular event settings
MyTracker provides a list of regular events to generate postbacks (for more details, refer to Postbacks):
Installs, Re-installs
New user
Re-engagements
Registration, First Registration
Authorization, First Authorization
Custom event
Purchase, First Purchase
Custom revenue, First Custom Revenue
For mobile apps, you can send postbacks for any regular events.
For web apps, only new user, re-engagements, registrations,
authorizations, and custom revenue are valid.
On the Events sending tab, select the app you need. The list of events that support postback configuration will be loaded into the form.
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.
Select sending mode for each event:
Do not send;
Send attributed — to send only postbacks related to users attracted by your partner's marketing campaign.
For Purchase and First Purchase events, choose the verification status from the drop-down list:
Send all — send postbacks for all payments, including unverified transactions;
Verified only — send postbacks only when the payment is verified on App Store and Google Play servers.
Click Save.
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 |
React Native |
Web, and
S2S API
On the Events sending tab, select the app you need. The list of regular and custom events that support postback configuration will be loaded into the form.
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.
Select sending mode for each custom event:
Do not send;
Send attributed — to send postbacks for users acquired through the partner's marketing campaign.
Select Application event name.
Only 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 "COMPLETE" to the tracker, while your partner expects to receive "FINISH".
The list of fields may depend on the selected partner:
For some partners, such as VK Ads + 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.
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.
Select all custom events that require a postback by clicking Add event.
For Purchase and First Purchase events, choose the verification status from the drop-down list:
