Google Campaign Manager 360

Google Campaign Manager 360 is part of Google Marketing Platform and serves as the central hub for campaign management, measurement, and attribution. With this destination, you can send conversion events to Campaign Manager 360 as offline conversions on your Floodlight activities.

Overview

The Ours Privacy integration with Google's Campaign Manager 360 platform enables you to track conversions and other allowed events from HIPAA-regulated sites. Ours Privacy proxies all events through the server to ensure the advertising platform never directly interacts with your clients' browsers or sees their IP addresses.

This setup allows your Campaign Manager 360 account to receive essential conversion data while you control what it receives.

Prerequisites

Before setting up this destination, ensure you have:

• A valid Google Campaign Manager 360 account that is linked to your CM360 account to grab the Activity ID for each conversion event.
• A CM360 account that is enabled for API access (this is the case by default for most CM360 accounts)
• A user profile in your CM360 account that has access to the advertiser and Floodlight activities you would like to connect and the "Insert offline conversions" permission

What This Destination Sends

This destination uploads conversions to the Campaign Manager 360 Conversions API. Each conversion is recorded against the Floodlight configuration and activity you map, matched by gclid or, when no gclid is present, dclid.

Note on Other Advertising Products

For tracking conversions in Google Ads (including Performance Max campaigns), YouTube Ads, and other Google advertising products, please refer to our Google Ads destination which provides server-side tracking for these platforms.

For enhanced conversions with higher match rates, comprehensive data payloads (cart data, user properties, full address matching), and GA4 integration, consider using the Google Data Manager API destination.

Setup and Configuration

Initial Setup

1. To add this destination, click on Destinations from your Ours Privacy platform
2. Click the Add destination button and select Google Campaign Manager 360 as the destination type
3. Click the Click to Authenticate Google button and sign into your account through Google
4. After authenticating, select your Google Campaign Manager 360 Account
5. Save or select an account - This saves your profile ID for future use

Destination Configuration

Once authenticated, you'll need to configure mappings for your events. You can pass back an array of options for each event mapping.

Note: Ours Privacy automatically collects and stores gclid and dclid on all users, so these parameters are available for mapping without additional configuration.

Consent Signals

Campaign Manager 360 accepts several per-conversion privacy fields, all optional and all mapped in the destination configuration:

• Ad User Data Consent: whether the person consented to their data being shared for advertising.
• Limit Ad Tracking: whether ad tracking is limited for this person.
• Non Personalized Ad: whether the conversion should be treated as non-personalized.
• Child Directed Treatment and Treatment For Underage: special treatment flags for the relevant audiences.

Map these from your CMP's categories so each signal matches what the visitor actually chose. See Consent Signals for the other destinations that accept per-event consent, and Limited Data Use for the CCPA-style restricted-processing flag on other platforms.

Implementation

Basic Event Tracking

After you set up this destination, you can track conversion events using:

ours('track', 'ConversionEventName');

This will send an event named "ConversionEventName" to the Ours Privacy platform. From there, you can allow it for this destination and configure the appropriate mappings.

Event Setup Process

1. Create allowed events you want to track in your Ours Privacy platform
2. Common events include conversions such as form submissions, sign-ups, and purchases
3. Enable the events and configure the appropriate Floodlight mappings
4. Save your configuration to activate the destination