Skip to content

Media buyer tool 3 · Postback URL Tester for BeMob

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

The affiliate network calls your BeMob postback URL when a conversion happens, passing back the click ID in cid. Below: BeMob's postback format and macros as BeMob's own docs give them, the ways a BeMob postback usually breaks, and the tester, pre-filled with an example of the postback URL your affiliate network calls in. Edit it to match yours and run the check.

Nothing you enter leaves your browser.

BeMob's postback format

http://xxxxx.yourdomain.com/postback?cid={click_id}&payout={payout}&txid={transaction_id}&status={status}

Set by your network, not by BeMob: put your network's click-ID macro in the cid= field. Source: Postback Settings of Affiliate Network (read on November 9, 2026). Networks rename macros and some show them only inside your account; if your dashboard differs, it wins.

BeMob macros

MacroMeaning
{clickId}BeMob token added to the offer URL when the network has no dedicated click ID field

Parameter names on the receiving side

  • cid: Required (only obligatory parameter). Click ID passed back to BeMob
  • payout: Revenue of the conversion
  • txid: Unique transaction ID per conversion, e.g. order number
  • status: Conversion status: accepted, rejected or pending

How a BeMob postback usually breaks

  1. REPLACE / OPTIONAL values not swapped

    All REPLACE and OPTIONAL values in the template must be replaced with the network's tokens. Leaving them sends literal text and the click is not found.

    Fix: Substitute each value with the network's token or remove the parameter.

  2. No click ID field on the network

    If the affiliate network provides no placeholder or dedicated field for {clickId}, add the click ID parameter and token on the BeMob side, in the offer URL.

    Fix: Append a parameter with the BeMob click ID token to the offer URL.

  3. cid is the only required parameter

    cid is the only obligatory parameter; a wrong cid token means nothing is recorded even if payout and status are correct.

    Fix: Verify the network's click ID macro first.

  4. Status not passed

    status is needed to pass accepted, rejected or pending per conversion; without it every conversion looks the same.

    Fix: Map the network's status token to status if you want rejected/pending tracked.

Test your BeMob postback

Pre-filled with an example: BeMob's postback with the example network macros its help page prints. Swap in your own network's macros. Paste your own URL over it; the check runs in this page and fires nothing.

Not BeMob's own macros: {click_id} (an example network (BeMob's docs)); {payout} (an example network (BeMob's docs)); {transaction_id} (an example network (BeMob's docs)); {status} (an example network (BeMob's docs)).

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.

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.