How to validate events being sent to Google Ads (Gtag) destination – Twilio Support

Objective

This guide outlines steps for you to validate events that are being sent to your Google Ads (Gtag) Destination through Segment.

Product

Twilio Segment

Environment

Segment Console

Procedure

To figure out if an event is flagged for conversion, follow these steps:

Confirm that the events mapped to a Google Ads conversion are being sent in device-mode while using the Segment Analytics.js library. To do this:
1. Go to Connections > Sources in your workspace and choose your Source.
2. Go to the Debugger tab.
3. Click on an event and look at the Raw view to make sure the events have a library name of analytics.js. There should be a snippet of code that looks like this:
```
     "library": {
       "name": "analytics.js",
```
Verify that the Google Conversion ID in your Segment workspace is correct.
Find your ad online and click it. This will redirect you to your website.
Open the Network tab in your browser and make sure the Preserve log checkbox is checked and All is selected. Keep this Network tab and webpage open.
Go to the Settings tab for your Gtag destination in Segment on a new webpage and choose Click Conversions to look at the mapped track() events and make sure the events are mapped to the correct Conversion Label.

The conversion label is unique to each conversion action and is configured per mapping. You can find the conversion label in the event snippet. The event snippet should have send_to: 'AW-123456789/AbC-D_efG-h12_34-567'. The conversion label is the part after the ‘/’.

  ![Edit Settings](../../images/conversion-settings.png)

Go back to your website and trigger the event mapped to the conversion. For example, as shown in the image above, it would be Order Completed.
Go to the Network tab in your browser and enter the Conversion Label linked to the event you triggered in the Filter field.
See if the value for the ct_cookie_present changed to true. If true, it means that Google Ads counts the event as a conversion.

Google Ads considers an event as a conversion when the user arrives to your website as a result of an Ad click. The Google SDK is responsible for checking if the user came from an Ad click and sets the parameter ct_cookie_present to true. Without clicking through an ad, Google Ads doesn’t reflect the conversion because this information is missing in the network requests.

Additional Information

More details on our Google Ads (Gtag) destination can be found below:

Google Ads (Gtag) Destination