Google Campaign Manager 360 Conversions
Use warehouse conversion events for Campaign Manager 360 measurement.
Connect this destination to write warehouse conversion events onto Campaign Manager 360, for use in measurement. You do not need an audience.
This destination writes to your Campaign Manager 360 account and is a good fit when you want to:
- Send offline conversions in Campaign Manager 360
- Enrich tag-based conversions with email, phone, or address
This maps to GrowthLoop Syncs:
| Use it for | Syncs |
|---|---|
| Creating offline conversion events | ✓ |
| Enhancing existing online conversions with user identifiers | ✓ |
To export Customer Match lists or sync Google Ads conversions, use Google Ads.
Prerequisites
Make sure you have:
- GrowthLoop's production service account added to your Ad Manager network:
[email protected]. See Google's service account access. - Your Profile ID. This seven-digit number is in CM360 under Admin → User Profiles.
- Your Floodlight Activity ID. Set it on the destination for every row, or map a column on the sync.
If you will sync enhanced conversions, you also need:
- The Enhanced Conversions Terms of Service accepted in the CM360 UI.
- Website tags that capture a
match_id. - Consent to enhance user data.
- At least one of
email,phone_number, or address components (first_name,last_name,street_address,city,state,country_code,postal_code). - Timing that lands between 90 minutes and 24 hours after the original online conversion.
NoteGrowthLoop normalizes and SHA-256 hashes user identifiers before sending them to CM360. Email is lowercased and trimmed. Gmail and Googlemail addresses have periods removed from the local part. Phone numbers are converted to E.164. You do not need to pre-hash. Pre-hashed SHA-256 hex strings are accepted and are not hashed again.
Set up Campaign Manager 360 as a destination
- In GrowthLoop, click the Destinations tab on the left sidebar.
- Click New Destination in the upper right corner.
- Search for Campaign Manager 360 and click Add Campaign Manager 360.
- Enter the required information, then click Create.
| Field | Description |
|---|---|
| Destination Name | Name this destination in GrowthLoop. Use a name so your team recognizes its purpose, like "Campaign Manager 360 Conversions". |
| Sync Frequency | Set the default frequency (for example, hourly or daily). You can override this setting for individual syncs. |
| Profile ID | Required. Seven-digit ID from CM360 Admin → User Profiles. |
| Floodlight Activity ID (optional) | Activity ID for every row. Leave blank if you will map a different ID per row. |
| Enhanced Conversions | Set to true to enrich existing online conversions with batchupdate. Leave off to create new offline conversions with batchinsert. |
GrowthLoop validates the connection. Campaign Manager 360 then appears in your list of connected destinations.
Create a sync in GrowthLoop
Create a sync from a warehouse table to write conversion events onto Campaign Manager 360. See Syncs for information on how to complete those steps.
Select an Object Type:
| Object | Use it for | Sync modes |
|---|---|---|
| Conversion | New offline conversion events (batchinsert) | Insert |
| Enhanced Conversion | Enrich existing online conversions (batchupdate) | Update |
Use a destination with Enhanced Conversions set to true for enhanced conversions. Use a destination without that setting for standard offline conversions.
When you configure the sync:
- Connection: Select your Campaign Manager 360 destination.
- Object Type: Select Conversion.
- Update Rule: Choose Insert only.
- Dataset/Table: Select the warehouse table that holds the conversions.
- Match Field: For standard conversions, map a click identifier such as Google Click ID. For enhanced conversions, map Match ID.
- Sync Frequency: Fifteen minutes, Thirty minutes, Hourly, Daily, Weekly, or Monthly. For enhanced conversions, choose Hourly or Daily so rows send between 90 minutes and 24 hours after the original conversion.
After you map fields, click Update Sync. Enable the sync with the toggle at the top of the page.
Encrypted user ID and candidates are not supported identifier types.
Standard conversion fields
| Destination field | Required | Description |
|---|---|---|
| Floodlight Activity ID | Yes, unless set on the destination | Where to send the conversion |
| Timestamp | Yes | Date and time of the conversion. GrowthLoop converts the value to Unix epoch time in microseconds. This column is also used as the ordinal for deduplication unless you map a separate ordinal column |
| User Identifier | Yes | The same click identifier you used as the match field, for example Google Click ID |
Quantity defaults to 1. Map a separate column to override it.
See Google's conversions overview.
Enhanced conversion fields
The timestamp must match the original online conversion within 1 minute.
| Destination field | Required | Description |
|---|---|---|
| Floodlight Activity ID | Yes, unless set on the destination | The conversion activity |
| Timestamp | Yes | Date and time of the original online conversion |
| Match ID | Yes | matchId from the original online conversion tag |
| At least one identifier | Normalized and SHA-256 hashed | |
| phone_number | At least one identifier | Converted to E.164 and SHA-256 hashed |
| first_name / last_name / street_address | At least one identifier | SHA-256 hashed |
| city / state | Address components | Lowercased, not hashed |
| country_code | Address component | Two-letter ISO code, for example US |
| postal_code or zip_code | Address component | Postal or ZIP code |
You can send up to 5 user identifiers per conversion. If you map more, GrowthLoop uses the first 5.
Quantity defaults to 1 and Value defaults to 0. Map separate columns to override them.
See Google's Enhanced Conversions guide.
WarningEnhanced conversions can only update conversions that an online tag already captured. If CM360 has not indexed the original conversion yet (often up to 90 minutes), the update returns
NOT_FOUND. GrowthLoop retries those rows.
Sync behavior
This is what GrowthLoop writes when you sync conversion events.
| Behavior | What happens |
|---|---|
| When it runs | GrowthLoop sends the sync as a batch on the next successful run. |
| Insert | Standard Conversion adds new offline events with batchinsert. |
| Update | Enhanced Conversion enriches existing tag-based conversions with batchupdate. |
| Standard match | Map a click identifier such as Google Click ID. |
| Enhanced match | Map Match ID. Timestamp must match the original conversion within 1 minute. |
| Enhanced window | Send enhanced data between 90 minutes and 24 hours after the original conversion. |
| Hashing | GrowthLoop hashes email, phone, and name or street identifiers. City, state, country, and postal code are not hashed. |
| Deletes | GrowthLoop does not delete conversions. |
| Missing identifier | Rows without the required fields fail. |
Confirm the export was successful
When the run finishes, confirm you can use the data in Campaign Manager 360.
- Conversion sync: Look up the Floodlight activity and confirm the conversions arrived.
- Enhanced Conversion sync: Look up the original Floodlight activity and confirm the enhanced identifiers.
In GrowthLoop, confirm the sync appears in the Syncs table. See Syncs for more information.
Congrats on successfully exporting to Campaign Manager 360 Conversions!
Troubleshooting
These are the issues we see most often. You can always email us at [email protected] for help.
| Problem | Cause | Resolution |
|---|---|---|
| Connection fails to validate | Profile ID is wrong, or the GrowthLoop service account is not on the network | Enter the seven-digit Profile ID from Admin → User Profiles. Add [email protected] |
| Standard rows fail | Floodlight Activity ID, Timestamp, or the click identifier is missing | Map those three fields, or set Floodlight Activity ID on the destination |
| Enhanced rows return NOT_FOUND | The original tag conversion is not indexed yet | Wait up to 90 minutes. GrowthLoop retries those rows |
| Enhanced rows fail | Match ID is missing, the timestamp is off by more than 1 minute, or no user identifier is mapped | Map Match ID, the original timestamp, and at least one email, phone, or address field |
| Enhanced data is rejected as too early or too late | The sync ran outside the 90-minute to 24-hour window | Use Hourly or Daily so rows send inside that window |
| A user identifier is rejected | You mapped an encrypted user ID or candidates | Use email, phone, or address components |
Updated 7 days ago