Other trackers
Connect Binom, Voluum, or any s2s-compatible tracker — receiver URL and macro mappings.
darkcore does not have separate integrations “for a specific tracker.” It receives conversions through a standard s2s postback, so you can connect any tracker that can send server-side postbacks. The logic is the same as for Keitaro; only macro names on the tracker side change.
General procedure
Pass darkcore's {click_id} into the target URL leading to the tracker, in its external/click parameter.
Configure the tracker postback to darkcore's receiver https://edge.darkcorepwa.com/p, inserting tracker macros into click_id, status, payout, and transaction_id.
Map tracker statuses to conversion types through aliases.
The receiver https://edge.darkcorepwa.com/p is shared across all workspaces. The same URL appears in the stream editor's Postback section.
Macro mappings
What to put into each darkcore parameter on the tracker side:
| darkcore | Keitaro | Binom | Voluum |
|---|---|---|---|
click_id | {external_id} | {clickid} | {externalid} / {clickid} |
status | {status} | — (one URL per status) | — (one URL per status) |
payout | {payout} | {payout} | {payout} |
transaction_id | {tid} | {transaction_id} | {txid} |
Binom and Voluum usually use a separate postback URL for each status, so instead of status={status}, use a fixed value — for example, status=deposit in the URL the tracker sends on sale.
Binom example:
https://edge.darkcorepwa.com/p?click_id={clickid}&status=deposit&payout={payout}Voluum example:
https://edge.darkcorepwa.com/p?click_id={externalid}&status=registrationSee Postback parameters for the full list of accepted parameters and aliases.
Keitaro integration: create a Traffic Source for darkcore
Create a darkcore source in Keitaro, pass click_id in the Campaign URL, and return the conversion for the matching click_id.
Postback parameters
Complete reference for incoming-postback parameters — aliases, validation, response codes, and deduplication.