Postbacks let you send data collected by the SDK to a separate third-party server. Leveraging the same triggers and traits you use to display an in-app message, you can configure the SDK to send customized data to a third-party destination.

Note: This functionality requires SDK version 4.6.0 or later.

Postback messages are queued and follow all existing online/offline rules that govern analytics data collection. Note that postback messages do not cancel the rest of the messages if a message matches (like shown-messages do). This allows for multiple postbacks to occur on the same analytics hit.

See the "postbacks" row in ADBMobile JSON Config for the definition.

Template expansions are available in both the templateurl and templatebody properties. Template items take the form of "{key}", where "key" is a context-data key, or traditional data key. The values available for template expansion are limited to the standard Lifecycle variables list, in addition to any custom data attached to the hit that triggers the message. No historical-based or segment-based data is available at this time.

There are also specific, reserved templates that the SDK will replace for you automatically with internal data known to the SDK.

This list includes:

Token Name Token Description


Returns SDK version.


Resolves to a random number between 1 and 100000000.


Returns Advertiser ID for Android. Note, this only works if you have used submitAdvertisingIdentifierTask.


Returns the Push Identifier token. Note, this only works if you have used setPushIdentifier.


Returns current timestamp in epoch time.


Returns current timestamp in JavaScript (ISO 8601) format.

  • Postbacks Example
    Definition and source code examples for the Postbacks feature.
  • Parent topic: Analytics