Blog / Google Ads

How to Set Up Google Ads Conversion Tracking With AI (Prompts Included)

The exact walkthrough I used on two of my own sites this week, including the gotcha that had quietly broken one of them.

If you run Google Ads without conversion tracking, Google is spending your money blind. It can't tell which searches turned into leads, so it can't do more of what works, and neither can you.

This week I set up Google Ads conversion tracking on two of my own sites with an AI agent driving the browser. Here's the walkthrough, the prompts I'd use, the problem that had been silently breaking one of them, and what you still need to check with your own eyes.

What is conversion tracking, in plain English?

A conversion is the thing you want a visitor to do. For most service businesses, that's a call or a filled-out form. Conversion tracking is how Google Ads finds out it happened, and which ad and keyword sent that person.

A few terms you'll see below:

  • Conversion action. The record in Google Ads that says "a lead form submit counts, and here's what it's worth."
  • Google Tag Manager. A free Google tool that holds your tracking code in one place, so you don't edit your website every time something changes.
  • Google tag. The base Google code that loads on every page. Google's Tag Manager help says that if a Google tag loads on every page, you don't also need a separate Conversion Linker tag, which is the piece that remembers which ad click brought the visitor in.
  • Conversion tag. The tag that tells Google Ads "a lead just happened." It only fires when its trigger says so.
  • Trigger. The rule for when a tag fires. Here, it's a custom event called generate_lead.
  • generate_lead. One of Google's recommended event names, meant for when someone submits a form or a request for information. Using the standard name keeps your Ads and Analytics speaking the same language.

What the agent needs before it starts

I used Claude in Chrome, which works inside my own Chrome browser. Anthropic's help article lists it on paid plans as of this writing. ChatGPT Work's cloud browser can do similar work. Either way, get three things ready.

You're signed in. Log into Google Ads and Tag Manager yourself, in the browser the agent uses. Never paste passwords into the chat.

You know where the form lives. The page URL, and whether the form is built into your site or embedded from a form tool or CRM.

You have test details. A test name, an email you control and a 555 phone number for the test lead, so you can find it and delete it afterward.

How to set up Google Ads conversion tracking, step by step

  1. Step 1

    Create the conversion action

    In Google Ads, create a website conversion action for lead form submits. Google's web conversions guide covers the setup options, including one that sends the tag setup straight to Tag Manager. Pick a lead category such as Submit lead form (see Google's conversion categories), count one conversion per click, and note the conversion ID and label.

  2. Step 2

    Add the Google tag in Tag Manager

    One Google tag, firing on all pages, with your Google Ads tag ID. If one already exists, the agent should find it and leave it alone, not create a second.

  3. Step 3

    Add the conversion tag

    A Google Ads Conversion Tracking tag with your conversion ID and label, firing on a Custom Event trigger named generate_lead. Google's custom event trigger page explains how a dataLayer push with that event name fires the tag.

  4. Step 4

    Make sure the form actually sends generate_lead

    Something on the page has to push generate_lead into the dataLayer when the form succeeds. This is where most setups break, and it's where mine did. More below.

  5. Step 5

    Preview and test

    Tag Manager's Preview mode connects your site to Tag Assistant so you can see which tags fired, and in what order. Submit a test lead. The conversion tag should fire once, after the submit, never on page load.

  6. Step 6

    Publish and check the live page

    Publish the container, load the live page, and confirm the new tags are there. In Google Ads, a new action usually starts as Unverified and moves to Recording once real conversions come in.

The iframe gotcha that broke my tracking

On both of my sites, the lead form isn't really on the page. It's embedded in an iframe, which is a window that shows content from another domain. Your page displays the form, but the submit happens over on the form tool's side.

So the page never "sees" the submit. Tag Manager's built-in form trigger can't hear it, and nothing fires. Everything looks set up. Conversions just never show.

The fix was a small listener script. Many embedded form tools send a message to the parent page when a form is submitted, using a browser feature called postMessage, which lets a page and an iframe inside it talk across domains. The listener waits for the form's "submitted" message and then pushes generate_lead into the dataLayer. From there, the trigger and tag do their jobs.

The part I didn't expect: while checking the second site, the agent noticed it had no listener at all. The tags were fine. Nothing was ever telling them a lead happened. That's why conversions had never recorded on that site. It took an agent reading the page code to spot it, and a person to understand why it mattered.

Check your form tool's documentation for the exact message it sends. They differ by tool, and the listener should only accept messages from your form tool's domain.

The prompts I'd use

These assume you're already signed in and the agent works in your browser. Swap in your details where you see brackets.

Prompt: audit before touching anything

I'm signed in to Google Ads and Google Tag Manager in this browser. Goal: find out whether conversion tracking for lead form submits on [website URL] works today. Do not change anything yet.

Check: what conversion actions exist in Google Ads and their status; what tags, triggers and variables exist in the Tag Manager container [container name]; whether the live page [form page URL] loads that container; whether the form is on the page or inside an iframe from another domain; and whether anything on the page pushes generate_lead (or any event) into the dataLayer when the form is submitted.

Done looks like: a short report of what exists, what's missing, and what you would change, in order. Stop and wait for my approval before making any change.

Prompt: build the tracking

Using the plan I approved, set up lead tracking. In Google Ads, create one website conversion action named [Lead form submit], category Submit lead form, counting one conversion per click, value [value or none]. In Tag Manager workspace [name]: make sure exactly one Google tag fires on all pages with tag ID [your tag ID]; create a Google Ads Conversion Tracking tag with the new conversion ID and label; create a Custom Event trigger with the event name generate_lead and attach it to that tag.

Don't create duplicates of anything that already exists. Don't publish. When finished, list every item you created or changed by its exact name, then stop.

Prompt: the iframe listener

The form on [page URL] is embedded in an iframe from [form tool domain]. Find this form tool's official documentation on the message it sends to the parent page when a form is submitted, and give me the link. Then write a small listener for a Custom HTML tag in Tag Manager that only accepts messages from [form tool domain], recognizes the submit message, and pushes the event generate_lead into the dataLayer once per submit.

Explain in plain English what each part does. Add it to the workspace with an All Pages trigger, but do not publish. Stop and show me.

Prompt: test it

Start Tag Manager Preview on [page URL]. Submit the form once using the name [Test Lead], the email [your test email] and the phone [314-555-0100]. Report: did generate_lead appear in the dataLayer, did the Google Ads conversion tag fire exactly once, and did it fire after the submit rather than on page load.

If anything fails, tell me what you see and stop. If everything passes, ask me before you publish the container.

What to check yourself

The agent does the clicking. These checks are yours, because they're the ones that cost money when they're wrong.

  • One lead, one conversion. Confirm the tag fires once per submit. Double-firing inflates your numbers and teaches Google the wrong lesson.
  • No double counting. If you also import a GA4 key event for the same form into Google Ads, make sure only one of the two is set as primary. Otherwise every lead counts twice.
  • The live site, not just Preview. After publishing, load the real page and confirm the version you published is the one running.
  • Calls too. Forms are only half the story for most service businesses. Phone calls need their own tracking, and I explain why in missed calls cost more than bad ads.
  • Clean up. Delete the test lead from your CRM or inbox so nobody calls a fake customer.

How long until Google Ads shows Recording?

Not instantly. Google's Tag Assistant troubleshooting guide says actions you verify in a debug session update after roughly 30 minutes, and the status only changes to Recording once the page actually receives conversions. Verified actions with no new leads can show No recent conversions for a while and still be fine.

What matters is that your test lead fired the tag correctly in Preview and on the live page. That's your proof. The status catches up.

If real leads have come in through the form and the status still hasn't moved, something is broken. Start with the audit prompt again.

Do this before you spend another dollar on ads

Skipping conversion tracking is one of the most common mistakes I see, and it made my list of Google Ads mistakes. Without it, you're judging ads by clicks, and clicks don't pay the bills.

The agent made this faster. It did the tedious clicking through Tag Manager screens, and it found the missing listener by reading the page code. But somebody still had to know what the setup should look like, decide what counts as a lead, and confirm the test actually recorded. That part doesn't go away.

Once tracking works, the next step is the campaign itself, which I walk through in build a local Google Ads campaign with AI.

Alex Lamy

Alex Lamy16 years in marketing, from radio to agencies to running his own shop. Now he runs a team of AI agents that do the marketing for St. Louis small businesses. You talk to him, and he checks every piece.

Want this handled for you?

$499 a month, flat. My AI agents produce it, I check every piece, and we meet weekly. Month-to-month, and you own everything. Want a reference first? I'll connect you with someone I did similar work for.

Book a 30-minute call