> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cometly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up Google Enhanced Conversions for Leads

> Fix Cometly conversions that Google Ads rejects or cannot match to an ad click by setting up Google Enhanced Conversions for Leads and the Google tag.

You mapped your events in Cometly's [Google Conversion API](https://docs.cometly.com/guides/conversion-api/google.md) (the server-side connection that sends your tracked leads and sales to Google Ads), but the conversions do not show up in Google Ads. Or they arrive, and Google does not credit them to any ad.

The usual cause is the Google Ads account, not the mapping. Google rejects the uploads until you accept its customer data terms and turn on Google Enhanced Conversions for Leads. It can then only match a conversion to an ad click when the conversion carries the Google click ID (the **gclid**), or when your Google tag has already captured the same email or phone on your form. The steps below fix each of these in turn.

## Why this matters

Google relies on user data and click identifiers to match conversions back to ads. If this is not configured correctly, conversions may not be attributed, which affects optimization and reporting.

This setup gives you:

* More accurate attribution in Google Ads
* Better campaign optimization
* Reliable tracking when cookies are limited

## What is Enhanced Conversions for Leads?

Enhanced Conversions for Leads lets Cometly send **offline conversions** (such as purchases or qualified leads) directly to Google Ads using **hashed user data** such as email or phone.

Cometly sends these conversions server-to-server using the Google Ads API.

## How matching works

Google connects conversions back to ad clicks in two steps.

### 1. The Google tag captures user data

* A visitor clicks a Google ad (the URL includes a **gclid**).
* They fill out a form on your site.
* The **Google tag** captures their email or phone.
* Google links the three together: `email/phone → gclid → ad click`.

### 2. Cometly sends the conversion

Cometly sends the conversion to Google. It includes:

* The **gclid** (if available)
* The **hashed email and/or phone**

### How Google matches

Google prioritizes matching like this:

1. **gclid** (best match)
2. **Email or phone match** (requires the Google tag setup)
3. **No match** (still accepted but not attributed)

> [!TIP]
>
> **Key takeaway:** if your Google tag is not capturing the email on form submissions, email-based matching will not work.

## Make sure Cometly conversions reach Google

### Step 1: Accept the customer data terms in Google Ads

* Go to **Google Ads → Admin → Customer data terms**.
* Review and accept the terms.

> [!WARNING]
>
> If the terms are not accepted, conversions will fail.

### Step 2: Enable Enhanced Conversions for Leads

* Go to **Google Ads → Goals → Conversions → Settings**.
* Turn on **Enhanced conversions for leads**.

> [!WARNING]
>
> If it is disabled, Google will reject conversions.

### Step 3: Create the correct conversion action

* Go to **Conversions** in Google Ads.
* Create or verify a conversion action with:
  * Type: **Import**
  * Source: **Upload from clicks** (`UPLOAD_CLICKS`)

Cometly only lists enabled conversion actions of this type. You map the action in Cometly in step 7 below.

### Step 4: Enable auto-tagging

* Go to **Google Ads → Admin → Account settings**.
* Enable **Tag the URL that people click through from my ad**.

This makes sure the **gclid** is added to your URLs.

### Step 5: Configure the Google tag (critical step)

This is the most important step for matching. Without it, Google cannot connect your conversions back to ad clicks using email or phone.

#### What you need

* A **Google tag (gtag.js)** or **Google Tag Manager (GTM)** installed on your website
* Access to your website or tag manager to configure tracking
* A form that collects at least:
  * **Email** (recommended)
  * **Phone number** (optional, but helps improve match rates)

#### What you are setting up

When someone submits a form on your website, you need to make sure that:

* The **Google tag receives the user's email or phone**.
* This happens **at the moment the form is submitted**.
* Google stores this data and links it to the original ad click.

This creates the connection that lets Cometly's conversion upload match later.

#### What "capturing user data" means

Capturing user data means:

* Passing the **email and/or phone number from your form** into the Google tag
* Doing this **on the form submission event**, not just on page load
* Making sure the data is tied to the same session in which the user arrived from the ad

> [!NOTE]
>
> Google handles hashing automatically. You do not need to hash anything yourself.

#### Two ways to set this up

**Option 1: Google tag (gtag.js)**

* Configure your existing Google tag to receive user data.
* Trigger it when a form is submitted.
* Pass the form's email (and optionally phone) into the tag.

**Option 2: Google Tag Manager (recommended for most users)**

* Create a **form submission trigger**.
* Create or update a tag to send user-provided data.
* Map your form fields (email, phone) to the correct variables.
* Fire the tag when the form is successfully submitted.

#### Where this needs to happen

You must capture the data on:

* Lead forms
* Contact forms
* Demo booking forms
* Any form where a user becomes a lead

> [!WARNING]
>
> This should happen **on the actual form submission**, not on a thank-you page, unless the data is still accessible there.

#### How to know it is working

After setup, verify that:

* The Google tag fires on form submission.
* The tag includes the **email (and/or phone)** as user-provided data.
* The data matches exactly what the user entered.

You can use Google Tag Assistant or GTM Preview mode to confirm this.

> [!WARNING]
>
> If this is not set up, email-based matching will fail.

### Step 6: Install the Cometly pixel

* [Install the Cometly pixel](https://docs.cometly.com/getting-started/install-pixel.md) on your website.
* Make sure your forms capture:
  * **Email**
  * **Phone** (optional)
* The pixel captures:
  * User data
  * The gclid from the URL

### Step 7: Map the conversion in Cometly

In Cometly, open **Events Manager** and click the **Conversion API** tab. Expand **Google**, select your **Google Ads account**, and map the Google conversion action from step 3 to a Cometly event. The full walkthrough is in [Google Conversion API](https://docs.cometly.com/guides/conversion-api/google.md).

For each mapping, choose one of these options in the **Rule** column.

#### Only send attributed events (recommended)

Cometly only sends the conversion if:

* A **gclid** exists.
* The conversion is attributed to Google.
* The click and the attribution point to the Google Ads account you are mapping.

This is best for accuracy and for avoiding duplicates.

#### Send all events

Cometly sends all conversions regardless of attribution. A conversion without a gclid is sent with the hashed email or phone only.

Use this if:

* Your Google tag is properly capturing the email.
* You want Google to optimize using more data.

> [!WARNING]
>
> **Risks:**
>
> * Can send conversions to multiple accounts
> * May inflate Google reporting
> * Requires the Google tag setup to work correctly

## Troubleshooting

### Conversions not showing

| Issue | Fix |
| - | - |
| No conversions at all | Accept the customer data terms |
| Uploads rejected | Enable Enhanced Conversions for Leads |
| Wrong conversion type | Use `UPLOAD_CLICKS` |
| No attribution | Install the Google tag properly |
| No gclid | Enable auto-tagging |
| Delayed data | Wait up to 24 hours |

### Pro tips

* Always enable **auto-tagging** to maximize match rates.
* Use **Only send attributed events** unless you fully understand **Send all events**.
* Make sure your **Google tag captures the email on form submission**.
* More user data (email and phone) improves matching.

## Confirm Google Enhanced Conversions for Leads is working

In Cometly, open **Events Manager** and click the **Conversion API** tab: the **Google** row shows the **Active** badge. In Google Ads, open **Goals > Conversions > Summary** and check the conversion action you mapped. New conversions appear there once Google has processed them, and conversions that carry a gclid or a captured email or phone are now credited to your ads.

## Frequently asked questions

### How long do Cometly conversions take to show in Google Ads?

Cometly sends each conversion to Google about 15 minutes after the event is tracked. Google can then take up to 12 hours to process and display it. Give a new setup a full day before you start troubleshooting.

### Why do Cometly and Google Ads show different conversion numbers?

The two platforms date conversions differently: Google Ads reports a conversion on the date of the ad click, while Cometly reports it on the date the person converted. Google Ads can also take 12 to 48 hours to fully process conversions sent through the API. See [Why Cometly and Google Ads conversion numbers differ](https://docs.cometly.com/support/troubleshooting/conversion-api/google-ads-conversion-differences.md).

### Can Cometly send conversions to more than one Google Ads account?

Yes. If you have more than one Google Ads account connected to the Space (your Cometly workspace), select each account in turn on the **Conversion API** tab and map it separately. Keep in mind that a row set to **Send all events** sends every occurrence of that event to its account, so the same conversion can reach several accounts.

## Next steps

* [Map your Google conversion actions with the Google Conversion API](https://docs.cometly.com/guides/conversion-api/google.md)
* [Understand why Cometly and Google Ads conversion numbers differ](https://docs.cometly.com/support/troubleshooting/conversion-api/google-ads-conversion-differences.md)
* [Install the Cometly pixel](https://docs.cometly.com/getting-started/install-pixel.md)
* [Exclude an event from the Conversion API](https://docs.cometly.com/guides/conversion-api/exclude-an-event.md)

Still have questions or need a hand? We're happy to help. Reach our team at [support@cometly.com](mailto:support@cometly.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.