Google Campaign Manager 360

To connect the Google Campaign Manager 360 destination, set up the prerequisites and then connect it to a source.

Before you begin, you need to have a Google Campaign Manager 360 account, with a Profile ID and a Floodlight Configuration ID. These are necessary to configure the Floodlight activities you want to track.

1. From the Segment web app, navigate to Catalog > Destinations.
2. Search for "Google Campaign Manager 360" in the Destinations Catalog, and select it.
3. Click Add destination.
4. Select the source that will send data to Google Campaign Manager 360.
   • If you select an Engage space, you'll be redirected to Engage to complete the following steps.
   • If you select a Reverse ETL source, you must enter a name for your destination and click Create destination.
5. On the Settings tab for your Google Campaign Manager destination:
   • Enter your Profile ID. Optionally, you can also provide your default Floodlight Configuration ID and/or your default Floodlight Activity ID. These fields are optional, but if you provide them, they will be used as defaults for all events sent to Google Campaign Manager 360. Otherwise, you can override these values in your mappings.
6. Click Save.
7. Follow the steps in the Destinations Actions documentation to customize your mappings.

The Google Campaign Manager 360 Action Destination supports the following actions:

• Conversion Upload
• Conversion Adjustment Upload

The Conversion Upload action allows you to send conversion data to Google Campaign Manager 360. This action is useful for tracking conversions that occur on your website or app.

The Google Campaign Manager 360 destination requires the following fields for the Conversion Upload action:

• Required ID: The identifier that identifies a user for the conversion. Only one value at a time can be provided from the following fields:
  • Google Click ID (gclid);
  • Display Click ID (dclid);
  • Encrypted User ID;
  • Mobile Device ID;
  • Match ID;
  • Impression ID;
  • Encrypted User ID Candidates;
• Timestamp: The time the conversion occurred.
• Value: The value of the conversion.
• Ordinal: The ordinal of the conversion. This field is used to control how conversions of the same user and day are de-duplicated.

The Conversion Adjustment Upload action allows you to send conversion adjustment data to Google Campaign Manager 360. This action is useful for adjustments to conversions that have already been uploaded, as well as enhancing conversions.

The Google Campaign Manager 360 destination requires the following fields for the Conversion Adjustment Upload action:

• Required ID: The identifier that identifies a user for the conversion. Only one value at a time can be provided, from the following fields:
  • Google Click ID (gclid);
  • Display Click ID (dclid);
  • Encrypted User ID;
  • Mobile Device ID;
  • Match ID;
  • Impression ID;
• Timestamp: The time the conversion occurred.
• Value: The value of the conversion.
• Ordinal: The ordinal of the conversion. This field is used to control how conversions of the same user and day are de-duplicated.

Google requires you to hash all PII before sending it to the Google API.

The Google Campaign Manager 360 destination supports hashing for the following fields:

• Email
• Phone
• First Name
• Last Name
• Street Address

The hashing algorithm used is SHA-256. If incoming data arrives already hashed, the destination will not hash it again. The values will be sent as-is to Google.

When you use OAuth to authenticate into the Google Campaign Manager 360 destination, Segment stores an access token and refresh token. Access tokens for Google Campaign Manager 360 expire after one hour. Once expired, Segment receives an error and then uses the refresh token to fetch a new access token. This results in two API requests to Google Campaign Manager 360, one failure and one success.

Because of the duplicate API requests, you may see a warning in Google for unprocessed conversions due to incorrect or missing OAuth credentials. This warning is expected and does not indicate data loss. Google has confirmed that conversions are being processed, and OAuth retry behavior will not cause any issues for your web conversions. Whenever possible, Segment caches access tokens to reduce the total number of requests made to Google Campaign Manager 360.