Google Analytics, Tag Manager, the Meta Pixel and the consent banner
Connect Google Analytics, Google Tag Manager and the Meta Pixel by id, and choose whether your website asks visitors before anything loads. Global Privacy Control is always honored.
Your website can send page views to Google Analytics, run a Google Tag Manager container and fire the Meta Pixel without you pasting any code. You give us the id; we write the tag on every public page. A typo is refused when you save instead of breaking a page, and when the consent banner is on, nothing loads until the visitor says yes.
Connect your tags
- Go to Website and scroll to Measurement and privacy.
- Paste the ids you have. You do not need all three.
- Google Analytics measurement id,
G-XXXXXXXXXX: in Google Analytics, Admin, Data streams, open your web stream. - Google Tag Manager container id,
GTM-XXXXXXX: at the top of your container in Tag Manager. - Meta Pixel id, a number: in Meta Events Manager, your pixel (dataset).
- Google Analytics measurement id,
- Choose how the consent banner behaves (below).
- Click Save measurement settings.
Saving refreshes your storefront's cache, so the tags reach every public page within moments. There is nothing to publish from the builder.
If you had pasted the Google tag, the Tag Manager snippet or the pixel code into Custom code before, remove it from there once the id is saved here, or the tag loads twice.
The consent banner
Ask first (recommended). A small banner in the corner of your website asks the visitor before anything loads. Your tags, the Meta Pixel and anything in Custom code wait for a yes; a no keeps them off. The answer is remembered on that browser, and a Privacy choices link at the bottom of every page brings the banner back so the visitor can change it. Taking back a yes reloads the page so nothing keeps running.
Load right away, no banner. The tags load on every visit, and your website's privacy policy names them and says so. Use this only if you know your state allows it.
In both modes, a browser that sends the Global Privacy Control signal is treated as a no, without a banner: your tags, the pixel and your Custom code stay off for that visitor. California, Colorado, Connecticut and other states require a business to honor that signal as an opt-out of sale and sharing, so it is not a setting.
Our own AI assistant chat on your website is part of the site, not a tracker: it does not follow visitors across the web and is never held back by the banner.
What is sent
- Google Analytics: the standard Google tag with Consent Mode set to granted at the moment it loads (it loads only after a yes, or at once when the banner is off). Google records page views and in-page navigation itself.
- Google Tag Manager: the standard container snippet. Your own triggers and tags live in Tag Manager; use its History Change trigger for in-page navigation.
- Meta Pixel: the standard pixel with a
PageViewon every page, including in-page navigation between pages of your site.
Nothing loads inside the visual builder's live preview, so your analytics never count your own edits.
Leads, calls and texts
Your tags also hear about the moments that matter, so you can count them as conversions (in Google Analytics, mark the event as a key event; in Meta, the standard events are already conversions):
| When | Google Analytics and Tag Manager | Meta Pixel |
|---|---|---|
| A shopper sends a form that creates a lead (a question on a vehicle page, the contact form, the financing pre-qualification, the trade-in form) | generate_lead, with form_name (vehicle_inquiry, contact, financing or trade_in) and vehicle_stock when the form was about a car | Lead |
| A shopper taps a phone link anywhere on your site | click_to_call | Contact |
| A shopper taps a text-message link | click_to_text | Contact |
They follow the same consent as the tags: sent only after a yes (or at once when the banner is off), and never for a visitor whose browser sends Global Privacy Control. They never carry the shopper's name, email address or phone number. A form a spam bot filled in is not counted. In Tag Manager, each one is a Custom Event trigger with that event name.
If your Tag Manager container already sends its events to the same Google Analytics property, fill in only the Tag Manager box: with both boxes filled, each lead and tap reaches that property twice.
FAQ
Do I still need Custom code?
Only for snippets we do not have a field for: a chat widget, another vendor's pixel, a site-verification tag. It lives under Advanced and follows the same consent banner.
Where do visitors change their answer?
Privacy choices at the bottom of every page, next to the copyright line. The link is there only while the banner is on and there is something to hold back.
Why do I see fewer visitors than before?
With the banner on, only visitors who said yes are counted, and visitors whose browser sends Global Privacy Control are never counted in either mode. That is the trade-off the banner makes.
Who can edit this?
Only an Owner or a Manager, the same as Custom code.