Media buyer tool 3 · Postback URL Tester for Affise
Test your Affise postback URL before the next conversion goes missing.
Affise calls the affiliate's postback URL (a link used to pass conversion info to an affiliate) with its macros replaced by conversion values. Below: Affise's postback format and macros as Affise's own docs give them, the ways a Affise postback usually breaks, and the tester, pre-filled with an example of the postback the platform fires to your tracker. Edit it to match yours and run the check.
Nothing you enter leaves your browser.
Affise's postback format
Docs show no full URL; the affiliate supplies their own URL and it is updated with Affise macros, e.g. https://tracker.example.com/postback?clickid={sub1}&payout={sum}Affise's click-ID macro: {sub1}. Source: Affiliate Postback URL Macros, Affiliate Postback Macros (Affiliates) (read on November 9, 2026). Networks rename macros and some show them only inside your account; if your dashboard differs, it wins.
Affise macros
| Macro | Meaning |
|---|---|
| {sub1} | Sub account 1 ({sub1}-{sub8}); used to pass the click ID back |
| {sum} | Conversion payout |
| {order_sum} | Conversion price |
| {order_currency} | Conversion currency |
| {status} | 1 approved, 2 pending, 3 declined, 5 approved and on hold |
| {goal} | Goal |
| {offerid} | Offer identifier in the system |
| {transactionid} | Advertiser's conversion identifier |
| {currency} | Currency |
| {geo} | Country |
| {timestamp} | Unix timestamp of conversion creation |
Parameter names on the receiving side
clickid: Name chosen by the affiliate's tracker for the click ID; value filled from {sub1}payout: Payout filled from {sum}status: Conversion status code from {status}goal: Goal name from {goal}
How a Affise postback usually breaks
Looking for a clickid macro
Affise has no clickid macro for affiliate postbacks; the click ID must travel in a sub parameter and come back as {sub1}-{sub8}.
Fix: Put your tracker's click ID macro in sub1 on the Affise tracking link and return {sub1}.
{sum} versus {order_sum} confusion
{sum} is the conversion payout while {order_sum} is the conversion price, so using the wrong one reports the sale value as your earnings.
Fix: Use {sum} for payout and {order_sum} for order value.
Sub slot beyond your plan
{sub9}-{sub30} are available only on certain plans, so using them elsewhere returns blanks.
Fix: Stay within {sub1}-{sub8}.
Status not filtered
{status} returns numeric codes (1 approved, 2 pending, 3 declined, 5 on hold), so a tracker that counts every call counts pending and declined conversions as sales.
Fix: Map status values or only count status 1.
Test your Affise postback
Pre-filled with an example: Affise's macros in an example tracker postback (track.example.com stands for your tracker). Paste your own URL over it; the check runs in this page and fires nothing.
Want me to trace one real campaign?
This tool checks the postback URL and offer link you pasted from what you typed. It can't see your ad accounts, tracker, network or live traffic. If the result shows gaps, I'll look at one real campaign for free: I trace it from ad click to payout and back, and within 48 hours I send you a written report on where money or data leaks silently, the fix for each, and the tests that prove it's fixed.
In the review I fire a test conversion end to end on one real campaign and check it lands once, with the right payout, in your tracker and in your traffic source. You get the fix for every place it doesn't.
Shilpa Goel, [email protected]
This is an engineering checklist, not a security audit, legal, compliance or investment advice.
Not affiliated with or endorsed by Meta, Google, TikTok or any network or tracker named here.