AXAffilinext Help Center

Postback Health

Running campaigns whose conversions stopped while clicks kept coming, which usually means the advertiser's postback broke, with the likely cause. For network admins.

A broken postback doesn't cause errors: conversions just stop arriving and reports quietly show less. This page checks every running campaign every 10 minutes and flags the ones that should have converted by now but haven't, so you can fix the postback before a whole day of conversions is lost.

What you can do here

  • Summary — How many running campaigns stopped converting, are healthy, are still learning, or have muted alerts.
  • Needs attention — Opens first when anything is flagged. Each row says how long it's been silent and the likely cause: postbacks arriving but rejected (with the most common reason), or none arriving at all.
  • Check now — Runs the check immediately instead of waiting for the next 10-minute run.
  • Alerts — When a campaign is flagged, admins with the Campaigns permission get a bell notification and an email; one alert per advertiser when several of its campaigns stop together. Another notice follows when conversions resume.
  • Snooze and mute — Snooze stops alerts for 24 hours or 7 days; mute stops them until you unmute. The campaign keeps being checked either way.

Fields and settings

FieldWhat it does
AllowanceHow long this campaign's conversions usually take to arrive after the click (the time 90% of them arrive within, between 1 and 72 hours). Clicks newer than that aren't counted yet, so slow offers and advertisers who send postbacks in batches aren't flagged early.
ExpectedConversions that should have arrived by now from the clicks since the last conversion, at the campaign's usual rate. A campaign is flagged at about 5.
Usual rateConversions per click over the last 30 days, leaving out the clicks since the last conversion.

Limitations

  • Supported: Every active web campaign whose advertiser is active is checked, whatever the postback method (advertiser token, platform token or campaign secret).
  • Depends on: A campaign needs 10 conversions in the last 30 days before it can be judged; until then it shows as Learning.
  • Not supported: App campaigns (mobile installs) aren't checked yet.
  • Restricted: The rejected-postback count comes from the Advertiser Postback log, which keeps the latest 2,000 attempts and starts empty after a server restart.

Common mistakes

  • Muting instead of fixing — Muting only hides the alert. If the advertiser's postback is broken, conversions are still being lost. Snooze while you wait for them to fix it.
  • Changing the advertiser's postback URL to test — Use Tracking → Advertiser Postback to see each attempt and why it was rejected. The flag clears by itself with the next real conversion.

Troubleshooting

  • Flagged, but the advertiser says postbacks are firing — Open Tracking → Advertiser Postback. If attempts are rejected, the reason tells you what's wrong: usually a wrong or missing token, or a click ID macro that isn't passing our click ID back. If there are no attempts, the postback is going somewhere else.
  • An offer that pays out in daily batches keeps getting flagged — The allowance learns from the campaign's own history, so it adapts after a few days of batches. Until then, snooze it for 7 days.