Google Ads Enhanced Conversions - Legacy Connector Setup Guide

Connector actions

Action Name	AudienceStream	EventStream
Send Conversion	✓	✓

This connector is now deprecated and should only be used if you are running app incrementality studies.
For the current connector, see the Google Ads Enhanced Conversions for Web connector.

API information

This connector uses the following vendor API:

API Name: Google Enhanced Conversion API
API Version: v1
API Endpoint: <https://www.google.com/ads/event/api/>

Configure settings

Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the About Connectors article.

After adding the connector, configure the following settings:

Action settings - parameters and options

Click Next or go to the Actions tab. This is where you configure connector actions.

This section describes how to set up parameters and options for each action.

Action - Send Conversion

Parameters

Parameter	Description
Conversion Tracking ID	Required The numeric value from `AW-123456789` that uniquely identifies your advertiser account. Omit `AW-` from the mapped value.
Conversion Label	Encoded conversion tracking ID and conversion type.
Conversion Type	Type of the conversion. Only used if you do not have access to label as the advertiser.
Conversion Value	The monetary value of the conversion for the advertiser. Default value is `$1 (USD)`
Currency Code	Currency associated with the conversion value. This is the ISO 4217 3-character currency code. Default value is `USD`. Examples: `USD`, `EUR`
Conversion Time	Unix time since epoch, in microseconds. The default value is `now`.
Transaction ID	Required ID that uniquely identifies a conversion event, generated by you as the advertiser.
Google Click ID	The Google Click ID (`gclid)` that led to the user conversion, where available.
User Agent	User agent for the user that converted, if the data is retained by advertiser.
Email	User email at point of conversion. Use array type attributes to add multiple emails, phone numbers and addresses. At least one of the following must be provided: User email User full name and address
Phone Number	Phone may be provided in conjunction with email or full name and address. Use array type attributes to add multiple emails, phone numbers and addresses. User phone number at point of conversion. E.164 standard format: `+prefix, country code, subscribe number` Example: `+14150000000`
Address: First Name	User first name. For address, all data fields must be provided (first name, last name, street address, city, region, postal code, country). Use array type attributes to add multiple emails, phone numbers and addresses.
Address: Last Name	User last name. For address, all data fields must be provided (first name, last name, street address, city, region, postal code, country). Use array type attributes to add multiple emails, phone numbers and addresses.
Address: Street	User street address. For address, all data fields must be provided (first name, last name, street address, city, region, postal code, country). Use array type attributes to add multiple emails, phone numbers and addresses.
Address: City	User city name. For address, all data fields must be provided (first name, last name, street address, city, region, postal code, country). Use array type attributes to add multiple emails, phone numbers and addresses.
Address: Region	User Province, State, or Region. For address, all data fields must be provided (first name, last name, street address, city, region, postal code, country). Use array type attributes to add multiple emails, phone numbers and addresses.
Address: Postal Code	User post code. For address, all data fields must be provided (first name, last name, street address, city, region, postal code, country). Use array type attributes to add multiple emails, phone numbers and addresses.
Address: Country	User 3-letter country code in ISO 3166-1 alpha-3 format. For address, all data fields must be provided (first name, last name, street address, city, region, postal code, country). Use array type attributes to add multiple emails, phone numbers and addresses.
Customer Data Hashing	Optional Check if mapped customer data (email, phone, first name, last name, street address) is already hashed using a websafe-base 64 eoncoded SHA-256 hash. Note: This is not the same as base64 encoding a SHA-256 string. Convert any existing SHA-256 strings to binary before base64 encoding.
App Conversion for Incrementality Study	Optional Check if this action is related to a conversion event for an incrementality study.
Conversion Data for Incrementality Study	Optional Map one to many miscellaneous data fields for use in the incrementality study for this conversion event.

Common errors and troubleshooting

The following are some common error codes and resolutions:

INVALID_CONVERSION_DATA: Data for the conversion is not valid. Possible action failures are:
- No valid conversion_type or label is provided in the url or json payload: If label is not provided, then conversion_type is required. Ensure one of these has a populated value for the mapped attribute.
- The conversion_time provided in the url or json payload is too old.: Ensure that the mapped timestamp is in the correct format, for example: 2022-08-01 00:06:06+00:01. Alternatively, remove the mapping and allow the connector to send the default current timestamp.
INVALID_USER_CUSTOMER_AUTHORIZATION: Confirm that the customer ID in the connector configuration does not include AW-. The authenticated user must have at least read-only access to the account owning the conversion action.
Invalid Parameter - Action has invalid parameter value or missing required parameter / Either Email or Full Name & Address need to be provided: Required PII for Enhanced Conversions are either of the following sets:
a) customer email
b) customer first name, last name, street address, city, state, country, and zip code
Ensure that required field values are present in the event data.