Integrations / Advertising
Google Floodlight
Fire Google Campaign Manager 360 / DV360 Floodlight counter and sales activities server-to-server via the ad.doubleclick.net activity endpoint. Maps GA4-style Signal events to Floodlight parameters (ord, qty, cost, u-variables) with EEA consent signals (ad_user_data, ad_personalization, npa). One blueprint preset per Floodlight activity (cat/type pair set in integration config).
Datafly Signal delivers first-party events to Google Floodlight server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Google Floodlight expects.
Why route Google Floodlight 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 Google Floodlight 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 Google Floodlight needs to attribute the event to the right session.
One consent decision governs every destination
Google Floodlight 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
pagepurchasesign_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 Google Floodlight documentation.
Frequently asked questions
Does Datafly Signal integrate with Google Floodlight?
Yes. Datafly Signal delivers first-party events to Google Floodlight server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Google Floodlight expects. The integration is included in every deployment at no additional cost.
How is server-side Google Floodlight tracking different from the Google Floodlight tag?
The Google Floodlight 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 Google Floodlight from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Google Floodlight?
The blueprint ships with mappings for page, purchase, sign_up. Any event in your schema can be mapped to Google Floodlight through pipeline configuration without a code change.
Do I need to keep the Google Floodlight 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 Google Floodlight deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Google Floodlight server-side?
See how Datafly Signal delivers first-party events to Google Floodlight from infrastructure you control, with hashed identity and consent enforcement built in.