If conversions don’t reach your ad network, you optimize on clicks, and in Black Friday week that means paying peak prices for traffic you can’t judge. Postback (server-to-server) tracking fixes that: your tracker or server tells EZmob each time a click converts, so conversions and conversion value show next to spend in your reports. Here’s a checklist to get it working before November 27.
- Copy your postback URL from Postbacks → Conversion Tracking, or load your tracker’s preset.
- Pass the click ID with the
{conversion}macro and the source with{subid}. - Fire the postback once per confirmed conversion, with the payout as a plain number.
- Run a test conversion and see it in Metrics before you scale.
Why postback beats pixel for pop and push
A pixel fires in the visitor’s browser, so ad blockers, browser privacy settings and closed tabs can lose conversions. A postback is sent from your server or tracker, so it doesn’t depend on the browser at all. If you can call a URL from your server, use the postback. If you can’t, the EZmob pixel is the fallback.
The checklist
1. Copy your postback URL
In the dashboard sidebar, click Postbacks to open Conversion Tracking, then copy Your Postback URL. It looks like this:
https://xml.qualiclicks.com/conversion?c={click_id}&value={value}
2. Use your tracker’s preset if there is one
Under Tracking Partners, click your tracker to load its pre-configured postback URL. We have step-by-step guides for Binom, Keitaro and Voluum.
3. Pass the click ID in your destination URL
Add the {conversion} macro to your campaign’s destination URL, for example:
https://yoursite.com/offer?clickid={conversion}
{conversion} is the only macro that carries the click ID. {click_id} is not a valid destination URL macro and is rejected when you save the campaign.
4. Pass the source too
Add {subid} to the same URL so your tracker can split results by traffic source. You’ll need it to block and whitelist SubIDs later. All macros are listed in Tracking Tokens and Parameters Explained.
5. Paste the postback into your tracker or server
Replace {click_id} with the click ID you received from {conversion}, and {value} with the conversion value (for example, your payout).
6. Fire it once per confirmed conversion
Send the postback only after the conversion is confirmed, and only once. Duplicate or premature postbacks inflate your numbers and send your optimization the wrong way.
7. Run a test conversion
Click through your own campaign, complete the conversion, and check the Conversions and Conv. Value columns under Metrics. Don’t scale a campaign until a test conversion shows up.
Common mistakes
- Using
{click_id}in the destination URL instead of{conversion}. - Firing on every page load of the thank-you page instead of once per conversion.
- Sending the payout in the wrong format. Send a plain number, such as
1.50. - Forgetting the source macro, so you can’t tell which SubIDs convert.
- Testing on Black Friday. Fix tracking in the quiet week, when a broken day costs little.
If conversions still don’t show, work through Troubleshooting Conversion Tracking Issues.
What to do with the data
Once conversions flow, use the Source report to compare SubIDs on cost per conversion, raise bid adjustments where you convert and block where you don’t. The Optimization Guide for Advertisers covers the next steps, and our post on why SubIDs matter in pop campaigns explains the logic.
Top up for Black Friday
Active EZmob advertisers get +10% on a top-up of $300 or more with code EZMORE26 (up to $200). If you haven’t spent in 60+ days, EZBACK26 gives +15% (up to $250). Both run until December 7. See the offers · Terms.
Start advertising on EZmob
Start advertising on EZmob with postback tracking built in.
