Google Data Manager API
The Google Data Manager API destination package provides server-side integration for sending conversion events and audience data to Google's advertising ecosystem through a single unified API endpoint.
Google Data Manager API is a server destination in the walkerOS flow:
Sends conversion events server-side to Google Ads, Display & Video 360, and GA4 through a single unified API.
Installation
Configuration
This destination uses the standard destination config wrapper (consent, data, env, id, ...). For the shared fields see destination configuration. Package-specific fields live under config.settings and are listed below.
Settings
| Property | Type | Description | More |
|---|---|---|---|
credentials | credentials | Service account credentials (client_email + private_key). Recommended for serverless environments. | |
client_email | string | Service account email | |
private_key | string | Service account private key (PEM format) | |
keyFilename | string | Path to service account JSON file. For local development or environments with filesystem access. | |
scopes | Array<string> | OAuth scopes for Data Manager API. Defaults to datamanager scope. | |
destinations | Array<object> | Array of destination accounts and conversion actions/user lists (max 10) | |
eventSource | Event source for all events. Defaults to WEB. Values: WEB, APP, IN_STORE, PHONE, OTHER | ||
batchSize | integer | Maximum number of events to batch before sending (max 2000, like 100) | |
batchInterval | integer | Time in milliseconds to wait before auto-flushing batch | |
validateOnly | boolean | If true, validate request without ingestion (testing mode) | |
url | string | Override API endpoint for testing | |
consent | consent | Request-level consent for all events | |
adUserData | Consent for data collection and use | ||
adPersonalization | Consent for ad personalization | ||
testEventCode | string | Test event code for debugging | |
logLevel | Log level for debugging (debug shows all API calls) | ||
userData | Record<string, any> | Guided helper: User data mapping for all events | |
userId | any | Guided helper: First-party user ID for all events | |
clientId | any | Guided helper: GA4 client ID for all events | |
appInstanceId | any | Guided helper: GA4 app instance ID (Firebase) for all events | |
sessionAttributes | any | Guided helper: Privacy-safe attribution for all events | |
consentAdUserData | string | boolean | Consent mapping: Field name from event.consent (like 'marketing') or static boolean value | |
consentAdPersonalization | string | boolean | Consent mapping: Field name from event.consent (like 'targeting') or static boolean value |
Mapping
This package does not define custom rule-level settings. For the standard rule fields (consent, condition, data, batch, name, policy) see mapping.
Examples
Page view
A page view is sent to Data Manager as a page_view event tied to the walker user id.
Lead
A demo request form submission is sent to Data Manager as a generate_lead conversion with a hashed email.
Purchase
A completed order is posted to Google Data Manager as a purchase conversion with hashed user identifiers.
Guided mapping helpers
Define common fields once in Settings instead of repeating them in every event mapping:
Consent mapping: Map your consent field names (string) or use static values (boolean). Event mappings always override Settings helpers.
Store sales (IN_STORE)
For physical store conversions, set eventSource: 'IN_STORE' on the destination
and map a storeId in the event mapping. The destination wraps it into the
API's required eventLocation.storeId shape.
Hash encoding
Every request is sent with encoding: 'HEX'. Google requires the field
whenever the payload contains hashed userData. The value is pinned because
all hashing in this destination produces lowercase hex SHA-256 digests;
exposing encoding as a setting would risk silently mismatched identifiers.