You need to have access to at least one user profile and one advertiser in Google Marketing Platform to sync data.
Go to the Destinations overview page and click the Add destination button. Select Google Campaign Manager 360 and click Continue. You can then authenticate Hightouch to Google Campaign Manager 360 via OAuth.
For the Authentication method, select Log in to Google Campaign Manager 360 and log into your Google Campaign Manager 360 account. Once successful, you will be redirected back to Hightouch to enter a descriptive name for your destination and complete setup.
Once you've set up your Google Campaign Manager 360 destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the Google Campaign Manager 360 destination you want to sync to.
To ensure syncs send each event, your event model must use a truly unique primary key. See the events syncs documentation for more information.
Google Campaign Manager requires each conversion to be associated with a Floodlight activity and configuration.
Hightouch provides a dropdown to select the available activities and configurations based on your Google Campaign Manager profile.
You can either select a static value for all events or select to use a column from your model.
You can opt to include encrypted user IDs in your conversion event payload.
Hightouch obtains encrypted user IDs from the %m match macro or Data Transfer.
If you are including, dclid, gclid, matchId, or a mobile device ID in your field mapping, you don't need to enable this.
Field mapping is where you select which customer information parameters or other event parameters you want to send to the Conversions API.
You can map data from any of your model columns to default and custom Google fields.
The Conversions API requires you to include at least one of the user identifier parameters below in your event payload, so be sure to map one here.
The identifiers options are:
Mobile device ID
Google Click ID
Match ID
Display Click ID
Encrypted user ID
Encrypted user ID candidates
You should provide only one of these user identifiers for matching.
To date, our customers haven't experienced any errors while using this destination. If you run into any issues, please don't hesitate to . We're here to help.
Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.