What this is
Google Enhanced Conversions API (CAPI) is a real-time destination: conversion data flows out of Zeotap CDP to your Google Ads account, sent from a published journey as users reach a Send to Destinations node. Nothing flows back into Zeotap CDP from this destination. Google Enhanced CAPI improves conversion tracking accuracy in Google Ads. It allows you to securely send hashed first-party customer data to Google, enhancing attribution while maintaining user privacy. By integrating it with Zeotap CDP, you can streamline data activation for Google Ads: Zeotap CDP ensures that conversion data is securely collected, transformed, and sent to Google in a privacy-compliant manner. This integration helps you:- Improve campaign performance with more accurate conversion tracking.
- Optimise bidding strategies using better attribution data.
- Maintain compliance with data privacy regulations while sharing first-party data with Google.
Supported identifiers and actions
To match conversion data to Google users, at least one of the following must be provided:- Hashed Email Address (SHA256)
- Hashed Phone Number (SHA256)
- Hashed First Name & Last Name (SHA256) along with Country Code and Postal Code
- Upload Conversion Adjustments
Prerequisites
Ensure that the following prerequisites are met before setting up Google Enhanced CAPI:- A Google Ads account with conversion tracking enabled.
- Enhanced Conversions for Web enabled in Google Ads.
- Customer Data Terms accepted in your Google Ads account.
Gather your Google Ads details
Ensure that you have details about the below components of Google Enhanced CAPI available before creating a destination in Zeotap CDP.- Customer ID – This is your Google Ads account ID, used for sending conversion data. It is a 10-digit code (remove the hyphens before entering it in Zeotap CDP) available when you click your profile icon in your Google Ads account. Learn more
- Conversion Action – This represents the specific user action that is considered a conversion, such as completing a purchase, signing up for a newsletter, or submitting a form.
- Transaction ID – This is a unique identifier assigned to each conversion event, helping to deduplicate and match enhanced conversions.
-
API Credentials –
Set up OAuth 2.0 authorisation for Google Ads API access by creating an app in your Google Cloud Platform (GCP) project. Follow the steps in the Google Ads API documentation to complete the setup.
Retrieve the following credentials for authentication:
- Developer token – Available in your Google Ads account. Learn more
- Client ID – Available in the app you created. Learn more
- Client secret – Available in the app you created. Learn more
- Refresh token – Generated while setting up your app. Learn more
These credentials belong to the Google Ads API. You create and manage them in your own Google Ads account and Google Cloud Platform project.
Create the Google Enhanced CAPI destination
Once you have taken care of the prerequisites above, proceed to creating a workflow in Journeys. After you have applied filters or added conditions for your users in Journeys as described in Create a Workflow, you can activate them in Google Enhanced CAPI from the Send to Destinations node.
Note:To use an existing destination for activation in Journeys, see Add the destination to a journey.
1
Click + Add New Destination as shown below.

2
Search for Google Enhanced CAPI.
3
Click Google Enhanced CAPI and enter a name for the destination.
4
In the Destination Instance Name field, enter a value of your choice.
5
Enter the following values you gathered from Google:
- Customer ID
- Client ID
- Client secret
- Refresh token
- Developer token
6
Review the fields entered above and click Next.
7
On the Mapping screen, under Choose your Action, select Upload Conversion Adjustments to send data from the workflow created in Journeys. Map the required identifiers and attributes based on your use case. Under Map the Fields, the Mandatory Attributes group lists the destination fields you must supply a Catalogue attribute for — Order ID and Conversion Action. Without both, you cannot proceed.Under Custom Identifier, select + Add Mapping Field to add any custom identifier you want to send to Google Ads.

8
Once the mapping is complete, click Create Destination. The destination is created and made available for activation on Journeys as shown below.

Add the destination to a journey
After creating a destination, you can link it in the Send to Destination node within the workflow, as explained below.1
Click the destination you created from the list of available destinations.

2
Under the Destination Details tab, the Customer ID, Client ID, Client secret, Refresh token and Developer token fields are automatically populated based on the values that you entered while creating the destination.
3
Under the Destination Settings tab, choose the action and mapping as per your requirement.
4
Click Save Destination and then click Add Destinations.
You can also add multiple destinations at this step if needed.
5
The linked destinations appear in the Send to Destination node within the workflow as shown below. You can then build and customise your workflow as needed by clicking +. Note that you must enter a name for your workflow in the provided text box to save it.

6
After adding conditions and filters for users, choose one of the following options:a. Save Draft: Enables you to revisit and edit the workflow before publishing.b. Next: Define Re-entry Criteria: Determines whether a user can re-enter the same workflow.
7
After defining the re-entry criteria, click Publish Workflow. The workflow appears in the Workflow listing screen with a Published status.

Verify the integration
After publishing the workflow, confirm that conversion data is reaching Google Ads:- Check that the workflow appears on the Workflow listing screen with a Published status.
- On the journey canvas, look at the Send to Destination node. Destination nodes with failures show red error count badges, while successful deliveries show green indicators. See Journey Error Codes.
- Open the node’s View Executions panel to read the Total Events Entered, Successful Events and Failed Events counts for the node.
- For an individual profile, open the right-hand Execution Details sidebar on the failed node. It shows the failure status code, the timestamp, the destination name and the Request ID. See Identify Journey Errors.
Troubleshoot Google Enhanced CAPI deliveries
After any configuration change, use the refresh icon in the execution view to pull the latest execution data before concluding whether the fix worked.