Skip to content

Media buyer tool 3 · Postback URL Tester for Admitad

Test your Admitad postback URL before the next conversion goes missing.

Admitad calls the server address you configure (your tracker's URL) with the selected parameters when an action, program status or cooperation status event happens. Below: Admitad's postback format and macros as Admitad's own docs give them, the ways a Admitad postback usually breaks, and the tester, pre-filled with an example of the postback the network fires to your tracker. Edit it to match yours and run the check.

Nothing you enter leaves your browser.

Admitad's postback format

https://your-server.example/endpoint?offer_id=[[[offer_id]]]&payment_status=[[[payment_status]]]

Admitad lists subid4 as the parameter to carry your click ID. Its article writes variables as [[[name]]] (e.g. [[[reward_ready]]]), so the example uses [[[subid4]]]. Source: Postback URL (Admitad knowledge base) (read on November 9, 2026). Networks rename macros and some show them only inside your account; if your dashboard differs, it wins.

Admitad macros

MacroMeaning
[[[reward_ready]]]The one variable the article prints in full; it shows the [[[name]]] syntax every parameter uses

Parameter names on the receiving side

  • subid4: SubID on the affiliate link that carries your click ID out
  • payment_sum: Earnings amount parameter
  • payment_status: Status: new, approved, declined, pending
  • order_id: Order number parameter

How a Admitad postback usually breaks

  1. Same conversion fires several times

    payment_status takes new, approved, declined and pending, so one order can post multiple times as status changes.

    Fix: Dedupe on order_id and update status instead of counting each call as a new conversion.

  2. Click ID in the wrong SubID

    Admitad says SubID4 can carry click_id or transaction_id; the value comes back only in the SubID you filled on the affiliate link.

    Fix: Put the click ID in subid4 and read [[[subid4]]].

  3. Other event types hit the same URL

    Program status, referral joined (empty request) and cooperation status events can also be sent; an empty-parameter request will fail parsers that expect a click ID.

    Fix: Subscribe only to the Action event type, or ignore calls with no order_id.

Test your Admitad postback

Pre-filled with an example: Admitad's parameters (subid4, payment_sum, payment_status, order_id from its table) in its [[[name]]] syntax, in an example tracker postback. Paste your own URL over it; the check runs in this page and fires nothing.

Not Admitad's own macros: [[[subid4]]] (Admitad (a parameter from its table, written in its [[[name]]] syntax)); [[[payment_sum]]] (Admitad (a parameter from its table, written in its [[[name]]] syntax)); [[[payment_status]]] (Admitad (a parameter from its table, written in its [[[name]]] syntax)); [[[order_id]]] (Admitad (a parameter from its table, written in its [[[name]]] syntax)).

Your network's click-ID macroThe macro the network fills with the click ID you sent it. It also tells the tester which syntax the network uses.

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.

Request the free spend-path review (opens Cal.com in a new tab)

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.