Home
Reporting & Analytics
Reporting
Advertiser Postback Report
Advertiser Postback Report

SERIES:

Advertiser Postback Report

Learn how to track, monitor, and troubleshoot Advertiser Conversion postbacks in Everflow's reporting, including setup guides, best practices, and real-world examples for affiliate marketers and ad networks.

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!"

Good to Remember
The Advertiser Postback Report shows the status of Conversions sent from your Advertisers to Everflow, helping you identify which Conversions were accepted or rejected, and why.

How to Access the Advertiser Postback Report

Click on the hamburger menu
in the top left corner of your Everflow dashboard.
Go to the
Reporting
section.
Select
Advertiser Postback
from the list of reports.

Using The Advertiser Postback Report

Analyze and manage your Advertiser postback data with various report features.

1
Navigation & Filtering
Date Range:
Select the period you want to analyze
Add Filter
button lets you narrow results by:
Advertiser: Focus on specific brands
Offer: Track specific campaign postbacks
Partner: Monitor postbacks for specific traffic sources
2
Data Management
For large datasets, you'll see a warning that only the first 1,000 rows can be displayed. Use the
Request Report
button to get the full dataset asynchronously.
3
Report Actions
Click the top-right menu to:
Save: Store your current report configuration
Load: Retrieve saved report settings
Schedule Report: Set up automated report delivery
Request Report: Get full datasets
Copy Link: Share report URL with team members
Show API Request: View API call format
4
Customizing Your View
Click Table Actions to:
Export: Download report data
Toggle visible columns using Columns Customization
Pixel ID
Date
Partner
Offer
Advertiser
Postback URL
Conversion ID
Transaction ID
And more...
5
Row-Level Actions
Click the vertical dots on any row to:
View Click Details
View Conversion Details
View Offer
View Partner
View Advertiser
Conversion Method Display: The "CV Method" column shows the Offer's configured tracking method, not the actual method used for each specific conversion.

Data Retention: Advertiser postback data is only stored for 90 days before being automatically removed from the system.

A Real-Life Example

Let’s say you are trying to configure conversion tracking with a new Advertiser.

You have configured the Default Landing Page 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.

Troubleshooting Missing Conversions

If your Advertiser reports a Conversion that you can't find in your Conversion report, the Advertiser Postback Report is the best place to start. Before you begin, it helps to have the Offer ID, the Transaction ID (if available), the Advertiser postback format, and either the payload of the Conversion or the redirect URL from the click details.

Work through the following checks:

Confirm the Advertiser actually sees the Conversion on their side, then check whether it came into Everflow but landed under Rejected in your Conversion reports.
Verify that the Base Destination URL is set up correctly and is passing the transaction ID into the click details through the redirect. For example:
http://domain.com/?aff_sub={transaction_id}
Confirm the postback passes the transaction ID back using the macro from the Advertiser's platform. For example:
http://domain.com/?nid=NID&transaction_id={aff_sub}
Open Reporting > Advertiser Postback to confirm the Advertiser actually fired the postback to Everflow.
If you still need more detail, ask the Advertiser for the payload of a Conversion, or for a test Conversion to be sent.
Matching the macros: The macro you place in the postback is usually the one that matches the parameter the transaction ID was originally passed into within the Base Destination URL. If the transaction ID arrives in
aff_sub
, the postback should send it back from
{aff_sub}
.

Test Mode Conversions

You can send a Conversion through in Test Mode by adding the &test=VALUE parameter to the Advertiser postback. You can replace VALUE with any value, but it cannot be left empty (for example, &test=1).

A Test Mode Conversion records with a Revenue and Payout of 0, so it won't affect your real numbers.

Good to Remember
Because "test" is a restricted parameter, it is not shown in the Conversion Details. To confirm that a Conversion came through in Test Mode, check the Advertiser Postback Report.
Next in This Series