A reference for which data fields Invoca sends to Google Ads for click conversions, call conversions, Customer Match audiences, and Signal conversions.
Integrations
Google Ads: Data Mapping
Last modified on September 24, 2026
Was this page helpful?
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
A reference for which data fields Invoca sends to Google Ads for click conversions, call conversions, Customer Match audiences, and Signal conversions.
| Field | Description |
|---|---|
gclid | Captured from the URL query string |
wbraid | The ad-level ID used to track a Google Display, YouTube, or Discovery ad click on iOS |
gbraid | The ad-level ID used to track a Google Search, Shopping, Display, or Performance Max ad click on iOS |
conversion_value | The value reported in the Invoca Revenue field as the conversion value |
currency_code | The currency of the value, for example USD |
order_id | The transaction ID for the conversion |
| Field | Description |
|---|---|
caller_id | The caller’s phone number in E.164 format. See Google’s help article on how call conversion upload data is used |
conversion_value | The value reported in the Invoca Revenue field as the conversion value |
currency_code | The currency of the value, for example USD |
| Field | Description |
|---|---|
hashed_phone_number | Hashed user data. See Google’s help article on the Customer Match process and how hashed phone numbers are used |
Was this page helpful?