Integrations
Every platform with browser tag, server API and shared deduplication
Advertising platforms, analytics, affiliate networks, your own systems and three shop platforms — each implemented, documented and tested against the vendor contract. No “coming soon”.
- 22 destination types
- 14 affiliate postback presets
- 3 shop platforms
Three delivery modes, one event
Which modes a platform supports is decided by its API, not by a plan. The catalogue below shows exactly what each connector implements.
Browser
The Track snippet loads the vendor tag only after consent for its purpose. No vendor code lives in your template.
Server
The worker delivers the same event through the vendor's API — with retries, health checks and a redacted payload preview per attempt.
Offline
Server events flagged as offline (CRM deals, store purchases) reach platforms whose API accepts non-web action sources.
Hybrid by default
When a platform supports both paths, browser tag and server request carry the same event id and purchases add the order id. The vendor deduplicates, and Track's own guard drops repeated source events before delivery.
Connect your first platform
The assistant walks through identifiers, credentials, mapping and a verified test event.