Count ad conversions
Last updated
If you run Google Ads, Microsoft Ads or Meta ads, your configurator can tell your website when a buyer configures, opens AR or sends a quote request, so your own tag manager counts it as a conversion. We add no tracking code to the configurator: your website’s tags and your cookie banner stay in charge.
Ask us to switch it on. It is included in Starter and Pro, and we switch it on for your configurator when you ask. It counts conversions once the configurator sits on your own website. Once it is on, your admin’s Install tab has a Count ad conversions section with the codes to use. Connecting the events to your tags is a job for your web person: send them this page.
How it works
When ad tracking is on, the configurator does two things. It adds no tags or cookies of its own; your website’s tag manager and its consent banner stay in charge.
- Events to your page. Inside an iframe on your site, the configurator sends
window.postMessageevents to your page. Your own Google Tag Manager, gtag or UET tag turns them into conversions. - Click ids on the quote request. The ad click ids and utm values in your page’s address (
gclid,gbraid,wbraid,msclkid,utm_source,utm_medium,utm_campaign,utm_term,utm_content) are kept for the browsing session only, without cookies, and stored with the quote request. They appear in the webhook and APIattributionfield and in the “Download my data” CSV, for offline conversion import.
For the click ids to reach the configurator, use the embed codes from the admin’s Count ad conversions section. They include a few inline lines that copy those values from your page’s address onto the configurator’s; nothing is loaded from us.
Step-by-step guides
- Google Ads, with a ready-made Google Tag Manager container to import
- Meta (Facebook and Instagram ads)
- Microsoft Ads
- Won deals to Google Ads and Microsoft Ads: upload files made from “Download my data”, in your browser
The events
type | When | Also carries |
|---|---|---|
studio:view | The configurator has loaded | product |
studio:configure | The buyer changes an option (at most once every 10 seconds) | product, value, currency |
studio:ar_open | The buyer opens the view in their room (AR) | product |
studio:quote_open | The buyer opens the quote request form | product, value, currency |
studio:quote_submitted | The quote request was received | product, value, currency, enquiry_id |
value is the price shown to the buyer, in the currency’s units; it is left out when the build is priced only in the maker’s quote. enquiry_id is the quote request’s id: use it as the conversion’s transaction id so a conversion is never counted twice. The events never carry the buyer’s name, email or phone. Check event.origin against the configurator’s address before you trust a message.
Google Tag Manager
Add a Custom HTML tag firing on All Pages (or the page with the configurator), with your configurator’s address in place of the origin:
<script>
window.addEventListener('message', function (e) {
if (e.origin !== 'https://your-configurator-address') return;
var d = e.data;
if (!d || typeof d.type !== 'string' || d.type.indexOf('studio:') !== 0) return;
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({ event: d.type, studio_product: d.product, studio_value: d.value, studio_currency: d.currency, studio_enquiry_id: d.enquiry_id });
});
</script>
Then create a Custom Event trigger named studio:quote_submitted, and a Google Ads Conversion Tracking tag (or a Microsoft Ads UET tag) on that trigger, with Data Layer Variables for studio_value (conversion value), studio_currency (currency code) and studio_enquiry_id (transaction id).
gtag.js or Microsoft UET without Tag Manager
<script>
window.addEventListener('message', function (e) {
if (e.origin !== 'https://your-configurator-address' || !e.data || e.data.type !== 'studio:quote_submitted') return;
var d = e.data;
// Google Ads (gtag.js already on the page): your conversion's send_to from Google Ads
if (window.gtag) gtag('event', 'conversion', { send_to: 'AW-XXXXXXXXX/YYYYYYYYYYYY', value: d.value, currency: d.currency, transaction_id: d.enquiry_id });
// Microsoft Ads (UET tag already on the page)
window.uetq = window.uetq || [];
window.uetq.push('event', 'submit_lead_form', { revenue_value: d.value, currency: d.currency });
});
</script>
Offline conversion import (won deals)
High-value leads are best counted when the deal is won. In the admin, “Download my data” gives enquiries.csv with the gclid and msclkid columns; for the requests that became sales, upload the click id, the time of the sale and its value in Google Ads (Goals → Conversions → Uploads) or Microsoft Ads (Conversion goals → Offline conversions). The webhook and the API carry the same ids, so a CRM can do the upload itself.
The full-page configurator (opened by a link or button, not in an iframe) sends no events, as there is no page of yours around it; the click ids still travel with the quote request when the link carries them.