In this article, we'll guide you through connecting Campaign Manager 360 (CM360) to GrowthLoop and syncing conversions to the destination.

Campaign Manager 360 (CM360) is a Google Marketing Platform tool used to track and manage digital ad campaigns, including sending and attributing conversions back to ads for accurate performance measurement.

GrowthLoop supports two conversion modes for CM360:

• Standard Offline Conversions — Create new offline conversion events using the batchinsert API.
• Enhanced Conversions — Enrich existing online tag-based conversions with user identifiers (email, phone, address) using the batchupdate API, improving conversion attribution accuracy.

Supported Objects

GrowthLoop enables syncing to the following objects:

Prerequisites

Standard offline conversions

• Add our production service account to your Ad Manager network:
  [email protected] Click here for step-by-step instructions on how to configure service account access.
• Have your Profile ID ready. This seven-digit number defines your access permissions and scope within a specific CM360 account. You can find it by logging into your CM360 account, navigating to the Admin section, and selecting User Profiles — your assigned Profile ID will be listed there.
• Have your Floodlight Activity ID ready. You can either apply the same ID to all rows during the sync by specifying it in the Setup Destination page, or dynamically assign a different ID to each row by mapping a column from your dataset on the Sync Field Mapping page.

Enhanced conversions

All of the standard prerequisites above, plus:

• Accept the Enhanced Conversions Terms of Service in the CM360 UI before enabling this feature.
• Website instrumentation: Your online tags must capture a match_id so that GrowthLoop can reference the original conversion.
• Timing: Enhanced conversion data must be sent between 90 minutes and 24 hours after the original online conversion was captured by the tag.
• User consent: Ensure you have obtained consent from users for data enhancement in accordance with your privacy policies.
• User identifiers: Your source table must include at least one of the following: email, phone_number, or address components (first_name, last_name, street_address, city, state, country_code, postal_code).

📘

Note

GrowthLoop automatically normalizes and SHA-256 hashes all user identifiers before sending them to CM360. Email addresses are lowercased and trimmed, Gmail/Googlemail addresses have periods removed from the local part, and phone numbers are converted to E.164 format. You do not need to pre-hash your data.

Setup destination

1. Log into GrowthLoop and click the Destinations tab on the left sidebar.

2. Click New Destinations on the upper right side.

3. Search for Campaign Manager 360 in the destination modal and click Add Campaign Manager 360.

4. Enter the required information in the modal, then click Create.

   1. Destination: Enter the name you want to give the destination.
   2. Sync Frequency: Select a default export frequency to the destination.
   3. Profile ID (Required): Enter the seven-digit number that defines your access permissions and scope within a specific CM360 account.
   4. Floodlight Activity ID: Enter the Activity ID where you want to send your conversions. This is optional if you prefer to dynamically assign a different ID to each row. See Sync Field Mapping section for details.
   5. Enhanced Conversions: Set to true to enable enhanced conversions mode. When enabled, GrowthLoop uses the batchupdate API to enrich existing online conversions with user identifiers instead of creating new offline conversions.

Set up a sync (standard offline conversions)

1. Click Syncs on the left sidebar.

2. Click Create Sync on the upper right hand-side.

3. Configure your sync by filling out the following fields:

   1. Route Name:

      1. Name: A friendly name for the sync.

   2. Source:

      1. Dataset/Table: The table that holds the data you want to sync. Usually, it's organized within an events table.
      2. Dataset Unique Field(s): The unique field(s) on the table. They will populate automatically after selecting the Dataset/Table.
      3. Match Field: The user identifier used to match and identify conversions from your source table in the destination (e.g., Google Click ID).

   3. Destination:

      1. Connection: The destination you will sync data to. Select Campaign Manager 360.
      2. Object Type: The object that you want to send data to. Select Conversion.
      3. Match Field: The user identifier used to match and identify conversions from the destination in your source table (e.g., Google Click ID).

   4. Sync Settings:

      1. Sync Frequency: The default frequency for syncing data to the destination. The options are: Fifteen minutes, Thirty minutes, Hourly, Daily, Weekly, and Monthly.
      2. Update Rule: The default operation for syncing data to the destination. Select Insert only.

4. Once you finish selecting/inserting the required fields, click Save Sync.

5. Next, set up the field mappings to start your sync. CM360 needs at least three of the following fields mapped: Floodlight Activity ID, Timestamp, and the same user identifier used to set up the sync.

📘

Note

• If Floodlight Activity ID is set in the destination setup, you don't need to map it.
• The column you map to Timestamp will also be used as the ordinal for deduplicating conversions. To use a custom value for ordinal, you can map a separate column.
• Quantity is automatically set to "1" for each conversion you want to sync. To use a custom value, you can map a separate column.
• Encrypted user ID and candidates are not supported user identifier types.

6. Let's begin with Floodlight Activity ID. Choose the field from your table that contains the Activity ID where you want to send your conversions.
7. Then, under the Destination section, choose Floodlight Activity ID from the drop-down menu, unless it has been automatically selected for you.
8. Next up, let's map Timestamp. Pick the field from your table that contains the date and time of the conversion.

📘

Note

GrowthLoop will convert any provided timestamp format into Unix epoch time in microseconds.

9. Then, under the Destination section, choose Timestamp from the drop-down menu, unless it has been automatically selected for you.
10. Lastly, choose the field in your source table that contains the user identifier associated with the conversion, and map it to the destination.

📘

Note

Must be the same user identifier used to set up the sync.

11. After clicking Update Sync, GrowthLoop will validate the information you provided. If everything looks good, your sync will be saved, and you can enable it by toggling the switch in the top-left corner of the page.

👍

Success

You've successfully created a standard conversion sync to CM360!

Set up a sync (enhanced conversions)

If you enabled Enhanced Conversions in the destination setup, follow these steps instead.

1. Click Syncs on the left sidebar.

2. Click Create Sync on the upper right hand-side.

3. Configure your sync by filling out the following fields:

   1. Route Name:

      1. Name: A friendly name for the sync.

   2. Source:

      1. Dataset/Table: The table that holds the conversion data along with user identifiers.
      2. Dataset Unique Field(s): The unique field(s) on the table. They will populate automatically after selecting the Dataset/Table.
      3. Match Field: Select Match ID — this is the identifier captured by your online conversion tag.

   3. Destination:

      1. Connection: Select your Campaign Manager 360 destination (with enhanced conversions enabled).
      2. Object Type: Select Conversion.
      3. Match Field: Select Match ID.

   4. Sync Settings:

      1. Sync Frequency: Select a frequency that ensures data is sent between 90 minutes and 24 hours after the original conversion. Hourly or Daily are recommended.
      2. Update Rule: Select Insert only.

4. Click Save Sync.

5. Set up the required field mappings:

   1. Floodlight Activity ID — Map the field from your table that contains the Activity ID, or leave unmapped if it's already set in the destination configuration.
   2. Timestamp — Map the field that contains the date and time of the original online conversion. This must match the original conversion timestamp within 1 minute.
   3. Match ID — Map the field that contains the matchId from the original online conversion tag.
   4. User identifiers — Map at least one of the following:

📘

Note

• You can provide up to 5 user identifiers per conversion. If more are provided, GrowthLoop will use the first 5.
• Pre-hashed values (SHA-256 hex strings) are accepted and will not be double-hashed.
• Quantity defaults to 1 and Value defaults to 0 for each conversion. To use custom values, map separate columns.

1. After clicking Update Sync, GrowthLoop will validate your configuration. If everything looks good, your sync will be saved, and you can enable it by toggling the switch in the top-left corner of the page.

⚠️

Warning

Enhanced conversions can only update conversions that were already captured by an online tag. If the original conversion is not yet indexed by CM360 (typically takes up to 90 minutes), the update will receive a NOT_FOUND response. GrowthLoop will automatically retry these records.

👍

Success

You've successfully created an enhanced conversion sync to CM360!

📘

Note

If you experience any issues when connecting to Google Campaign Manager 360 Conversions, please reach out to us at [email protected], and we'll be in touch shortly to help resolve the matter!