Event Postbacks
Event postbacks, at their core, are similar to source postbacks in that they are used to transmit data from one server to another with specified sets of data.
The use-case for event postbacks do vary when comparing them to source postbacks. As discussed in Event Management Overview events fire on certain actions which help to enhance your overall reporting.
Pingtree gives you the option to generate a global postback URL (this can be used for any campaign in your Pingtree org, or a campaign-specific postback URL.
Global Postbacks
You will find the global postback inside of your System Settings -> Event Management section. This view lives in the same area where your events and event lists live as they are both commonly intertwined.
Campaign-Level Postbacks
Campaign-level postbacks will be found inside your Events Manager tab inside your campaign.
Configuring Event Postbacks
Properly configuring your event postbacks is just as important as knowing the actual use-case of the postback. If this is built incorrectly, you may not some or all of your data back properly.
Steps to setting configuring your postback:
Determine if you want to use the Global Postback or Campaign-Level Postback
Base Postback URL example: https://api.pingtree.com/api/event/global/659ddb7fdb968a97h183ab9aDetermine 2 key points
What action are you looking for that will trigger this event postback to fire
What pieces of data do you want fired back
Add in your event ID (if applicable) - While you will generally fire an event postback with a certain event, it's not mandatory. If you are including an event, you will grab the specified event ID from your event list and add ID as a static key:value pair in the URL.
Add the "transaction_id" parameter. It's EXTREMELY important to add this. If this is not added, and/or the partner firing this postback does not include the dynamic value or it's mapped incorrectly, you will NOT be able to attribute your lead data properly.
Hot Tip: When sending out the postback URL to be installed, you should include as much information as possible. Event Id's have a static value (for each particular event) so you can "hard code"' that key:value pair in the URL. Values that require dynamic data to be sent back should have the value formatted in double curly brackets to signify that this is a dynamic value.
This would include parameters such as "transaction_id={{UNIQUE_LEAD_ID}}" or "amount={{REVENUE_AMOUNT}}"
If you already know the parameter that you would map your parameter to such as transaction_id={{sub1}} you can include their actual field in the curly double brackets. In the examples above, both "transaction_id" and "amount" are the formats in which Pingtree will ingest those certain values.
You can send the partner the full postback URL along with how they can fire the postback (GET or POST request), example API response and response codes and any additional information they may need.