> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runconverge.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Google CM360

> Send Converge conversions to Floodlight activities in Google Campaign Manager 360 (CM360)

## Overview

Destination Type: Client-side

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 [enhanced conversions](https://support.google.com/campaignmanager/topic/6094315) 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**.

> [!WARNING]
>
> 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.

| Counting method | Type | What Converge sends |
| - | - | - |
| `standard` | Counter | One conversion each time the event fires. |
| `unique` | Counter | Same as `standard`. CM360 keeps only the first per user per day. |
| `per_session` | Counter | One conversion with the Converge session ID, so CM360 counts one per session. |
| `transactions` | Sales | The [conversion amount](https://docs.runconverge.com/destinations/conversion-amount.md) as revenue, and the event ID as the transaction ID. |
| `items_sold` | Sales | The conversion amount, the event ID as the transaction ID, and a quantity. See the setting below. |

***

## Configuration

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

| Setting | What it does |
| - | - |
| Conversion amount | Which revenue value Converge sends for sales activities. See [Conversion amount](https://docs.runconverge.com/destinations/conversion-amount.md). |
| Deploy a separate data layer for Converge | On for destinations you create in the app. Converge then uses its own data layer, so existing `dataLayer` events on your site aren't picked up. When it's off, Converge shares your site's `dataLayer`. |
| Count transaction as single conversion | On by default. For `items_sold` activities, sends a quantity of 1 per order. Turn it off to send the total number of items in the order instead. |
| Google Tag Gateway path | Loads the tag through your Google Tag Gateway. See [Implementing Google Tag Gateway](https://docs.runconverge.com/guides/implementing-google-tag-gateway.md). |

### 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.

| Converge Feature | Supported |
| :- | :-: |
| [Custom Events](https://docs.runconverge.com/destinations/event-mapping.md#event-mapping-modes) | |
| [Filters](https://docs.runconverge.com/destinations/filters.md) | |
| [Server-side Conversions](https://docs.runconverge.com/destinations/event-mapping.md#forwarding-modes) | |
| [Conversion amount](https://docs.runconverge.com/destinations/conversion-amount.md) | |

***

## 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](#installation-instructions). Any Converge event, including custom events, can be mapped. All mappings fire from the browser.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.