How to Track Google Ads Conversions in Google Tag Manager in 2026

Step 1: Create the conversion action in Google Ads

Before touching GTM, you need to create the conversion action inside Google Ads. This is where your Conversion ID and Conversion Label live.

1. Go to Goals in Google Ads. In the left nav, click Goals, then Conversions, then Summary.
2. Click the blue + button to create a new conversion action.
3. Select “Website” as the conversion source.
4. Choose your conversion category. For an ecommerce purchase, select Purchase. For a lead form, select Submit lead form. Match this as close as possible to what actually happened. If prompted, select to create a conversion “Manually with code”.
5. Name your conversion action clearly. Use a name that maps to the event, such as Purchase or Lead Form Submit. This shows up in your Google Ads reporting, so keep it clean.
6. Set the value. If order values vary, select Use different values for each conversion. This lets you pass dynamic revenue data from GTM later.
7. Save and continue. On the next screen, choose Use Google Tag Manager.
8. Copy your Conversion ID and Conversion Label. You will need both in GTM. They look like this: ID is a number such as 123456789, Label is a string such as AbCdEfGhIjKlMnOp.

Do not close this screen until you have noted both values.

Step 2: Create GTM variables for your conversion data

Variables store the dynamic values your tag needs: conversion value, transaction ID, and currency. Create these before building your tag.

Variable 1: DLV – transaction_id

• Variable type: Data Layer Variable
• Data Layer Variable Name: ecommerce.transaction_id
• Name it: DLV – transaction_id

Variable 2: DLV – value

• Variable type: Data Layer Variable
• Data Layer Variable Name: ecommerce.value
• Name it: DLV – value

Variable 3: DLV – currency

• Variable type: Data Layer Variable
• Data Layer Variable Name: ecommerce.currency
• Name it: DLV – currency

The naming prefix DLV stands for Data Layer Variable. This prefix makes it immediately clear where the variable is pulling its value from when you are scanning a long variable list in GTM.

⚠️If your site pushes transaction data using a different key structure (for example, some platforms use transactionId or revenue instead of the GA4-style ecommerce object), adjust the Data Layer Variable Name to match what your site actually pushes. Check your data layer in GTM Preview before assuming.

Step 3: Create the trigger

The trigger controls when your Google Ads tag fires. If you already have a GA4 purchase tag using a Custom Event trigger on the purchase event, reuse that same trigger. There is no need to create a duplicate.

If you do not have one yet, create it now:

1. In GTM, go to Triggers and click New.
2. Select Custom Event as the trigger type.
3. Set the Event Name to purchase (This name may vary depending on your website but this is the standard).
4. Leave it set to fire on All Custom Events unless you need to restrict it further.
5. Name the trigger: CE – purchase

The prefix CE stands for Custom Event. Consistent prefixes mean you can filter your trigger list instantly and know exactly what type of trigger you are looking at without opening it.

Step 4: Build the Google Ads conversion tag

1. In GTM, go to Tags and click New.
2. Click Tag Configuration and select Google Ads Conversion Tracking.
3. Fill in the fields as follows:

4. Under Triggering, select CE – purchase.
5. Name the tag: Google Ads – Purchase
6. Save the tag.

The tag name format Google Ads – [Conversion Action] makes it easy to scan your tag list and immediately know which platform and which event each tag handles. If you add more conversion types later (such as a lead form), they follow the same pattern: Google Ads – Lead Form Submit.

Step 5: Verify in GTM Preview mode

1. Click Preview in the top right of GTM.
2. Enter your site URL and click Connect.
3. Complete a test purchase on your site (use a test order or a low-value product in a dev environment).
4. In the GTM debug panel, click on the purchase event in the left sidebar.
5. Under the Tags tab, confirm Google Ads – Purchase appears under Tags Fired.
6. Click the tag to expand it and confirm the conversion value, order ID, and currency are all populated correctly. If any show as undefined, your data layer variable name does not match what the site is pushing. Check the Data Layer tab in Preview to see the exact key structure.

Do not publish until every field is populated with real values, not undefined.

Step 6: Publish and verify in Google Ads

1. Once Preview mode confirms the tag is firing correctly with populated values, click Submit in GTM.
2. Add a meaningful version name such as Add Google Ads purchase conversion tag.
3. Click Publish.
4. In Google Ads, go to Goals > Conversions > Summary. Your conversion action status will initially show as Unverified. After a real conversion fires, it will move to Recording conversions. This can take up to 24 hours.

For faster verification, use the Google Tag Assistant Chrome extension on a live test transaction to confirm the gtag hit is being sent with the correct conversion ID and label.

What your data layer push should look like

For the variables you created in Step 2 to have data to read, your site needs to push a purchase event to the data layer on the order confirmation page. A standard push looks like this:

window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
  event: 'purchase',
  ecommerce: {
    transaction_id: 'T-12345',
    value: 49.99,
    currency: 'USD'
  }
});

This push needs to happen before GTM fires, which means it should sit in the page source of the confirmation page, not loaded asynchronously after GTM. If your platform handles this through a plugin (WooCommerce, Shopify, etc.), confirm that the data layer push includes these exact keys and that it fires on the order confirmation page specifically.

Common mistakes

Using a Page View trigger instead of a Custom Event trigger. Some guides tell you to fire your conversion tag on the thank-you page URL. This works, but it breaks down the moment your URL structure changes, and it can double-count if someone refreshes the confirmation page. The Custom Event trigger on purchase is more reliable because it fires only when the transaction is explicitly pushed to the data layer.

Hardcoding the conversion value. If you set a fixed value in the tag instead of pulling from the data layer, every conversion will report the same revenue in Google Ads. That makes your ROAS data meaningless. Always pass dynamic value.

Forgetting the Order ID field. Leaving Order ID blank means Google Ads cannot deduplicate conversions. If the same order is counted twice (page refresh, back-button, etc.), your conversion numbers inflate. Pass the transaction ID.

Using the AW- prefix in the Conversion ID field. GTM’s Google Ads Conversion Tracking tag type expects just the numeric ID, not the full AW-123456789 string. Paste only the numbers.

Not checking data layer variable values in Preview. Publishing before verifying that your variables are populated with real values is the most common reason conversion tracking silently fails. Always open the tag in Preview, expand it, and confirm every field shows an actual value.