Onboarding

Google Ads channels offer a seamless onboarding experience through the OAuth process, which connects your Google Ads account with EdgeTag. This integration enables your site to send events to Google Ads. Let's walk through the process.

Before you start the process, we need to have conversion actions created in the Google Ads dashboard first. Please follow these instructions to create one browser and one server conversion action. If you have a preference for running integration purely on the browser side or the server side, you can create only those conversion actions.

Video Guide

Authorization

To add a channel, begin by entering the channel's name. We recommend choosing a name that clearly describes the dataset you are adding. This will assist with debugging if any issues arise. Once you have entered the name, click on "Sign in with Google."

This will redirect you to the Google Ads authorization flow, where you will need to confirm your identity and grant the necessary permissions for our system to function correctly. Ensure that you enable the checkbox if you are authenticating for the first time.

After completing the Google Ads process, you will be redirected back to our app to finish the onboarding.

Now we need to select the Google Ads ad account, map the conversions created in Google Ads, and that's it. Let's go over how to set up these fields one by one.

Ad account ID

In the provider form, the Select Account dropdown will show you the list of ad accounts to which you have access. We need to ensure that we select the correct ad account.

To find the ad account ID of your Google Ads ad account, go to the Google Ads dashboard. In the top right, you would see your name, ad account name, and ID. In the Select Account dropdown on the form, ensure that you select the same ad account ID as previously.

Sub account ID

If your ad account is managed within an MCC or Manager ad account, this field is mandatory. We will need to select the ad account ID of your sub-account in the Select sub-account dropdown. This would help us in identifying to which exact sub-account the data should be sent.

Conversions Mapping

Once the Ad account and Sub account (if applicable) are selected, we will retrieve all browser and server conversion actions created in the Ad account. From here, you need to map the EdgeTag events that you are capturing on the website with Google Ads conversion actions. Based on the mapping added, we will try to send the event data to the mapped conversion actions.

In the above image, Purchase was mapped to a browser conversion and a server conversion. Once the purchase occurs on the website, we will attempt to send the purchase event to browser conversion via gtag. If that fails, we then send the same purchase event to the server conversion.

However, if you map only a browser conversion or only a server conversion against an event, we will attempt to send the event from there and not worry about the other flow.

This way, you can map all the events that you want to receive in Google Ads. However, before that, we need to ensure that conversion actions for them are in place.

GAds Enhanced Conversions Setting

Enhanced conversions indicate sending the first-party customer data for conversions that were already captured. This would help in identifying cross-device attributions, etc.. It will not generate extra conversions, but it helps Google Ads attribute conversions more clearly with these first-party identifiers.

You can set it to Google Tag or Google Ads API, and based on the setting, we will try to send these enhanced conversions.

Make sure to have the same option selected in the Google Ads dashboard for enhanced conversions, else this won't work.

Once all the above fields are configured, you can click on "Save & Deploy." Congratulations, the basic setup is now complete. Let's proceed to the next section to explore additional configuration options.