Send your event data from RudderStack to Google Ads Offline Conversions.
Google Ads Offline Conversions helps you track the offline sales which occur when your ads lead to a click or call to your business. It lets you measure your sale conversions in the offline mode after a user clicks your ad online but does not directly proceed to sale in the online mode.
RudderStack supports sending event data to Google Ads Offline Conversions via the following connection modes:
Once you have confirmed that the source platform supports sending events to Google Ads Offline Conversions, follow these steps:
From your RudderStack dashboard, add the source. Then, from the list of destinations, select Google Ads Offline Conversions.
Assign a name to your destination and click Continue.
To successfully configure Google Ads Offline Conversions as a destination, first authenticate your account by following the below steps:
Click Create Account in the Account Settings section.
From the modal, click the Sign in with Google button.
Choose the required account and grant RudderStack the required permissions.
Click Save to use the specified account:
In case you have authenticated multiple accounts, you can click Edit Credentials to select or delete any other authenticated account:
RudderStack gives an error if you try to delete an account used by any other connection set up for the same destination.
Next, configure the following settings:
Customer ID: Enter the ID associated with your Google Ads account. See FAQ for more information on obtaining your customer ID.
Subaccount: Enable this setting if you are using a Google Ads subaccount. See Google Ads documentation for more information on subaccounts.
Map your events with Google Ads Offline Conversions: Enter the RudderStack event name you want to map to the Click, Call, or Store conversion type in Google Ads.
Map your Google Ads Conversions Names: Enter the RudderStack event name corresponding to the Google Ads Conversion name created in the Google Ads dashboard. See FAQ for more information on creating click and call conversions in Google Ads dashboard.
Map your variable names to custom Google Ads variables: Enter the track event property which you want to map to the Google Ads custom variable (defined in the Google dashboard). See FAQ for more information.
User Identifier Source: Select the type of user identifier source from the dropdown. See Google Ads API documentation for more information on the different source types.
Conversion Environment: Select the conversion environment of the uploaded conversion from the dropdown. See Google documentation for more information on the different conversion environments.
The user identifier for store and click conversions: Select the default user identifier from email or phone for store and click conversions.
Hash User Identifying Information (SHA-256): This setting is enabled by default and hashes the user identifying information like email and phone number using SHA-256.
Validate Only: Enable this setting to only validate the request and not execute it. See Google Ads documentation for more information.
Google Ads permissions
This integration relies on the authorizing Google Ads user’s underlying permissions and must be at least Standard or Admin.
If you authorize the integration without the Standard or Admin permissions, the API calls will fail and a “RudderStack Admin” user will disable the integration. If you encounter an entry in your audit logs from a Rudder Adminfirstname.lastname@example.org user, it means that RudderStack disabled the integration on account of insufficient user permissions.
To avoid this, ensure that the authorizing user has the Standard permissions, at minimum.
RudderStack associates the track event with the event name defined in the Map your events with Google Ads Offline Conversions dashboard setting.
RudderStack supports the following conversion types:
If you specify a user identifier in The user identifier for store and click conversions setting but don’t include it in the payload, RudderStack looks for the following fields as user identifiers (in the same priority order):
If none of the above are present, RudderStack sends an empty user identifier.
Where can I find my Google Ads customer ID?
To get the customer ID associated with your Google Ads account, click the Help option in your Google Ads dashboard. You will find the customer ID in the resulting pop-up:
How do I create custom variables in Google Ads dashboard? Which event properties can I map with these variables?
To create custom variables in Google Ads dashboard, follow these steps:
I am getting a 400 Bad Request error message. What should I do?
If you get a 400 Bad Request error while configuring the destination, make sure your customer account is allowlisted and configured to have Standard or Administrative access levels in Google Ads. Refer to the above FAQ for steps on setting the access level permissions for the account.
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
for the working of basic functionalities of the website. We also use third-party cookies that
analyze and understand how you use this website. These cookies will be stored in your browser
consent. You also have the option to opt-out of these cookies. But opting out of some of these
have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.