Postback parameters

Use parameters in postback URL templates to send additional information to the partner. Parameters can be assigned fixed values or macros that pass dynamic data from tracking links, device information, application event parameters, and partner integration settings.

For example, in this URL template
http://site.com/postback/?param1=123&idfa={mt_idfa}&event-time={mt_event_ts}&revenue={mt_payment_sum_src}:

• 123 — fixed value (constant)
• {mt_idfa} — device identifier macro
• {mt_event_ts} — event timestamp macro
• {mt_payment_sum_src} — payment sum macro

Before sending a postback to your partner, MyTracker automatically replaces macros with specific values. For example, the above template may turn into such a URL:
http://site.com/postback/?param1=123&idfa=AAAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAAA&event-time=1505486690&revenue=5.9999
with following replacements:

• {mt_idfa} → AAAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAAA
• {mt_event_ts} → 1505486690
• {mt_payment_sum_src} → 5.9999

Parameter types in postbacks

The following parameters can be passed in postbacks:

• Constant is a specific value, sent to a partner without changes.
• Tracking link parameter is any GET-parameter that is passed in partner's tracking links. When setting up the postback, you should specify the name of the parameter from the tracking link in the "parameter name" field. When sending a postback, the value of this parameter will be passed.
• SubID parameters are MyTracker parameters that can be used for additional granularity on traffic sources within a single tracking link:
  • mt_network
  • mt_campaign
  • mt_adset
  • mt_creative
  • mt_medium
  • mt_sub1, mt_sub2, mt_sub3, mt_sub4, mt_sub5
  For more details, refer to the SubID and UTM parameters section.
• MyTracker system parameters are parameters through which you can pass data that is already in MyTracker: device identifiers, event parameters, user information, etc. Like SubID, they have the mt_ prefix.
• Custom event parameter. When sending a postback, the value of the specified event parameter is substituted. They have the mtep_ prefix.
• JSON is required for partners that accept postback parameters as JSON object. They have the mtj_ prefix.
• Platform dependent constant allows to send a specified value dependent on the application platform. Platform values should be written to a JSON object using the mtpc_ prefix.
• Campaign parameters are the value of a unique key associated with a specific partner campaign. When setting up postback, parameters are automatically pulled up in the drop-down list of parameter types from the Campaign Parameters tab and have the mtpp_ prefix. See the Campaign parameters section.
• Custom partner parameters. For some partners, the postback must contain a unique advertiser/application key (for example, VK Ads, Liftoff). The value of this parameter for each application is specified when configuring event sending. The parameter macro with the mtap_ prefix and the partner name will be automatically added to the drop-down list of parameter types when setting up postbacks.

MyTracker system parameters

List of MyTracker system parameter macros that can be used in postbacks:

Device info

Hashed device IDs

App info

User info

Event info

Payment info

Postback info

Traffic info

Attribution info