With Google Ads you can use ads with Google searches based on relevant keywords defined by the advertiser. Google uses these characteristics to place advertising content on pages where they think it might be relevant, based on a pay-per-click formula.
With our Google Ads Offline Conversion integration integration, you'll be able to track your ad conversion and import Kaisa call data into your Google Ads account.
In this article:
How to enable the integration
How to set it up in Google side
About User consent
1. To enable this integration, simply go to the Dashboard in your account, click on the Workflows menu, select Integrations and request Google Ads Offline Conversion integration. (This only needs to be done once and only if it is not done before). This will send a ticket to our support team that will enable the Workflow for you as soon as possible. Note that your agreement must include this workflow in order for you to use it.
2. When you have got an email saying the integration has been enabled you can go to the integrations site again and click on Setup.
3. There, you will only need to add your Customer ID (without dashes, only digits as seen below) in Google Ads and click to save the changes.
To know your Customer ID, follow these steps:
- Sign in to your Google Ads account.
- Look at the top right corner of any page.
- Find “Customer ID” above your email address.
More on this here: https://support.google.com/google-ads/answer/1704344?hl=en
4. When you save the changes click on the Google button to start the OAUTH2 flow and authorise Kaisa's Google Ads Offline Conversion App to upload conversion into your Google Ads account.
- What will this app do with user data? Kaisa will only store the email and the name of the person authorising the App so it can understand who to contact in case of an issue with the app.
- How does this app enhance user functionality? By automating the conversion upload to your Google Ads account there is no need to go through difficult ETL processes to understand which campaigns are driving the most calls.
- Privacy policy
Once you have authorised Kaisa to feed data to your account a conversion needs to be created in Google Ads. Go to Tools -> Measurements -> Conversions. Create a new IMPORT conversion:
Give it a name, and set it up the best way it suits you and use that conversion name to set up the integration in Kaisa. The conversion name should match the newly created one.
Note: please note the AutoTagging feature from Google needs to be enabled, you can do so in the Admin menu (the cog icon), then click Account Settings, then Auto-Tagging section. You'll be able to check the current status of auto-tagging for your account. To turn auto-tagging on or off, click to check or uncheck the box next to “Tag the URL that people click through from my ad”. Make sure to Save any changes. More info here: https://support.google.com/google-ads/answer/3095550?hl=en
Once everything is connected, Kaisa will import conversions 6 hours after the call is made (due to Google Ads offline conversion API restrictions).
About user consent
The Kaisa javascript (fs.js) will automatically pick up the consent value from your gtag implementation and pass it along with the offline conversion when uploaded to Google Ads.
How it works:
1) Getting the consent information from the customer
Our solution assumes that you have a working Consent Management System in place on your website. If you have also implemented gtag on your site, the integration will work automatically.
The Kaisa javascript will pick up the consent information from Google gtag by scraping the dataLayer configuration object for the latest updated setting relevant for Offline Conversion. This variable is called ad_user_data
If the ad_user_data value was found it will be stored by Kaisa for use after the call. The value stored is either denied, granted, or empty.
2) Passing it to Google
After a call has happened, the integration will pass the consent parameter along with the Google click ID in the upload of the Conversion.
Here's what we send to Google Ads:
- Conversion Name
- Conversion Value
- Conversion Currency Code
- Consent parameter
Conversion value is basically the call commission. Call commission can be setup by creating pricing models for a customer.
That's it! Any questions, don't hesitate to contact our Support team.
Comments
0 comments
Please sign in to leave a comment.