AXAffilinext Help Center

Tracking tools

Build advertiser postback URLs, test publisher postbacks, inspect advertiser postback logs and fire pixels. For network admins.

Four tools for getting conversions flowing: build the postback URL you give an advertiser, fire a test conversion to a publisher's postback, read the postbacks advertisers have sent you, and test a campaign's pixel.

What you can do here

  • Postback Builder — Type a path or start from a preset (Generic, Trackier-, Affise- or HasOffers-style), click macros to insert them, and copy the full URL on your tracking domain.
  • Publisher Postback Test — Pick a publisher and campaign, choose the event and values, and fire a test conversion to that publisher's postback. The result shows the resolved URL, response body and validation checks.
  • Advertiser Postback — Recent postbacks sent to you by advertisers, filterable by advertiser and campaign.
  • Pixel Tester — Fires a campaign's configured pixel URL and shows the HTTP response.

Fields and settings

FieldWhat it does
Postback path / URLThe URL the advertiser calls when a conversion happens. It must carry the click ID you passed in the offer URL, plus a token. Values: click_id the click ID (required, or coupon= for coupon sales); txid the advertiser's order ID — prevents duplicates; status approved (default), pending or rejected; payout / revenue amounts, when they vary per conversion; token advertiser or platform token (or secret= with the campaign secret). Limits: The presets don't include the token — add &token=… before sharing.

How to use it

  1. Open Postback Builder, pick the preset closest to the advertiser's platform and adjust the parameter names to match theirs.
  2. Add &token= with the advertiser's token and copy the full URL to the advertiser.
  3. Ask the advertiser to fire a test, then check Advertiser Postback for the request and its result.
  4. Use Publisher Postback Test to confirm the publisher receives conversions too.

Examples

Generic S2S postback

What a typical advertiser integration looks like.

  • URL: https://<tracking-domain>/postback?click_id={click_id}&txid={order_id}&revenue={amount}&status=approved&token=ADV_TOKEN

Limitations

  • Restricted: Network admins only — partner accounts get a 404 because these tools list every campaign, advertiser and publisher. Team members need the Publishers permission for the publisher test and pixel tester, and Advertisers for the advertiser postback logs.
  • Depends on: Postbacks without a valid token or campaign secret are rejected with 401.
  • Not supported: Statuses other than approved, pending and rejected aren't recognised: a new conversion sent with any other status is recorded as approved.

Common mistakes

  • Sharing a preset without a token — Every postback fails with 401. Add the advertiser's token.
  • Advertiser leaves {click_id} unreplaced — The postback arrives with a literal macro and fails with Unknown click_id. The advertiser must substitute their own stored value.

Troubleshooting

  • Advertiser says they fired but nothing is logged — They're calling the wrong host or path. Compare their URL with the builder's full URL.
  • 422 “Click was rejected” — The click failed targeting or fraud checks, so it can't convert. Look the click up in Reports → Click Intelligence.