IronMile Studio

Count configurator quote requests as Meta Pixel leads

Last updated

For the person who looks after the maker’s website and Meta ads. About 15 minutes, with Google Tag Manager on the site. Last checked against Meta’s help pages: October 2026 (Meta renames menus now and then; see the sources).

What you get: each quote request sent from the configurator on your site is recorded by your Meta Pixel as a standard Lead event, with the build’s price as its value when it has one, and the quote request’s id as the event id. Your Meta campaigns can then report and optimise on those leads. How many you see depends on your traffic, your visitors’ consent choices and their browsers; nothing here changes how your ads perform.

Before you start

1. Is the Meta Pixel already on the site?

Not sure? Meta’s free Meta Pixel Helper browser extension shows whether a page loads a Pixel, and which one.

2. Import the container (skip if you already did for Google Ads)

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. Everything it adds is named Studio - …; the ad tags arrive paused. Details: Google Ads guide, step 3.

3. Fill in the variables

VariableValue
Studio - Configurator addressThe 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 the Google Ads guide.
Studio - Meta Pixel IDOnly if the Pixel is not on the site yet: the ID from step 1.

4. Turn the tags on

  1. Unpause Studio - Meta Pixel Lead (tick it in the Tags list → Unpause). It fires on studio:quote_submitted and sends fbq('track', 'Lead', {value, currency}, {eventID}).
  2. Only if the Pixel was not on the site: also unpause Studio - Meta Pixel base code (Meta’s standard snippet, all pages).
  3. Consent: set the tags’ consent settings as your other marketing tags are set, so they follow your cookie banner.

5. Test, then publish

  1. In Tag Manager, Preview, and open the page with the configurator.
  2. In Meta Events Manager, open the Pixel → Test events, and enter the same page’s address to test browser events.
  3. Send a quote request in the configurator (write “TEST” in the notes). In Tag Assistant, studio:quote_submitted shows Studio - Meta Pixel Lead fired; in Test events, a Lead event appears within a minute or so.
  4. Mark the test request Lost in the maker’s admin, then in Tag Manager Submit → Publish.

6. Use the leads in Meta Ads Manager

For campaigns that should bring quote requests, choose a Leads objective with the conversion location Website, the Pixel, and the Lead event. Meta’s own reporting shows the leads it attributes to each ad. If the site already counts other leads (a contact form) as Lead, you can tell them apart with a custom conversion; the configurator’s Lead events come from the configurator’s page.

Won deals

Unlike Google Ads and Microsoft Ads, Meta has no click id that the configurator keeps, so there is no won-deal upload by click id here. Meta can match offline sales by the buyer’s email or phone, but that means sending buyers’ personal details to Meta: that is the maker’s decision, under their own privacy policy, and this kit does not do it. The utm_ values that come with each quote request (if your Meta ads’ links carry them) show which campaign it came from, in the admin and in “Download my data”.

What this does not do

Sources