Build the callback. Understand the attribution.
A postback is a server-to-server callback sent after a conversion. Use this lab to assemble a GET callback, generate a terminal-safe test command, and verify the fields that make a conversion attributable.
Map the callback fields
Paste the recipient URL from your tracker or CRM. Then use the macro names your affiliate network actually returns.
Use sub fields only when you have a documented reporting or reconciliation need.
Ready callback URL
Terminal test command
This command substitutes safe sample values. Run it only against an endpoint you control, then confirm the event appears once in the receiving system.
curl --fail-with-body --get 'https://…'The same ID must survive the full path.
The tracker cannot infer an offer-side conversion from a browser redirect. The network or CRM must return the identifier it received at click time.
- 01
Click
A tracker creates a click ID and adds it to the outbound offer URL.
- 02
Offer
The affiliate network stores that identifier beside the user or lead.
- 03
Conversion
After a registration or deposit, the network calls your S2S URL with that same ID.
- 04
Attribution
The recipient processes the callback. Confirm in its reporting log that the click, status, and value were actually matched and recorded.
Field map
For DarkCore ingress, use canonical names below. The recipient endpoint itself must come from the stream configuration, not from a guessed URL.
| Field | Why it matters |
|---|---|
click_id | Matches the callback to the original visit. It is the non-negotiable field. |
status | Tells the receiving system which conversion occurred. DarkCore accepts registration or deposit, plus documented aliases. |
payout | Stores the monetary value when the source sends one. Confirm currency and payout semantics with the partner. |
sub1-sub10 | Carries optional context only when you need it for reports or reconciliation. |
Test the failure points, not just the happy path.
- 1
Identifier
Confirm the exact click ID is present in the offer URL and comes back unchanged.
- 2
Status
Send one test event for every status you will use. Do not map a sale to a lead by assumption.
- 3
Response
A 200 response only says the endpoint accepted the callback. Confirm the matched record in reporting before you trust attribution.
- 4
Deduplication
Repeat the same callback once. The receiver should not count the same conversion twice.
- 5
Timing
Check delayed callbacks against the timezone and attribution window used in reporting.
Map one live callback before it costs attribution.
Bring one offer URL, click parameter, postback template, and the status map. We will help you verify the flow against the actual campaign, not a demo string.