Media Postback Macro

Postback macro

“Postback Macro” is used for sending dynamic data collected by DFINERY to the media partners.

You can create a Postback URL using the postback macro list on this page. The DFINERY postback server will check your postback URL whenever the event occurs and send postback to the partner server.

Some “Postback Macro” cannot be used on postback types (Attribution / Event), Attributions and event types(first_install, last_install, last_deeplink). Please see the postback type and postback macro for configuring the postback URL.

Attribution Postback Macro

Attribution postback is the postback data sent to the media's postback server when the user executes "App Open Event".

*App Open Event

• first_install: New Install
• last_install: Last Install (If the new install is only attribution, first_install = last_install)
• last_deeplink: Open the app with deeplink.

Click Data

This is the macro list of tracking link click data. These click data macro will be sent to your server when the attribution has happened.

All these macro can be used on all attribution event types like first_install, last_install, and last_deeplink.

Attribution data

This is the list of attribution data macro.

All these macro can be used on all attribution event type like first_install, last_install, last_deeplink 

Event Postback Macro

Event postback is the in-app event data, collected by DFINERY SDK, sent to your media server.

Event postback macro offers attribution data with the in-app event and in-app event data.

Attribution Data

This is the macro list for attribution data with the in-app event.

These macros can be offered based on *attribution event type.

*Attribution event type

• first_install : First install attribution
• last_install : Last install attribution (If first install is last one first_install = last_install)
• last_deeplink : Last app open attribution
• last : (Regardless attribution event type) Last attribution

Macro can be used in {attribution_type.data_name} format based on the attribution event types.

All these macro can be used on all attribution event type. (first_install, last_install, last_deeplink, last)

Base macro's attribution_type can be substituted by all event attribution event type.

Example) {attibution_type.cb_1} Substitute base macro for all attribution event type.

• {first_install.cb_1} : Click data from first install attribution event
• {last_install.cb_1} : Click data from last install attribution event
• {last_deeplink.cb_1} : Click data from last open attribution event
• {last.cb_1} : (Regardless attribution event type) Click data from last attribution event

Event Data

Send event data, collected by DFINERY SDK, to the media server.

There are two event types: DFINERY SDK “pre-defined event type” and “custom event” using DFINERY SDK.

• DFINERY SDK pre-defined event
  
  • Event which collected directly by DFINERY SDK (Example: app_start , app_open etc)
    
    • evt.group : abx
  • DFINERY SDK pre-defined event (Example: Tutorial_complete, purchase etc)
    • evt.group : abx
• Custom event
  
  • custom event using DFINERY SDK. (not pre-defined)
    • evt.group : custom
• The postback macro of a single product is deprecated. Instead of them, we provide all the data belonging to commerce events as JSON at once, so use {req.evt.param_json} macro. If you want the details and samples about JSON, please send the email to support-tracker@adbrixsupport.zendesk.com.

Appendix

DFINERY pre-defined event

DFINERY can offer pre-defined event data that is commonly used for app marketing.

Attribution Type 

Every attribution must have one attribution type.

{attr_type} macro will return a number value depending on the attribution type.

Attribution Model Type

AD Touch Type

A tracking link that attributes conversion has one ad touch type.

{i_request_type} will return a numeric value depending on the ad touch type.

 If you have any further questions, please let us know through support-tracker@adbrixsupport.zendesk.com.