Instead of manually matching affiliate conversions to ad clicks, connect EZmob to Binom so the EZmob click identifier travels into your self-hosted tracker, your offer reports conversions back into Binom, and Binom sends attributed results to EZmob. Test every hop before using any conversion report to change bids or exclude inventory.
- Binom runs on your own server, so its postback URL must be publicly reachable — a local install breaks the callback.
- Map EZmob’s click identifier into Binom first; pass Binom’s {subid} to the offer, never the reverse.
- Test the full path: paid click, tracked visit, offer event, source callback — each hop separately.
- A successful postback response proves transport, not attribution. Inspect the identifier inside the request.
Why this matters
A conversion can land in your affiliate dashboard without ever being attributed to the click that produced it. When that happens you are buying traffic against incomplete reporting, and every optimization decision inherits the error.
EZmob is best for affiliate media buyers who want self-serve access to pop, push, display, and native traffic. Its role is traffic acquisition; Binom's role is click tracking and conversion attribution on infrastructure you control. Start with EZmob for the advertising platform, then wire the tracking path before launch.
The one structural difference from hosted trackers: Binom is self-hosted. You install it on your own server, which gives you full data control and no per-click fees, and it also makes you responsible for uptime, HTTPS and reachability — the usual failure points in an EZmob-to-Binom postback chain in 2026.
Before you start
- An EZmob advertiser account with at least one campaign ready to serve.
- Binom installed and running on your own server, on a domain with a valid HTTPS certificate.
- A test offer or affiliate network that can fire a postback to a URL you control.
The gotcha that bites mid-setup: a Binom install that only responds on a private address will silently receive nothing. EZmob's servers must be able to reach your postback endpoint from the public internet, so verify the certificate and external reachability before you touch any macro.
What each system does
| Component | Best for | Useful capability | Limitation to account for |
|---|---|---|---|
| EZmob | Buying self-serve traffic | Runs advertiser campaigns across pop, push, display and native | Campaigns pass creative moderation first; tracking setup does not bypass it |
| Binom | Self-hosted click tracking | Records tracker click IDs and processes postbacks you configure | Attribution depends on correct mapping and a publicly reachable endpoint |
| Affiliate network or offer | Reporting the conversion | Fires the event with the tracker identifier attached | Event definitions and reporting timing belong to the offer side |
Treat these as connected systems, not interchangeable reports. No tracker can recover an identifier that never reached the offer.
Step 1: Map the EZmob click identifier into Binom
In your Binom traffic-source settings for EZmob, set the external identifier macro (the {external_id} field in Binom's EZmob template) and add the matching EZmob click macro to the campaign's offer URL so every click carries its own identifier into the tracker.
Do not substitute a campaign ID or creative ID for a click identifier. Those values describe groups of traffic; only the per-click identifier can receive conversion credit.
Expected result: a click served by the live campaign creates a Binom click record that contains both Binom's click ID and the EZmob click identifier stored against it.
Inspect a real campaign click, not a URL pasted into a browser. Macros expand when the ad is served; pasting the macro text proves nothing about expansion.
Step 2: Pass Binom's subid to the offer
Append Binom's {subid} macro to the offer URL as the sub-ID parameter your affiliate network reads. Binom must receive its own identifier back to locate the visit; the stored EZmob identifier is used later for source attribution.
Expected result: the offer URL your visitor lands on contains a live Binom subid, and that same value travels with the conversion when the offer reports it.
Follow the redirect path if you use pre-landers: an intermediate page that strips the query parameter breaks the chain at the exact hop nobody watches.
Step 3: Configure the offer postback into Binom
In your affiliate network, set the postback (S2S) URL to your Binom conversion endpoint, with the network's sub-ID placeholder mapped to the Binom subid you passed in Step 2. Add the payout parameter if you want revenue in reports.
Expected result: a test conversion from the offer attaches to the correct Binom click and shows the intended status. Confirm separately how revenue values and currencies are interpreted.
A test that reaches the endpoint but returns an unknown identifier is a transport test, not an attribution test. Keep working until the conversion attaches to the intended click.
Step 4: Send results back to EZmob and test end to end
In Binom's EZmob traffic-source settings, configure the postback that calls EZmob's conversion notification endpoint, using the stored external click identifier as the click reference. Choose the event condition that matches what you are buying — an initial lead or an approved conversion.
The event path is paid click, tracked visit, offer event, source callback. Check each transition independently so a missing conversion tells you which system to investigate.
| Workflow | Best for | Advantage | Trade-off |
|---|---|---|---|
| Initial-event postback | Diagnosing funnel activity | Shows the first reported event fast | Does not prove the event was approved |
| Approved-event postback | Optimizing on accepted conversions | Aligns the signal with what pays | Arrives only after upstream approval |
When both events exist, keep both for analysis but do not count both as independent acquisitions.
Troubleshooting
The EZmob identifier arrives as literal macro text
The click ID macro did not expand. Compare the macro against EZmob's current documentation and inspect a click served by the live campaign. Also confirm the campaign uses the traffic-source configuration you edited.
The offer reports a conversion, but Binom cannot attribute it
The identifier sent to the offer and the one returned in its callback must refer to the same Binom visit. A stripped query parameter or the wrong affiliate sub-ID field breaks this connection — follow the redirect path through any pre-lander.
Binom records the conversion, but EZmob does not
Once attribution works, the remaining checks are the outgoing postback and source-side acceptance: confirm the outgoing call carries the original EZmob click identifier, the endpoint and event condition are correct, and check the response EZmob's endpoint returns. This is not an incoming-postback failure.
Conversions appear duplicated
Look for both a browser event and a server postback reporting the same action, plus retries and separate lead/approval events. Pick one documented deduplication method and do not assume identical retries are harmless.
The postback never reaches Binom
Self-hosted means self-operated: check server availability, HTTPS validity, firewall rules and bot protection. A server-to-server sender cannot complete an interactive challenge. Separate an unreachable endpoint from a reachable one receiving invalid parameters using request logs.
Customize your workflow
Once attribution works, add placement and creative identifiers so reports answer buying questions, and segment by GEO and format instead of reading campaign totals. Changing a bid, destination or tracking template should trigger another end-to-end check — especially when the edit touches URL parameters.
Optimize against the event you actually want to buy. Conversion tracking identifies reported outcomes; it does not by itself prove traffic quality or remove ad fraud.
FAQ
How do I connect EZmob to Binom for postback tracking?
Map EZmob’s click identifier into Binom, pass Binom’s {subid} to the offer, configure the offer’s postback into Binom, and set Binom’s outgoing postback to EZmob. Test each hop in order before trusting conversion reports.
Does Binom need a publicly reachable URL to work with EZmob?
Yes. Binom is self-hosted, so EZmob’s servers must reach your postback endpoint from the public internet over valid HTTPS. A private or localhost install silently receives nothing.
What is the difference between {subid} and the external ID in Binom?
{subid} is Binom’s own click identifier and goes to the offer; the external ID stores the EZmob click identifier and is used when Binom notifies EZmob of a conversion.
Can I test the postback without a real conversion?
Use your affiliate network’s supported test-conversion procedure when it provides one. The test must return a valid identifier from a tracked visit — an arbitrary identifier does not verify attribution.
Why does Binom show a conversion that EZmob does not?
The incoming postback can work while the outgoing one fails. Check the stored external identifier, the outgoing event condition and the response EZmob’s endpoint returns.
Should I send leads or approved conversions to EZmob?
Send the event that matches your optimization objective. If you buy approved conversions, keep preliminary leads as diagnostics instead of counting both.
One last thing
A 200 response from the postback is not proof of correct attribution. Before scaling a 2026 campaign, open the request and inspect the identifier inside it and the conversion credited to it. Transport, attribution and event selection are three separate checks; passing only the first leaves your optimization signal unverified.
Related guides
- How to connect EZmob to Keitaro for real-time postback tracking
- How to connect EZmob to RedTrack for real-time campaign tracking
- How to connect EZmob to AdsBridge for postback conversion tracking
- How to connect EZmob to Voluum for automated conversion tracking
Ready to put the tracking path to work? Start advertising on EZmob and test your first campaign from a $100 budget.