Google Data Manager API

Overview

The Google Data Manager API is Google's unified ingestion API for first-party data across its advertising products. Ours Privacy provides an early integration with this API for organizations that have a specific reason to use it instead of the standard Google Ads destination.

Limited availability. This destination is in private beta and is not self-serve — an Ours Privacy team member must enable it for your account. For most customers we recommend the standard Google Ads destination or the Google Campaign Manager 360 destination, which are more mature integrations.

The integration uses server-side tracking. Ours Privacy proxies events through the server, so Google does not directly interact with your clients' browsers or receive their IP addresses.

Web Conversions

Web conversion types are not yet supported through this destination. The Data Manager API currently supports offline and upload conversion types. Web conversion support depends on Google completing its own rollout.

Supported Google Products

This destination can send conversion data to the following Google advertising products. Actual support per product varies based on Google's rollout of the Data Manager API:

Google Ads

• Search Ads
• Display Ads
• Shopping Ads
• Performance Max
• YouTube Ads
• Discovery Ads
• App Campaigns

Not Supported

This destination does not support the Google Marketing Platform 360 suite. For Campaign Manager 360, Search 360, Display & Video 360, and Floodlight, use the Google Campaign Manager 360 destination.

When to Consider This Destination

Most customers should use the standard Google Ads destination. Reach out to support@oursprivacy.com before configuring this destination if you have a use case that the standard Google Ads destination cannot cover — for example, offline conversion uploads with multiple identifier types — and we will confirm whether the Data Manager API destination is the right fit today.

Supported Data Types

User Identifiers

The Data Manager API accepts multiple identifier types:

• Email address (hashed)
• Phone number with country code (hashed)
• Full address: first name, last name, street, city, state, postal code, country

Cart Data

• Cart items: product IDs, quantities, prices
• Transaction discounts
• Merchant identifiers

User Properties

• Customer type: NEW, RETURNING, or REENGAGED
• Customer value bucket: LOW, MEDIUM, or HIGH
• Custom properties

Custom Variables

Custom conversion variables defined in your Floodlight or Google Ads configuration.

Setup and Configuration

Prerequisites

Before this destination can be set up:

• An Ours Privacy team member needs to enable the destination on your account
• A Google Ads account with conversion actions configured
• A user with permission to manage conversion actions
• (Optional) A Google Ads Manager account if managing multiple client accounts

Initial Setup

1. Contact support@oursprivacy.com to enable the destination on your account
2. Once enabled, open Destinations in your Ours Privacy platform
3. Click Add destination and select Google Data Manager API
4. Click Authenticate with Google and sign into your Google account
5. Select your Google Ads Account from the dropdown
6. Configure your conversion action mappings

Manager Account Support

If you manage multiple Google Ads accounts through a Manager account:

1. Authenticate using your Manager account credentials
2. Enter your Manager Account ID in the configuration
3. Select the client account to send conversions to

Conversion Action Configuration

You can configure conversion actions in two ways:

Automatic Sync: Ours Privacy can sync your allowed events with Google Ads conversion actions. Click the Sync button after configuring your events.

Manual Entry: If you prefer to manage conversion actions directly in Google Ads, you can manually enter the Conversion Action ID for each event mapping.

Event Mapping Options

PII fields are optional. Identifier fields like email, phone, and address are optional. Sending additional identifiers can improve match rates, but you should evaluate your own privacy policies and compliance requirements (including HIPAA) before including them. Conversion tracking is possible using only ad identifiers (GCLID, GBRAID, WBRAID) without sending PII.

When configuring event mappings, you can specify the following fields:

Required Fields

• Event Name: The event name in your Ours Privacy platform
• Conversion Action: The Google Ads conversion action to map to

User Identifiers

• Email: User's email address (automatically hashed)
• Phone: User's phone number with country code (automatically hashed)
• First Name (automatically hashed)
• Last Name (automatically hashed)
• Street Address (automatically hashed)
• City (automatically hashed)
• State: State or region code
• Postal Code: ZIP or postal code
• Country: Two-letter country code (e.g., US, CA, GB)

Ad Identifiers

• GCLID: Google Click Identifier
• GBRAID: Google App Click Identifier (iOS)
• WBRAID: Google Web-to-App Click Identifier

Conversion Data

• Value: Monetary value of the conversion
• Currency: Three-letter currency code (e.g., USD, EUR)
• Transaction ID: Unique transaction identifier
• Order ID: Order identifier for purchase events

Cart Data

• Cart Items: Array of products with item details
• Transaction Discount: Discount amount applied
• Merchant ID: Store or merchant identifier

User Properties

• Customer Type: NEW, RETURNING, or REENGAGED
• Customer Value Bucket: LOW, MEDIUM, or HIGH
• Custom Properties: Additional key-value pairs

Consent Fields

• Ad User Data Consent: Whether the user consented to ad data usage
• Ad Personalization Consent: Whether the user consented to ad personalization

Implementation

Basic Event Tracking

After configuring your destination, track conversion events using the Ours Privacy SDK:

ours('track', 'Purchase', {
  value: 150.0,
  currency: 'USD',
  transaction_id: 'TXN-12345',
});

Including User Data

To include user identifiers:

ours('track', 'Submit Lead Form', {
  value: 50.0,
  email: 'user@example.com',
  phone: '+15551234567',
  first_name: 'Jane',
  last_name: 'Smith',
  street_address: '123 Main St',
  city: 'San Francisco',
  state: 'CA',
  postal_code: '94105',
  country: 'US',
});

Including Cart Data

For e-commerce conversions:

ours('track', 'Purchase', {
  value: 299.99,
  currency: 'USD',
  transaction_id: 'ORD-78901',
  cart_items: [
    { item_id: 'SKU-001', quantity: 2, price: 99.99 },
    { item_id: 'SKU-002', quantity: 1, price: 100.01 },
  ],
  transaction_discount: 0,
});

User Properties

ours('track', 'Purchase', {
  value: 500.0,
  currency: 'USD',
  transaction_id: 'ORD-45678',
  customer_type: 'RETURNING',
  customer_value_bucket: 'HIGH',
});

Privacy Features

Server-Side Architecture

• All events are sent through Ours Privacy servers, so Google does not directly interact with your users' browsers
• User IP addresses are not sent to Google
• PII (email, phone, address components) is automatically hashed before transmission
• Built-in support for ad user data and ad personalization consent flags

Consent Handling

You can pass consent signals with your events:

ours('track', 'Purchase', {
  value: 100.0,
  currency: 'USD',
  ad_user_data_consent: 'GRANTED',
  ad_personalization_consent: 'GRANTED',
});

Technical Details

When Events Dispatch

Events are dispatched to the Google Data Manager API when:

1. The destination is authenticated and configured
2. The event name matches an allowed event on your destination
3. At least one valid identifier is present (gclid, gbraid, wbraid, or user identifiers)

Automatic Retry

If the Google Data Manager API returns a retriable error (such as a temporary API issue or rate limiting), Ours Privacy will automatically attempt to re-dispatch the event.

Next Steps

• Google Ads: Standard Google Ads conversion tracking. Recommended for most customers.
• Google Campaign Manager 360: For the Google Marketing Platform 360 suite.
• Google Data Manager API reference: Google's own documentation for the underlying API.

Need Help?

If you have questions about this destination or want to discuss whether it fits your use case, reach out to support@oursprivacy.com.