TOOLS · 23 September 2026 · 7 min read

Postbacks to Keitaro, Binom and Other Trackers: Setup and Testing

A practical setup guide for sending Bynix events into Keitaro, Binom and similar trackers, with testing steps to catch broken attribution.

Postbacks to Keitaro, Binom and Other Trackers: Setup and Testing

If you buy traffic or run content at scale, postbacks are what turn guesswork into usable data. They let your tracker record what happened after the click, so you can compare creatives, placements and audiences on something more reliable than registrations alone.

For Bynix partners, the setup is straightforward once you understand the event names and macros. The key is to pass the right click ID, map each event properly, and test before you scale. This guide covers Keitaro, Binom and similar trackers, plus the mistakes that usually break attribution.

Postbacks to Keitaro, Binom and Other Trackers: Setup and Testing
Postbacks to Keitaro, Binom and Other Trackers: Setup and Testing

Why postbacks matter

A tracker can only optimise what it receives. If your campaigns send clicks to Bynix but no conversion events come back, you are effectively flying blind. With postbacks enabled in Dashboard, you can match traffic to registrations, first-time deposits and commission-related updates in real time.

For most affiliates, that helps with three practical jobs:

  • Checking which source or angle produces registrations and FTDs.
  • Splitting results by sub-ID so you can compare ad sets, creators or placements.
  • Spotting issues early if clicks are coming through but no events are being recorded.

Bynix supports postbacks in Links › Postbacks and uses these macros:

  • {click_id}
  • {sub}
  • {amount}
  • {event}

The basic setup flow

At a high level, every tracker setup follows the same pattern:

  1. Create or choose your partner link in Dashboard.
  2. Add a unique click ID parameter from your tracker when sending traffic.
  3. Use the campaign field as your sub-ID if you want source-level grouping.
  4. Add your tracker postback URL in Links › Postbacks.
  5. Map the returned values in your tracker so each event is recorded correctly.
  6. Run a test registration and check the postback log before spending more.

The most important value is the click ID. Your tracker generates it on the outbound click, Bynix receives it through your link, and then sends it back via postback so the tracker knows which visit converted.

The {sub} macro is useful for your own naming structure. If you use sub-IDs carefully, you can separate campaigns by geo, angle, creator or placement without creating unnecessary link clutter.

How to map events in trackers

Different trackers label conversions differently, but the logic is the same: one incoming postback URL can carry an event type, and your tracker decides what to do with it.

A simple mapping approach is:

  • Registration event goes to a lead or signup conversion.
  • FTD event goes to a first deposit conversion.
  • Amount-related values can be stored where your tracker accepts revenue or payout fields.
  • Event names should be handled exactly as your tracker expects, with no guessing.

For Bynix, the macro set gives you:

  • {event} for the action name.
  • {amount} for the value sent with the event.
  • {click_id} to match the original click.
  • {sub} for your campaign label.

In Keitaro, Binom and most other trackers, you will usually:

  • Paste the postback URL into the tracker offer or traffic source flow, depending on how you structure campaigns.
  • Set the tracker to accept the click ID parameter you are passing.
  • Create rules so event names are categorised correctly.
  • Confirm whether your tracker expects revenue in a separate field or as part of the conversion event.

If you are unsure, keep the first version simple. Start by tracking registrations and FTDs cleanly. You can refine reporting once the basics are working.

Building a clean test

Do not skip testing. A setup that looks correct can still fail because of one wrong parameter name or a pasted URL with missing tokens.

A sensible test process is:

  1. Generate a tracking link with the correct click ID token from your tracker.
  2. Open the link yourself and complete a real registration.
  3. Wait for the registration event to appear in your tracker.
  4. Check the postback area in Dashboard to confirm the call was sent.
  5. If you are validating deposit events, use a compliant real-money flow and check for the FTD event after it is processed.

A few points matter here:

  • Use a fresh test click so the click ID is unique.
  • Make sure the click reaches Bynix through your actual partner link.
  • Do not rely on cached redirects or old links from chat history.
  • If you use sub-IDs, confirm the expected {sub} value is also being passed.

Because Bynix stats show clicks, registrations, FTDs, deposits, volume and commission in real time, you can compare what the dashboard reports against what your tracker records.

Common mistakes that break postbacks

Most failed setups come down to small operational errors rather than anything complicated.

Watch for these:

  • The tracker click ID is not being appended to the outbound link at all.
  • The wrong parameter name is used, so the tracker cannot match the returning conversion.
  • The postback URL was pasted into the wrong place in the tracker.
  • Event mapping treats all events as one generic conversion.
  • Revenue fields are expected by the tracker but {amount} was not mapped.
  • You tested with an old click that does not exist in the active campaign.
  • You changed links mid-test and the click ID no longer matches.
  • Your campaign naming in sub-ID is inconsistent, so reporting looks duplicated or fragmented.

Also remember the programme rules. Do not use spam, cookie stuffing, incentivised sign-ups, brand bidding on Bynix, or any creative that promises guaranteed profits. US traffic is not accepted, and you must not target minors or restricted countries.

Reading the postback log

When something does not appear in the tracker, the postback log is the first place to look. It tells you whether Bynix attempted the call and gives you a practical starting point for diagnosis.

Check the log for:

  • Whether the postback fired at all.
  • Which event was sent.
  • The click ID included in the request.
  • The value passed in {amount}.
  • Any obvious formatting issue in the destination URL.

If the dashboard shows the event but your tracker does not, the problem is usually on the tracker side: field mapping, event rules, or click ID matching. If the dashboard does not show the event either, review the test path from the original link click onwards.

A note on scale

Once postbacks are working, resist the temptation to overcomplicate the setup. Good naming conventions and a reliable click ID flow usually matter more than building dozens of micro-events. Start with data you will actually use to pause, raise or rewrite campaigns.

Use postbacks with better partner data

Postbacks work best when paired with the rest of the partner tools. In Dashboard, you can create unlimited links, organise traffic by campaign field, and monitor clicks, registrations, FTDs, deposits, volume and commission per day, per link and per trader.

If you are building educational funnels or creator-led traffic, the Academy is also useful for checking platform features, trading terms and content accuracy before publishing.

Next step

Open Dashboard and set up your postback in Links › Postbacks, then run one clean test before you scale.

Risk warning: trading involves significant risk; partners must never promise profits.

More guides