AXAffilinext Help Center

Publisher detail

One publisher's overview, profile, global postbacks, campaigns, API keys, security log, status, password and Login As. For network admins.

Everything about one publisher. Edit their profile and payment terms, configure the postbacks that tell their tracker about conversions, see their campaigns and API keys, change their status, set their password, or sign in as them to see exactly what they see.

What you can do here

  • Overview — Clicks, conversions and payout totals, account details, login status, traffic sources and recent postback activity.
  • Profile & Details — Contact details, reference and tax IDs, account manager, traffic sources, payment terms and internal admin notes (never shown to the publisher).
  • Global Postbacks — The publisher's postback URLs with filtering, payout hiding and signing, plus their delivery logs.
  • Campaigns, API Keys, Security & Logs — Their campaigns and payouts, their API keys, and the audit trail for their account.
  • Change Status — Active, paused, suspended and so on, with a reason shown to the publisher and an internal note.
  • Login As — Opens the platform as this publisher, with a banner to return to your own account.

Fields and settings

FieldWhat it does
Fire forWhich conversions trigger this postback. Values: All conversions every conversion on any offer; Selected events only only conversions whose event/goal name is in the list (e.g. lead, sale); Selected offers only only conversions on the listed campaign IDs.
Payout visibilityHide payout sends 0 in the payout macros, for publishers whose trackers shouldn't see amounts.
HMAC-SHA256 signatureAdds a header the publisher can check to be sure the postback really came from you. X-Postback-Signature: sha256=<hex HMAC-SHA256 of the final URL using the secret token>.
StatusAny status other than active signs the publisher out, blocks their logins and API keys, and refuses their clicks (or follows a Publisher not active fallback rule).

How to use it

  1. Check Overview for performance and whether they have a login.
  2. Set a login password if they need to sign in.
  3. Add or check their Global Postbacks and read the delivery logs if they report missing conversions.
  4. Use Login As to reproduce what they see — you return with the banner at the top.

Limitations

  • Restricted: Login As is for the Super Admin only, and can be switched off in Settings → User & Role.
  • Restricted: Setting passwords needs the Publisher logins permission for team members.
  • Supported: Up to 10 global postbacks per publisher.

Common mistakes

  • Suspending to fix a postback — Suspension stops all their traffic. To stop postbacks, set the postback to inactive instead.
  • Leaving notes in the public reason — Reason is shown to the publisher; put internal context in Internal note.