Count configurator quote requests as Microsoft Ads conversions
Last updated
For the person who looks after the maker’s website and Microsoft Advertising. About 20 minutes, with Google Tag Manager on the site. Last checked against Microsoft’s help pages: October 2026 (see the sources).
What you get: each quote request sent from the configurator on your site is counted by your Microsoft Ads UET tag as a submit_lead_form event, with the build’s price as its revenue when it has one, and a conversion goal turns it into conversions. The deals you win can be uploaded later by their Microsoft click id. How many conversions you see depends on your traffic, your visitors’ consent choices and their browsers; nothing here changes how your ads perform.
Before you start
- Google Tag Manager on the website, with permission to edit and publish it.
- Microsoft Advertising: permission to manage UET tags and conversion goals.
- The maker has turned on Count ad conversions, and the configurator is embedded with the code from the admin (as in step 1 of the Google Ads guide). That code also passes the
msclkid; check that auto-tagging of the Microsoft Click ID is on in the account’s settings.
1. The UET tag
In Microsoft Advertising: Tools → Conversion tracking → UET tag.
- The site already loads it (Microsoft’s UET Tag Helper browser extension shows it): note the tag’s ID, nothing to add.
- Not yet: Create UET tag, name it after the website, and copy its Tag ID (a number). You will add it in step 4.
2. Create the conversion goal
- Tools → Conversion tracking → Conversion goals → Create.
- Choose Website, goal category Submit lead form, type Event. Name: Configurator quote request.
- Event: Action Equals
submit_lead_form. Leave Category, Label and Value empty (the configurator does not send them; a goal that asks for them would never match). - Revenue: Conversion value may vary, with a default value of your choice (used when a build is priced only in the maker’s quote).
- Count: Unique (one per click, as for leads). Choose the UET tag from step 1, and save.
3. Import the container (skip if you already did)
Download studio-gtm-container.json
In Tag Manager: Admin → Import Container → choose the file → workspace Existing → Merge → Rename conflicting tags, triggers and variables → Confirm. Never choose Overwrite. Details: Google Ads guide, step 3.
4. Fill in the variables
| Variable | Value |
|---|---|
Studio - Configurator address | The configurator’s address from its embed code, e.g. https://acme-cabins.example.com (https, no slash at the end). Already set if you did another guide. |
Studio - Microsoft UET tag ID | Only if the UET tag is not on the site yet: the Tag ID from step 1. |
5. Turn the tags on, test, publish
- Unpause
Studio - Microsoft Ads lead. It fires onstudio:quote_submittedand sendsuetq.push('event', 'submit_lead_form', {revenue_value, currency}). - Only if the UET tag was not on the site: also unpause
Studio - Microsoft UET base code(Microsoft’s standard snippet, all pages). - Consent: set the tags’ consent settings as your other marketing tags are set.
- Preview, open the page, send a quote request (write “TEST” in the notes): Tag Assistant shows the tag fired, and the UET Tag Helper shows a
submit_lead_formevent. Mark the test request Lost in the maker’s admin. - Submit → Publish. The goal’s status in Microsoft Advertising updates once real conversions arrive; it can take several hours.
Won deals: upload them by Microsoft click id
Shortcut: the won deals page makes the upload file from “Download my data” for you, in your browser (the file stays on your computer).
- Create a second goal: Conversion goals → Create → Offline conversions, named e.g. Configurator won deal. Microsoft asks to wait about two hours after creating it before the first upload.
- In the maker’s admin, Download my data:
enquiries.csvhas anmsclkidcolumn next tocreated_at,status,totalandcurrency. - In Microsoft Advertising, open the offline conversions upload page (Tools → Conversion tracking → Offline conversions) and download its template.
- For each request that became a sale and has an
msclkid: Microsoft Click ID =msclkid, Conversion Name = the goal’s exact name, Conversion Time = when the deal was won (with its time zone; after the click), Conversion Value = the sale’s value, Conversion Currency =currency. - Upload within 90 days of the click. A file can upload “successfully” and still not count click ids that are too old or belong to another account: check the goal’s numbers afterwards.
What this does not do
- It does not change your ads, bids or budgets, and it does not promise more conversions: it counts what already happens.
- Visitors who decline ad cookies, or whose browser blocks the UET tag, are not counted by the tag; the won-deal upload still works for requests that carry an
msclkid. - The event carries no name, email or phone.