Google Search Ads 360

Datafly Signal uploads conversions to Search Ads 360 with the conversion API (DoubleClick Search API v2), attached to the visit by its Google click ID.

Why route Google Search Ads 360 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 conversion from your own server, so the conversions Search Ads 360 optimises against are not filtered by the browser.
Click identifiers are captured and replayed. Signal captures the click ID first-party when the visitor lands and attaches it to later conversions.
One consent decision governs every destination. Search Ads 360 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

Activate the conversion API

In Google Cloud enable the Search Ads 360 API for your project, create a service account and a JSON key, and add the service account as a Search Ads 360 user with the conversion API service activated.

Create Floodlight activities for offline conversions

The vendor event names in the preset are Floodlight activity names (Purchase, Lead, Sign Up, …). Create matching activities, or rename the events in the preset, and set each one’s primary source to offline in Search Ads 360.

Find your agency and advertiser IDs

Both are in the Search Ads 360 UI.

Configure in Signal

Configuration Fields

Field	Required	Description
`agency_id`	Yes	Your Search Ads 360 agency ID, sent as agencyId on every conversion.
`advertiser_id`	Yes	Your Search Ads 360 advertiser ID, sent as advertiserId on every conversion.
`service_account_json`	Yes	Service account JSON key with the doubleclicksearch scope; the service account must be a Search Ads 360 user with the conversion API service activated.

Management UI Setup

Go to Integrations > Add Integration > Google Search Ads 360 Conversions.
Choose a preset: Default (default), Retail (ecommerce), Lead Generation (lead_gen), Insurance (insurance).
Fill in the fields above and click Save.

Request format

POST https://www.googleapis.com/doubleclicksearch/v2/conversion
Authorization: Bearer <service account token>

{"conversion": [{"agencyId": "20100000000000932", "advertiserId": "21700000000011523",
  "clickId": "COiYmPDTv7kCFcP0KgodOzQAAA", "conversionId": "ORD-1001",
  "conversionTimestamp": 1758500000123, "segmentationType": "FLOODLIGHT",
  "segmentationName": "Purchase", "type": "TRANSACTION", "revenueMicros": 259990000,
  "currencyCode": "GBP", "floodlightOrderId": "ORD-1001", "adUserDataConsent": "GRANTED"}]}

Event Mapping

Signal event	Vendor event	Presets
`purchase`	`Purchase`	Default, Retail
`generate_lead`	`Lead`	Default, Lead Generation, Insurance
`sign_up`	`Sign Up`	Default, Lead Generation
`contact_requested`	`Contact Request`	Lead Generation
`quote_completed`	`Quote Completed`	Insurance
`purchase`	`Policy Purchase`	Insurance

Purchases are TRANSACTION conversions with revenue in micros; leads and sign-ups are ACTION conversions.

⚠️

Search Ads 360 may not recognise a click ID until 6 hours after the click, and Signal uploads in real time, so a conversion very soon after the click can be rejected (#1384). Google’s Data Manager API also accepts Search Ads 360 offline conversions.

Identity

Conversions are attributed by the Google click ID (gclid). The API’s terms forbid personal data, so no email, phone or other identifier is sent.

Search Ads 360 is an advertising destination and requires marketing consent by default. adUserDataConsent carries the visitor’s marketing consent.

Troubleshooting

Problem	Solution
`401` or `403`	The service account must be a Search Ads 360 user with the conversion API service activated.
`Click ID is not found`	The upload was within 6 hours of the click (#1384), or the click is older than 90 days.

Blueprint

The Google Search Ads 360 blueprint version is 0.7.0. It was last reviewed against the vendor’s documentation on 2026-09-22.