Home
Reporting & Analytics
Reporting
Partner Postback Report
Partner Postback Report

SERIES:

Partner Postback Report

Learn how to monitor, troubleshoot, and debug partner postback tracking in Everflow, including step-by-step guides for successful conversion tracking with affiliate networks, ad platforms, and marketing partners.

Overview

When running traffic with Partners (like Meta or affiliates), you need to tell their systems when conversions happen. This is often done through a postback URL - a special URL provided by your Partner that Everflow calls to notify them about conversions.

Here's how it works:

  1. Your Partner sends traffic using their tracking link with their Click ID
    https://yoursite.com/offer?click_id=123abc
  2. When a conversion happens, Everflow needs to tell your Partner about it using their postback URL
    https://partner-system.com/conversion?click_id=123abc

The Partner Postback Report shows you if these notification URLs are working properly.

This is crucial because:

  • Failed postbacks mean Partners can't see their Conversions
  • Ad platforms need Conversion data to optimize campaigns
  • Affiliates need Conversion data to bill you correctly

Key Features

  • Success/Failure status of each postback delivery
  • Payload preview showing what data was sent
  • Debug Info showing server responses

How to Access the Partner Postback Report

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

Using The Partner Postback Report

Monitor and analyze postback delivery to Partners with this comprehensive report.

1
Set Your Date Range
Select your desired timeframe
Shows postback delivery status for selected period
2
Apply Filters
Click
Add Filter
to narrow results by:
Offer: Search by specific offers
Partner: Filter by partner name
Use
Clear
to reset filters
3
Status Filter
Click
All
dropdown to filter by:
Success (green)
Failure (red)
All postbacks
4
Report Actions
Click top-right menu to:
Save report configuration
Load saved reports
Schedule Report delivery
Request Report for large datasets
Copy Link to report
Show API Request
5
Row Actions
Click vertical dots at end of any row to:
View Click Details
View Conversion Details
View Offer
View Partner
View Debug Info
View Flowchart
6
Additional Features
Search bar
for quick filtering
Type column shows postback category (like Conversion)
Payload column displays the actual postback URL

A Real-Life Example

Let's say you're working with an affiliate network that uses a Global Partner Postback:

Checking the Partner Postback Report, you notice:
Multiple failed postbacks for your top affiliate network
Debug Info reveals:
Postback Url: https://networkname.com/postback?clickid={sub1}
Status: 400
Headers: Content-Type: [application/json]
Return: {"status":2}
Investigating the Payload and Debug Info:
Status 400 indicates a bad request
Their system isn't accepting the Click ID format
The Global postback is failing for all conversions
Take action:
Contact the Partner to verify their correct postback URL format
Confirm with the Partner that the Partner Tracking Link is configured properly in their platform (i.e. their click id is passed in the correct parameter - sub1 in the above example)
Update the postback URL to their specification, if needed
Test with a new conversion

This shows how the Partner Postback Report's Debug Info helps you identify formatting issues in your postback configuration, especially important for Global postbacks since they affect all conversions for that Partner.

Best Practices

Keep a close eye on the status column to quickly spot any postback failures. When you do find errors, use the debug info to understand exactly what went wrong.

Make sure your partners' postback URLs are always up to date, and whenever you make any changes, test them right away to ensure everything's working properly.

Automated Postback Deactivation
Any postback that reaches 10 failed delivery attempts with zero successful fires, where the span from the first failure to the latest exceeds 72 hours, is automatically deactivated. Everflow makes up to 5 attempts per logged failure, so that threshold can be met by as few as 2 logged failures more than 72 hours apart. When this happens, an alert is sent to all Account Administrators and the Affiliate or Advertiser Manager tied to the offer, with troubleshooting details so you can resolve the issue and reactivate.
Next in This Series