This article describes how to set up the Google Ads Enhanced Conversions connector.

In this article:

API Information

This connector uses the following vendor API:

Connector Actions

Action Name AudienceStream EventStream
Send Conversion

Configure Settings

Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.

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.

    This is not the same as base64 encoding a SHA-256 string. Convert any existing SHA-256 strings to binary before base64 encoding.

Public