Integration · destination
Affiliate & performance networks
Universal server-to-server postbacks with presets for Awin, CJ, Impact, TradeTracker, Tradedoubler, Partnerize, Rakuten, Webgains, Digistore24, Adcell, Belboon, TUNE and Everflow.
How events reach Affiliate networks
Every path ends in the same place: the policy engine checks the consent purpose this destination requires, strips what may not leave, and the worker delivers with the shared event id.
- Server API — delivered by the worker with retries, health checks, error classification and a redacted payload preview for every attempt.
What is sent
Only what you configure in the event mapping, and only after the policy engine has allowed the event for this destination.
- Event name and timestamp, mapped from Track's standard events to the platform's event names.
- The shared event id in the platform's order_id field, so browser and server deliveries count once.
- Click ids this platform may receive: aff_click_id, aff_sub_id, awc, cjevent, irclickid, tduid, ttl, utm_term. Other vendors' click ids are never forwarded.
- Order id, value, currency and items for purchase-type events.
- SHA-256-hashed identifiers (e-mail, phone, external id) for matching — only with the required consent and only if captured.
- The consent state the event was collected under, where the platform accepts consent signals.
Never sent
- Raw e-mail addresses, phone numbers or names — identifiers are hashed on ingest.
- Inferred values: unknown stays unknown, nothing is guessed.
- Events collected without the purpose this destination requires.
- Secrets: tokens live in the encrypted vault and never reach the browser, the assistant or a log.
Technical facts
- Deduplication field
order_id— transaction id- Click ids
aff_click_id,aff_sub_id,awc,cjevent,irclickid,tduid,ttl,utm_term- Consent purpose
- Marketing
- Pinned API version
postback-v1- Implementation status
- Implemented · verified against the vendor documentation · verified 2026-09-03
- Network presets
- Awin, CJ Affiliate, impact.com, TradeTracker, Tradedoubler, Partnerize, Rakuten Advertising, Webgains, Digistore24, ADCELL, belboon, TUNE (HasOffers), Everflow, Custom postback
- Vendor documentation
- Track documentation
What you need
Public identifiers can be typed in chat or the wizard; secrets go through the secure credential card or OAuth and are stored encrypted.
Public identifiers
- preset
- Network preset
Credentials
- API access token
access_token— stored in the encrypted vault, optional- API secret
api_secret— stored in the encrypted vault, optional- Signing secret (generated by Track)
signing_secret— stored in the encrypted vault, optional- Webhook secret
webhook_secret— stored in the encrypted vault, optional
Consent
Requires the marketing purpose. Without it nothing is loaded in the browser and nothing is sent from the server. Inferred consent is never exported, and Global Privacy Control opt-outs block delivery.
Setup in a few steps
The assistant runs the detailed checks. You see the milestones that need a decision from you.
Enter identifiers
Add the public IDs from the platform. Formats are validated against the vendor's documentation before anything is saved.
Connect credentials
Paste the token into the secure card or connect the account via OAuth. Secrets go straight into the encrypted vault.
Map and test
Standard events are pre-mapped to the platform's event names. A flagged test event runs through the real pipeline and shows the vendor's answer.
Publish
Review the diff, approve, publish a signed configuration version. Roll back with one click if needed.
From Tracking Knowledge
Guides written by the team that builds this connector.
Affiliate server-to-server postbacks: one engine, fourteen networks, and what each one signs
How affiliate S2S postbacks work end to end — capturing the network click id, storing it first-party, firing the postback on the verified purchase, handling reversals — with the specifics of Awin, CJ, Impact, TradeTracker, Tradedoubler, Partnerize, Rakuten, Webgains, Digistore24, Adcell, Belboon, TUNE and Everflow.
Tutorial · 3 min read
Click ids and attribution windows: which parameters to capture, how long to keep them and where to store them
A reference of advertising click ids (gclid, gbraid, wbraid, dclid, msclkid, fbclid, ttclid, li_fat_id, rdt_cid, epik, ScCid, twclid, tblci, ob_click_id, affiliate ids), how consent gates their capture, how attribution windows differ per platform and how first-party storage should expire.
Reference · 3 min read
Questions
Can I run server-only?
Yes. Choose server mode in the wizard; the vendor script is never loaded and matching relies on hashed identifiers and click ids captured by the tracker.
How are duplicates avoided?
The browser tag and the server request carry the same event id, and purchases add the order id. The worker also deduplicates repeated source events before delivery.
What if the vendor API changes?
API versions are pinned centrally with the verification date; sunset warnings appear in the destination health long before an endpoint is retired.
Connect Affiliate networks
Set it up with the guided wizard or let the assistant do it in chat.