Integrations / Advertising
Google Audience Segments
Audience segment syncing for Google Ads.
Datafly Signal delivers first-party events to Google Audience Segments server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Google Audience Segments expects.
Why route Google Audience Segments 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 Audience Segments optimises against are not filtered by the browser.
Email, phone number, first name and last name hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Google Audience Segments receives match keys rather than raw personal data.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Google Audience Segments rate limit, and retries on 429 or transient failure rather than dropping the event.
Token lifecycle is handled for you
Signal obtains and refreshes the OAuth credentials Google Audience Segments requires, so nothing expires quietly in the middle of a campaign.
One consent decision governs every destination
Google Audience Segments 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
identifyVertical presets
General. 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 Audience Segments documentation.
Frequently asked questions
Does Datafly Signal integrate with Google Audience Segments?
Yes. Datafly Signal delivers first-party events to Google Audience Segments server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Google Audience Segments expects. The integration is included in every deployment at no additional cost.
How is server-side Google Audience Segments tracking different from the Google Audience Segments tag?
The Google Audience Segments 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 Audience Segments from your server, so delivery does not depend on browser conditions.
What personal data is sent to Google Audience Segments?
Email, phone number, first name and last name are normalised and SHA-256 hashed inside your own deployment before delivery, so Google Audience Segments receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Google Audience Segments?
The blueprint ships with mappings for identify. Any event in your schema can be mapped to Google Audience Segments through pipeline configuration without a code change.
Do I need to keep the Google Audience Segments 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 Audience Segments deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Google Audience Segments server-side?
See how Datafly Signal delivers first-party events to Google Audience Segments from infrastructure you control, with hashed identity and consent enforcement built in.