Integrations / Advertising
TradeTracker
Server-to-server affiliate conversion tracking for TradeTracker. Fires sale conversions to ts.tradetracker.net and lead conversions to tl.tradetracker.net as the backend equivalent of the TradeTracker conversion pixel. Attributes each conversion to the referring publisher via the captured click reference (data), with optional SHA-256 hashed e-mail for cross-device matching.
Datafly Signal delivers first-party events to TradeTracker server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload TradeTracker expects.
Why route TradeTracker through Datafly Signal
Conversions survive ad blockers and tracking prevention
A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari's ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions TradeTracker optimises against are not filtered by the browser.
Email hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so TradeTracker receives match keys rather than raw personal data.
One consent decision governs every destination
TradeTracker is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
generate_leadpagepurchaseVertical presets
Retail. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the TradeTracker documentation.
Frequently asked questions
Does Datafly Signal integrate with TradeTracker?
Yes. Datafly Signal delivers first-party events to TradeTracker server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload TradeTracker expects. The integration is included in every deployment at no additional cost.
How is server-side TradeTracker tracking different from the TradeTracker tag?
The TradeTracker tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to TradeTracker from your server, so delivery does not depend on browser conditions.
What personal data is sent to TradeTracker?
Email are normalised and SHA-256 hashed inside your own deployment before delivery, so TradeTracker receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to TradeTracker?
The blueprint ships with mappings for generate_lead, page, purchase. Any event in your schema can be mapped to TradeTracker through pipeline configuration without a code change.
Do I need to keep the TradeTracker tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so TradeTracker deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move TradeTracker server-side?
See how Datafly Signal delivers first-party events to TradeTracker from infrastructure you control, with hashed identity and consent enforcement built in.