Media buyer tool 3 · Postback URL Tester for EZmob
Test your EZmob postback URL before the next conversion goes missing.
The advertiser's tracker calls EZmob's conversion endpoint when a conversion happens, passing back the EZmob click ID. Below: EZmob's postback format and macros as EZmob's own docs give them, the ways a EZmob postback usually breaks, and the tester, pre-filled with an example of the postback your tracker fires back to the traffic source. Edit it to match yours and run the check.
Nothing you enter leaves your browser.
EZmob's postback format
https://xml.qualiclicks.com/conversion?c={click_id}&value={value}EZmob's click-ID macro: {conversion}. Source: Setting up conversion tracking / How do I track conversions, Tracking tokens and parameters explained, Third-party tracking platform integration (read on November 9, 2026). Networks rename macros and some show them only inside your account; if your dashboard differs, it wins.
EZmob macros
| Macro | Meaning |
|---|---|
| {conversion} | EZmob click ID (the only macro that carries the click ID) |
| {campaign} | Campaign ID |
| {offer} | Offer ID |
| {banner} | Ad ID |
| {bid} | Click cost (CPC, XML) or cost per view (CPV, Display) |
| {subid} | Publisher feed subID |
| {original_subid} | Unrestricted subID |
| {publisher} | Publisher ID |
| {country} | Two-letter country code |
| {timestamp} | Unix timestamp |
Parameter names on the receiving side
c: EZmob click ID, the value received via {conversion}value: Conversion value, e.g. the payout
How a EZmob postback usually breaks
Using {click_id} in the destination URL
EZmob says {click_id} is not a valid destination URL macro and is rejected when you save the campaign; only {conversion} carries the click ID outward.
Fix: Put {conversion} in the tracking link and keep {click_id} for the postback template only.
Tracker tokens not on EZmob's list
EZmob states tracker tokens not on its macro list are rejected when you save a link.
Fix: Use only macros from EZmob's tokens article in the campaign link.
Leaving {click_id}/{value} placeholders unreplaced
The postback template's c={click_id}&value={value} must be filled with the tracker's own click ID and payout tokens; literal braces mean no click matches.
Fix: Swap both for your tracker's click ID and payout tokens before saving.
Wrong click ID parameter in the link
The link must pass {conversion} into the parameter your tracker uses for its external ID (EZmob's example: clickid={conversion}); a different parameter means the tracker never stores the EZmob ID.
Fix: Map {conversion} to the tracker's external ID parameter.
Test your EZmob postback
Pre-filled with an example: EZmob's documented postback with example tracker tokens in place of {click_id} and {value}. Confirm the postback domain in your EZmob dashboard. Paste your own URL over it; the check runs in this page and fires nothing.
Not EZmob's own macros: {clickid} (your tracker (example token)); {payout} (your tracker (example token)).
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.