IronMile Studio

Count configurator quote requests as Google Ads conversions

Last updated

For the person who looks after the maker’s website and Google Ads. About 20 minutes, with Google Tag Manager already on the site. Last checked against Google’s help pages: October 2026 (Google renames menus now and then; the sources below have the current wording).

What you get: each quote request sent from the configurator on your site is counted as a conversion in Google Ads, with the build’s price as its value and the quote request’s id as the transaction id, so it is never counted twice. Later, the deals you actually win can be uploaded too. How many conversions you see depends on your traffic, your visitors’ consent choices and their browsers; nothing here changes how your ads perform.

Configurator(iframe on your page)Request a quote ✓ event Your pageGoogle Tag Managerstudio:quote_submitted tag Google Adsconversionvalue · transaction id
The configurator never loads Google’s code itself: your page’s own Tag Manager, under your own cookie banner, does the counting.

Before you start

1. Use the embed code that passes the ad click id

In the maker’s admin, Install → Count ad conversions → Inside your page: copy that code and use it on the page, instead of the plain embed code. Its few inline lines copy gclid, gbraid, wbraid and the utm_ values from your page’s address onto the configurator, so the quote request remembers which ad click it came from. Nothing is loaded from us.

The admin's Install tab, section Count ad conversions, with the code for inside your page and for a button
The admin’s Install tab (sample address). Use the code under Inside your page.

Note the configurator’s address in that code (the data-src, here https://acme-cabins.example.com/): you need it in step 4, without the slash at the end.

2. Create the conversion action in Google Ads

  1. In Google Ads: Goals → Conversions → Summary → + Create conversion action (or New conversion action).
  2. Choose Website (conversions on a website) and enter the website’s address.
  3. Choose to add the conversion action manually (not the automatic “from page loads or clicks” option).
  4. Goal and action: Submit lead form. Name: Configurator quote request.
  5. Value: Use different values for each conversion, with a default value of your choice (used when a build is priced only in the maker’s quote and has no online price).
  6. Count: One (one conversion per click, as for leads). Keep the other settings or adjust them to how you work.
  7. Save, then on the tag set-up screen choose Use Google Tag Manager. Copy the Conversion ID (digits) and the Conversion label.

Whether this action counts towards bidding (primary or secondary) is your choice in the action’s settings; start it as secondary if you want to watch the numbers before bidding on them.

3. Import the ready-made container into Tag Manager

Download studio-gtm-container.json

  1. In Tag Manager: Admin → Import Container.
  2. Choose container file: the file you downloaded.
  3. Workspace: Existing (your default workspace) or a new one if you prefer to review it apart.
  4. Import option: Merge → Rename conflicting tags, triggers and variables. Never choose Overwrite: it would replace your container.
  5. Confirm (Add to workspace). Tag Manager shows what it adds: 7 tags, 5 triggers and 9 variables, all named Studio - … or DLV - studio_…. Nothing goes live until you submit and publish.
Tag Manager's Tags list after the import: the Listener on All Pages, and the Google Ads, Meta and Microsoft tags paused
After the import (a test container): only Studio - Listener is active; the ad tags show the paused sign.
ImportedWhat it doesState
Studio - ListenerListens for the configurator’s events, only from its own address, and puts them in the data layer (studio:view, studio:configure, studio:ar_open, studio:quote_open, studio:quote_submitted). Sends nothing anywhere.On
Studio - Google Ads conversionThe conversion, on studio:quote_submitted: value, currency, transaction id.Paused
Studio - Conversion LinkerGoogle’s Conversion Linker on all pages (keeps the ad click for the conversion).Paused
Studio - Meta Pixel …, Studio - Microsoft …For Meta and Microsoft Ads (their own guides). Leave them paused if you don’t use them.Paused

4. Fill in three variables

In Variables → User-Defined Variables, open each and replace the value:

VariableValue
Studio - Configurator addressThe configurator’s address from step 1, e.g. https://acme-cabins.example.com (https, no path, no slash at the end). If the configurator has two addresses, put both, separated by a comma.
Studio - Google Ads conversion IDThe Conversion ID from step 2 (digits only, without AW-).
Studio - Google Ads conversion labelThe Conversion label from step 2.

5. Turn the two Google tags on

The imported Studio - Google Ads conversion tag: conversion ID and label from the Studio variables, value, transaction id and currency from the configurator's event
The imported conversion tag, still paused: value, transaction id and currency come from the configurator’s event.
  1. In Tags, tick Studio - Google Ads conversion in the list and choose Unpause (or open the tag, ⋮ menu → Unpause).
  2. The Conversion Linker: if your container already has a Conversion Linker on All Pages, delete Studio - Conversion Linker; otherwise unpause it.
  3. The Google tag. If the conversion tag shows Cannot detect if the Google tag is in your container, check that the container has a Google Tag for this Google Ads account (its Tag ID is AW- followed by your Conversion ID), firing on Initialization - All Pages. A site already advertising on Google through Tag Manager usually has it. If not: New → Google Tag → Tag ID AW-… → trigger Initialization - All Pages → Save. (The notice also appears while the ID is a variable, as in this container.)
  4. Consent: if your site uses a consent banner with Google’s consent mode, the Google Ads tag follows it as your other Google tags do; nothing to change.

6. Test before publishing

  1. In Tag Manager, Preview, and open the page with the configurator.
  2. In the Tag Assistant window you should see studio:view when the configurator loads, then studio:configure when you change an option.
  3. Send a quote request in the configurator (use your own name and write “TEST” in the notes). studio:quote_submitted appears, and under it Tags Fired shows Studio - Google Ads conversion, with the value and the transaction id in its details.
  4. The test request reaches the maker’s inbox like any other: mark it Lost there so it is not followed up.

No events in the preview? Check that the page uses the code from step 1 (an iframe, not a link), and that Studio - Configurator address matches the address in that code exactly, starting with https and without a slash at the end.

7. Publish

Submit → name the version (“IronMile Studio configurator conversions”) → Publish. In Google Ads, the conversion action’s status moves from Unverified to Recording conversions once real conversions arrive; Google says this can take a few hours, and up to 48 hours.

Won deals: upload them from “Download my data”

Shortcut: the won deals page makes the upload file from “Download my data” for you, in your browser (the file stays on your computer). The steps below are what it does.

A quote request is a lead; a sale is worth more to Google Ads’ bidding. When quote requests turn into sales, you can import them as a second conversion action. The click id that came with each request makes it possible.

  1. In Google Ads, create a second conversion action: Goals → Conversions → + Create conversion action → Import → CRMs, files or other data sources → track conversions from clicks. Name it, e.g. Configurator won deal.
  2. In the maker’s admin, Download my data. The zip has enquiries.csv, with the columns gclid, gbraid, wbraid, msclkid and utm_… next to id, created_at, status, total and currency.
  3. In Google Ads, Goals → Conversions → Uploads, and download Google’s template (the columns can change; the template is always right).
  4. For each request that became a sale and has a gclid, fill in one row:
    Template columnFrom
    Google Click IDgclid
    Conversion Nameexactly the action’s name, e.g. Configurator won deal
    Conversion Timewhen the deal was won, e.g. 2026-10-20 14:30:00, with the time zone in the template’s parameter row (or +0000 at the end). It must be after the click.
    Conversion Valuethe sale’s value (the total column is the price the buyer configured; use the signed amount if it differs)
    Conversion Currencycurrency
  5. Upload the file in Uploads. Google keeps a click id for 90 days: upload won deals within that time, ideally every week or two.

Rows with only gbraid or wbraid (some iPhone clicks) are not accepted by the classic file template; Google’s Data Manager or the API take them. A CRM connected by the webhook gets the same ids in each quote request’s attribution and can do the upload itself.

What this does not do

Sources