Google Search Ads 360

Datafly Signal delivers enhanced conversion data to Google Search Ads 360 for search campaign attribution, bidding optimisation, and cross-channel reporting.

Why route Google SA360 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 SA360 optimises against are not filtered by the browser.
Email and phone number are hashed before leaving your infrastructure. Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Google SA360 receives match keys rather than raw personal data.
Click identifiers are captured and replayed. Signal stores clickid, gclid first-party at collection time and attaches them to the conversion later, so attribution survives even when the original landing cookie has expired.
Delivery is batched, rate-limited, and retried. Signal buffers to Kafka, respects the Google SA360 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 SA360 requires, so nothing expires quietly in the middle of a campaign.
One consent decision governs every destination. Google SA360 is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.

Prerequisites

Before configuring SA360 in Signal, you need:

A Search Ads 360 account with API access enabled
A GCP service account with SA360 API permissions
Your Agency ID and Advertiser ID from the SA360 console

Get your SA360 credentials

Sign in to Search Ads 360.
From the account picker, note your Agency ID and Advertiser ID.
In Google Cloud Console, create a service account and generate a JSON key.
Enable the DoubleClick Search API (SA360) for the GCP project.
In SA360, grant the service account access at the advertiser level under Agency settings → Users.

See Google’s SA360 API reference for full details.

Configure the integration in Signal

In the Management UI, go to Integrations → Add Integration.
Select Google SA360 from the catalogue.
Give the integration a name (for your reference).
Fill in the required fields:

Field	Required	Description
`agency_id`	Yes	SA360 agency ID.
`advertiser_id`	Yes	SA360 advertiser ID.
`service_account_json`	Yes	GCP service account JSON key with SA360 API access.

Choose which pipeline(s) this integration should run on.
Select consent categories (defaults to marketing).
Click Save.

API endpoint

POST https://www.googleapis.com/doubleclicksearch/v2/conversion

Allow egress to www.googleapis.com from the network your delivery workers run on.

Event mapping

Signal event	SA360 conversion
`Order Completed`	`purchase`
`Lead Submitted`	`lead`

To map additional events, edit the integration’s Field Mappings.

Identity

Signal sends the following enhanced-conversion signals to SA360, subject to consent and availability:

Capability	Notes
Click ID	`gclid` from the URL
Hashed email	SHA-256 (lowercase, trimmed)
Hashed phone	SHA-256 (E.164)
Client IP / User-Agent	Forwarded from the original request

This integration is gated on the marketing canonical consent category.

Verify it’s working

In the Management UI, open Pipelines → your pipeline → Live Events and trigger a test conversion.
The event appears in the live feed; inspect the payload sent to SA360.
In SA360, check the Conversions report — uploads may take several hours to surface.

Troubleshooting

PERMISSION_DENIED. The service account is missing advertiser-level access in SA360. Add it under Agency settings → Users.

No gclid on conversions. Confirm Datafly.js is capturing gclid from the landing URL and that the user reached the conversion event in the same session/cookie scope.