.svg){kind=icon}
Overview
When a user converts on your Advertiser's website (like making a purchase or installing an app), their system needs to tell Everflow about this Conversion.
An Advertiser does this using an Advertiser postback - a special URL that fires when a Conversion happens:
https://www.eftrackall.com/?nid=1&transaction_id=abc123def456ghi7890&amount=50
This report shows you:
- Which Conversions were successfully recorded (Approved)
- Which ones were rejected
Think of it as a log of every time an Advertiser tries to tell Everflow "hey, this user converted!"
How to Access the Advertiser Postback Report
Using The Advertiser Postback Report
Analyze and manage your Advertiser postback data with various report features.
A Real-Life Example
Let’s say you are trying to configure conversion tracking with a new Advertiser.
You have configured the Base Destination URL and shared your Global/Advertiser Postback with your Advertiser, asking it to be triggered when a new user registers.
The Advertiser informed you that a conversion had occurred but you do not see this conversion in the conversion report.
In this report, you notice:
- A postback URL did record
- Check the postback URL:
http://everflow-demo.servecvr.com/?nid=63&oid=3&transaction_id=86b850e639a248a289739debd6e6eadc - However, the conversion is attributed to a different Partner based on the transaction ID
Then, you can:
- Conclude that the conversion did not show as it was attributed to the wrong Partner
End result? You request a new test to be done in a clean browser, with no prior cookies.
Best Practices
Make sure you're looking at both Conversion and event postbacks when reviewing your data.
This information comes in especially handy when you need to troubleshoot any issues with advertiser postbacks.
