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.
This blueprint is currently in beta.
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.
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 |
Consent
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.