Integrations / Advertising
Flashtalking
Server-to-server Flashtalking Spotlight conversion tracking. Fires the /container Spotlight pixel as an HTTP GET to servedby.flashtalking.com with cachebuster, ftXRef (order ID), ftXValue, ftXCurrency and custom U-variables. Matching is FTrack first-party cookie plus forwarded IP/User-Agent — no hashed PII required.
Datafly Signal delivers first-party events to Flashtalking server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Flashtalking expects.
Why route Flashtalking 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 Flashtalking optimises against are not filtered by the browser.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what Flashtalking needs to attribute the event to the right session.
One consent decision governs every destination
Flashtalking 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_leadpagepurchasesign_upVertical presets
Default. 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 Flashtalking documentation.
Frequently asked questions
Does Datafly Signal integrate with Flashtalking?
Yes. Datafly Signal delivers first-party events to Flashtalking server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Flashtalking expects. The integration is included in every deployment at no additional cost.
How is server-side Flashtalking tracking different from the Flashtalking tag?
The Flashtalking 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 Flashtalking from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Flashtalking?
The blueprint ships with mappings for generate_lead, page, purchase, sign_up. Any event in your schema can be mapped to Flashtalking through pipeline configuration without a code change.
Do I need to keep the Flashtalking 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 Flashtalking deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Flashtalking server-side?
See how Datafly Signal delivers first-party events to Flashtalking from infrastructure you control, with hashed identity and consent enforcement built in.