Google Floodlight
Server-side delivery of conversion events to Google Floodlight activities. Distinct from the CM360 Campaign Manager integration — Floodlight handles direct conversion pixel replacement and offline conversion imports at the activity-tag level.
Status: alpha. Scaffolded entry. Two delivery modes are planned — direct pixel replacement (counter / sales activities) and offline conversion import via the CM360 API. Formalised in a future release.
Prerequisites
- A Campaign Manager 360 account with Floodlight enabled.
- A Floodlight Advertiser ID (
srcparameter). Find it under Advertiser Settings in CM360. - Activity Group tag string (
type) and Activity tag string (cat) for each activity you want to track. - For offline conversion imports only: a Google Cloud project with OAuth2 credentials for the CM360 API.
Configuration fields
| Field | Required | Notes |
|---|---|---|
advertiser_id | Yes | Floodlight advertiser ID (src). |
activity_group | Yes | Activity group tag string (type). |
activity_tag | Yes | Activity tag string (cat). |
oauth_refresh_token | No | Only required for offline conversion imports via CM360 API. |
Delivery mode: pixel replacement
Signal replaces the in-browser Floodlight pixel with a server-to-server call, preserving the standard src/type/cat parameters plus any custom Floodlight variables. No changes needed at the advertiser side — Floodlight sees the same activity structure it would from the client-side pixel.
Delivery mode: offline conversion import
For sales-cycle conversions that happen after the web session (e.g. phone-closed deals, in-store purchases linked back via gclid), Signal can push offline conversions via the CM360 Offline Conversions API. Requires OAuth2 setup with the CM360 API scope.
Why this is distinct from CM360
The CM360 Campaign Manager blueprint handles higher-level click / impression / measurement pipelines. Floodlight is the conversion tag layer underneath. A typical CM360 deployment uses both — campaign data via CM360, conversion data via Floodlight.