Skip to main content

​
Overview

Destination Type: The Google CM360 destination fires your Floodlight activities in Google Campaign Manager 360 (CM360) from the browser with Google’s tag (gtag.js). In the app it’s called Google Campaign Manager 360 - Floodlight activity. It supports and Consent mode v2.

​
Before you start

You need two things from CM360:
  • Your Floodlight Config ID: DC- followed by digits or uppercase letters, for example DC-123456.
  • For each conversion you want to track, the Floodlight activity’s group tag string, activity tag string, and counting method. You find them in the activity’s tag in CM360.

​
Installation instructions

  1. In the Converge sidebar, click on Destinations and then click Create new destination.
  2. Select the Google Campaign Manager 360 - Floodlight activity destination and click Next.
  3. Give your destination a name (e.g. CM360) and click Next.
  4. Fill in your Floodlight Config ID (e.g. DC-123456) and click Next.
  5. Map each Converge event to a Floodlight activity. Converge suggests Placed Order. In Forward as, enter the activity as DC-[floodlightConfigID]/[activityGroupTagString]/[activityTagString]+[countingMethod], for example DC-123456/sales/purchase+transactions. Click Next.
  6. Select the sources you want to forward events from, then click Next.
  7. Review any issues and click Submit.
Once you have installed your Converge Destination, you should pause or remove your existing Floodlight tags for the same activities. Leaving these on will lead to duplicate tracking.

​
Counting methods

The counting method at the end of Forward as decides what Converge sends with each conversion.

​
Configuration

Open your destination, click Configuration, and open the Advanced configuration (optional) section.

​
Enhanced conversions

When Converge knows the customer’s email, phone number, or address, it sends them to Google as user data for enhanced conversions. Turn on enhanced conversions for your Floodlight configuration in CM360 to use them.

​
Converge functionality

This integration supports the following Converge destination functionality.

​
Event mapping

Events aren’t mapped automatically, because every Floodlight activity has its own tag. Map each Converge event to an activity as described in step 5 of the installation instructions. Any Converge event, including custom events, can be mapped. All mappings fire from the browser.