Home / Blog / Keitaro setup and Binom v2: pass conversion data correctly

Keitaro setup and Binom v2: pass conversion data correctly

, 4 min read

Keitaro and Binom can connect referred clicks to conversion data, but they use different parameters and processing rules. Start with the product event and a controlled test journey. The setup is complete when the correct action, status and amount appear in the intended report, including retries and corrections.

Keitaro setup and Binom v2: pass conversion data correctly
Yan Krukau / Pexels

Prepare the event and the two systems

Confirm the installed tracker version and read the corresponding documentation; the Binom details below refer to v2. You need a configured tracker, an offer or product endpoint that preserves the referral identifier, and a supported way to report the action. An actively spending ad campaign is not required for a controlled integration test.

Define the qualifying event, its authoritative product record and the expected financial value. Agree the identifier, currency, statuses, updates and privacy requirements. A registration should not silently become a confirmed sale because that status is convenient for a dashboard.

Pass the tracker click ID out and return the same value

In the offer URL, put the tracker's click token into a parameter that the receiving network supports. Keitaro uses {subid}; Binom uses {clickid}. The receiving parameter might be named differently, so confirm it in the network's documentation rather than copying another offer's link.

Copy the incoming postback URL from your own tracker. Current Keitaro documentation places it in Settings > Postback URL; Binom v2 uses Settings > Tracking links. In the network's callback configuration, replace the relevant placeholder with the network's macro that returns the stored click value. The returned value, not the macro's spelling, must match the original tracker click.

Keitaro receives that identifier as subid, while Binom v2 receives it as cnv_id. A network transaction ID is not interchangeable with either click ID. Keep the generated endpoint and security components intact, and do not put secret-bearing callback URLs into a public landing page.

Map statuses, amounts and repeated actions

Current Keitaro documentation requires a supported status or an explicit mapping for a nonstandard status. It also uses tid to distinguish additional transactions associated with the same click. Decide when a later message should update the existing conversion and when it represents another purchase.

Binom v2 accepts conversion information through cnv_status and cnv_status2 and provides status schemes and status-based payout settings. A custom PHP converter is not inherently required. Check the installed configuration: the same incoming status can have different financial consequences under different rules.

For Binom offers, Auto uses the payout supplied in the postback. Upsell adds incoming payouts instead of replacing the previous amount, so it must not be enabled without testing retries and corrections. In either tool, specify whether the amount is commission or customer revenue, and use the documented currency parameter. Do not treat a pending payout as confirmed revenue.

Test the complete transaction and the failure cases

Create a valid referral through the configured campaign or approved test route. Confirm the identifier at the tracker and recipient, then complete a permitted test action. Reconcile the incoming request, processing log and final conversion record with the product's source record. A made-up test123 identifier cannot prove that an existing click is attributed correctly.

Repeat the same event and verify that its business effect is not duplicated. Then test another legitimate transaction from that click, a status update, a rejection or refund, an unknown identifier and an invalid status. Confirm the amount, currency and reporting period after each step.

If the request succeeds at the HTTP layer but no conversion appears, inspect processing messages, identifier matching, status mapping, permissions and report filters. Do not assume every mismatch is a click-ID problem. Delayed conversion reporting and an HTTP request timeout are different issues; there is no general 30-second conversion expiry to fix with a guessed setting.

Treat delivery to ad platforms as a separate integration

Receiving a conversion in the tracker does not automatically send a usable event to Meta, TikTok or Google Ads. Configure the supported connector or API separately, with its required identifiers, permissions, event definitions and deduplication rules. Verify the receiving platform's diagnostics as well as the tracker log.

The S2S postback guide explains why server-side delivery does not bypass privacy requirements or guarantee complete attribution. A correct callback also does not establish profitability: acquisition cost, customer contribution and retained use still come from the relevant product and financial records.

Keep a record of the mappings, test cases and the person responsible for failures after launch. Repeat the affected checks when a network, tracker version or event definition changes.

FAQ

Do Keitaro and Binom use the same callback parameters?

No. For the click identifier, Keitaro uses subid while Binom v2 uses cnv_id. The network's returned macro must contain the correct stored value for the chosen tracker.

Does every Binom status mapping need custom code?

No. Binom v2 documents status schemes and status-based payout handling. Check whether those features cover the required logic before adding another component.

Can I test by sending a random click ID?

That can test rejection behavior, not successful attribution. A positive test needs a valid known click and an approved way to create the corresponding test action.

How long does setup take?

It depends on the existing integration, access, event complexity and failure handling. Define the testable scope before estimating; a copied URL alone is not the full implementation.

Sources

Discuss your product's next step

I help define product priorities, plan launches and investigate where users drop out.

Ioann Putevoy
Ioann Putevoy
Product Manager working on mobile apps, launches and growth. Explore my work and experience.

Bring me a product that needs to find its market