Postback Integration
Postback process is used to send conversion information to Publishers in real time. mTrackit allows publishers to define multiple postback templates.
Postback Template Configuration
The Postback template configuration includes the postback endpoint URL and the list of reporting parameters to be shared.
The list of reporting parameters to be shared in defined using the mTrackIt macros.These are used to map the mTrackit Reporting data to the publishers nomenclature.
publisher_landingpage_id={landing_page_id}&publishers_campiagn_id={campaign_id}In the above example the mTrackIt landing_page_id and campaign_id is mapped to the corresponding parameters in the publishers system.
The below table captures a list of mTrackIt macros which can be used in the postback templates.
Postback Macro
Description
App / Web
mtrk_report_id
A unique auto increment ID
Web
inserted_date
The date when a record entry was added to this table
Web
inserted_time
The datetime when a record entry was added to this table
Web
customer_id
A unique identifier for the app, or website
Web
campaign_id
The campaign id for which the attribution is tracked
Web
landing_page_id
The landing_page identifier received as part of the click request
Web
publisher_id
The publisher_id from whom the click was generated
Web
sub_publisher_id
The sub_publisher_id from whom the click was generated
Web
offer_id
The offer_id received as part of the click
Web
order_id
The order_id received as part of the Pixel Request
Web
click_id
The unique click id generated by the Mtrackit system. This contains the campaign and publisher information
Web
click_ip
The IP address from which the click was originated
Web
click_make
The Make of the device from which the click originated
Web
click_model
The Model of the device from which the click originated
Web
click_time
The datetime at which the click was recorded
Web
click_date
The date on which the click was recorded
Web
conversion_ip
The IP address from which the click was originated
Web
conversion_make
The Make of the device from which the click orginated
Web
conversion_model
The Model of the device from which the click orginated
Web
conversion_status
The status of the conversion ??
Web
conversion_time
The datetime at which the click was recorded
Web
conversion_type
The type of conversion - fingerprint, referer string etc
Web
conversion_date
The date at which the conversion happend
Web
session_referrer
The host domain from which the click was originated
Web
adid
The unique advertising id of the user
App
device_id
The unique device id of the device
App
mac_address
The mac address of the Device WiFi interface of any.
App
user_id
The cookie id associated withe the user?
Web
session_id
The session id information, which indicates a unique session within an app or website
Web
transaction_id
Optional parameter for attribution, generated at server side.
Web
app_version
The version of the app whose install is being attributed
App
os_version
The OS version of the device in which the conversion happend.
App
time_zone
The time zone in which the conversion happend.
Web
revenue_amount
The revenue generated due to the transaction being attributed (for example Sale Revenue)
Web
cost_amount
The cost incurred for the customer due to the attribution.
Web
aff_sub1
Extra parameters which are passed along with the click
Web
aff_sub2
Extra parameters which are passed along with the click
Web
aff_sub3
Extra parameters which are passed along with the click
Web
aff_sub4
Extra parameters which are passed along with the click
Web
aff_sub5
Extra parameters which are passed along with the click
Web
cust_field1
Extra parameters which are passed along with the Pixel
Web
cust_field2
Extra parameters which are passed along with the Pixel
Web
cust_field3
Extra parameters which are passed along with the Pixel
Web
cust_field4
Extra parameters which are passed along with the Pixel
Web
cust_field5
Extra parameters which are passed along with the Pixel
Web
Last updated
Was this helpful?