AXAffilinext Help Center

Conversion review

Every pending conversion and why it's waiting, with bulk approve and reject. For network admins.

Conversions that aren't approved yet wait here, each with the reason it's waiting: a fraud rule flagged it, a cap or budget was reached, it came after the attribution window, the visitor turned out to be outside the campaign's countries, the postback had no revenue for a revenue-share offer, or the advertiser simply sent it as pending. Approve or reject one at a time, a page at a time, or everything matching your filters.

What you can do here

  • Why it's waiting — Colour-coded reasons: red for fraud rules, amber for caps and budgets, blue for policy (attribution window, countries, no status), violet for pricing, grey for the advertiser or an admin. Hover a reason for the detail, such as which rule or which country.
  • Bulk decisions — Tick rows, or tick the header box and then Select all … matching to include every page. Approve or reject with an optional note for the audit log.
  • Filters — By reason, period, campaign and publisher; search by conversion, click or transaction ID; sort newest, oldest or by payout.
  • Totals — How much payout and revenue is waiting, so you know what's at stake before deciding.

Fields and settings

FieldWhat it does
ReasonsWhy a conversion is pending. Values: Flagged by a fraud rule a conversion rule set to flag matched (too soon after the click, a publisher burst, repeat conversions from one IP); Cap or budget reached the campaign had reached a cap or its budget when the conversion arrived; Outside the attribution window it arrived later than the campaign's attribution window after the click; Visitor outside the campaign's countries the click's country was only found after it went through, and it isn't one the campaign accepts; Revenue missing from the postback a revenue-share offer's postback had no revenue, so the payout would be 0; Pending at the advertiser the advertiser sent it as pending (or hold); Postback sent no status the network holds conversions without a status (Settings → Campaign & Offer).

How to use it

  1. Start with a reason chip, for example Flagged by a fraud rule, so similar conversions are decided together.
  2. Narrow by campaign or publisher, check the totals, then select the page (or everything matching).
  3. Approve or reject, adding a note such as who you checked with. Each publisher is notified through their postbacks.

Limitations

  • Supported: Decisions are final against the advertiser: re-sending approved won't overturn a rejection, and won't release a conversion you put back to pending. A later chargeback or refund from the advertiser still applies.
  • Supported: Publishers' campaign postbacks, and their global postbacks set to fire on that status, are sent for every decision.
  • Depends on: Only the newest 5,000 pending conversions in the period are listed; narrow the period or filters to reach older ones.
  • Restricted: Needs the Finance permission: approving makes a conversion payable.

Common mistakes

  • Approving a whole fraud batch without looking — A fraud rule flagged them for a reason. Open a few clicks in Click Intelligence first, or reject the batch and approve the exceptions.
  • Invoicing before reviewing — Only approved conversions are invoiced. Clear the queue before generating invoices, or the pending ones roll into a later invoice.

Troubleshooting

  • Some conversions were skipped — They were approved or rejected meanwhile (by someone else, the API or the advertiser) and were left as they are.
  • The publisher says they didn't receive the approval — Check their postback logs and the conversion's publisher postback result. Global postbacks set to New conversions only don't fire on later status changes.