Google Ads Conversions API Reference
The Google Ads Conversion API requires setting up new Conversion Actions within Google Ads. If you want to re-use your existing Google Ads configuration, take a look at the Google Ads Proxy Destination.
Optimize your Google Ads spend by attributing ad clicks to conversion and other key behaviors.
Destination Info
Supports Track calls
Supports HIPAA mode
Refer to this destination as Google Ads Conversion API in the Integrations object
Connection Modes:
Client-side | Server-side | |
---|---|---|
Web | ||
Mobile | ||
Server |
This is a reference document for the Google Ads Conversions API destination. For information on how to set up this integration, see the Quick Start guide.
Events
Freshpaint .track()
events map to any Click Conversions you've already created in Google Ads.
Track Events
When you send an event to Google Ads, you can track conversions from your ad campaigns based on those events.
Server-side
Freshpaint's servers use the same API as the client-side Google Tag. You may provide the following additional event properties:
Freshpaint property | Google Ads parameter | Type | Required? | Description |
|
| string | Required | gclid (Google Click ID) is generated at ad click time and appended to the landing page URL. Freshpaint will automatically capture gclid for events from your website. If you wish, you may provide |
|
| string | Required | The Conversion Name or Conversion Id of the conversion action in Google Ads. When using the Conversion Name, the Freshpaint integration will lookup the conversion id before sending the event to google. |
|
| number | Optional | The time the event occurred as a unix epoch. The time needs to be after the ad is clicked or it won't be accepted by google. |
|
| object | Optional | The cart data associated with this conversion. Google Docs |
|
| list | Optional | Additional data about externally attributed conversions. This field is required for conversions with an externally attributed conversion action, but should not be set otherwise. Google Docs |
|
| list | Optional | The custom variables associated with this conversion. Google Docs |
|
| enum | Optional | The environment this conversion was recorded on, for example, App or Web. Google Docs |
|
| number | Optional | Value of the conversion. See About conversion values for more information |
|
| string | Optional | Currency of the conversion value, "USD" by default. See the list of supported currency codes. |
|
| string | Optional | The email address of the user |
|
| string | Optional | The phone number of the user |
|
| string | Optional | Mobile device ID (advertising ID/IDFA). Accepted only for Customer Match. |
|
| string | Optional | Advertiser-assigned user ID for Customer Match upload, or third-party-assigned user ID for Store Sales. Accepted only for Customer Match and Store Sales. |
|
| object | Optional | Address information. Accepted only for Customer Match, Store Sales, and ConversionAdjustmentUploadService. Google Docs |
Freshpaint will only deliver events to Google when a user arrives on your site by clicking on a Google Ad, thus generating an gclid
. Without gclid
, Google will not be able to attribute conversions.
Setup Conversion Actions
When using the conversion API to send converisons to Google Ads, you will need to create new import
conversion actions.
Get your google conversion label. In your Google Ads account go to Tools > Conversions.
Click
+ New Conversion Action
to create a new conversion action.
Considerations
Conversions may take up to 24 hours to appear in your Google Ads Conversion Goals.
Google Ads API v15 introduces a consent object to indicate whether users within the European Economic Area have consented to the event being shared with Google. If the event is enabled and consented to within Freshpaint using the Freshpaint consent management features, Freshpaint will automatically mark the event as consented to when sending the event to Google's servers. See Consent Management for more information.
View-Through Conversions and Retargeting
View-through conversions and retargeting are possible for users when an identifier such as email or phone number is shared with Google.
Note that retargeting of anonymous users is not possible, due to the absence of an identifier that can be used to retarget that user.
Last updated