What is a GTM container builder?

A GTM container builder generates a Google Tag Manager container as a JSON file you import into GTM, with the tags, triggers, and variables already wired together. TagManagerBuilder does this for free: you pick your website platform, tracking tools, and events, enter your IDs, and download the file.

Which website platforms does TagManagerBuilder support?

It supports WooCommerce, WordPress, BigCommerce for WordPress, and GoHighLevel websites and funnels. Each platform has its own event list, such as Purchase and Add to Cart for stores, or form, survey, and booking conversions for lead-generation sites.

Can I use Google Tag Manager with GoHighLevel?

Yes. Paste your GTM snippet into the Tracking Code (Header) setting of your GoHighLevel website or funnel, then import a container built with this tool. It adds GA4, Google Ads, Meta, TikTok, and Pinterest tags for GoHighLevel form submissions, survey completions, calendar bookings, and thank-you page views.

How do I track GoHighLevel form submissions with GTM?

GoHighLevel forms load in iframes, which GTM's built-in form trigger cannot see. The generated container includes a bridge tag that listens for the message HighLevel's embed sends on submit and pushes a dataLayer event, plus a thank-you page trigger as a dependable fallback. Confirm the event once in GTM Preview after importing.

Which tracking tools can I set up?

GA4, Google Ads, Meta Pixel, TikTok Pixel, Pinterest Tag, LinkedIn Insight Tag, Microsoft UET, and X Pixel, in any combination. Each tool gets the tags and triggers that match the events you select.

Is TagManagerBuilder really free?

Yes. Every platform, tool, and event is free with no account, no trial, and no locked tiers. The site is supported by display advertising, and paid done-for-you services are optional.

Do I need to know how to code?

No. You choose options in a wizard and import the downloaded file into Google Tag Manager. Some events on WooCommerce, BigCommerce, and WordPress need your site to push a dataLayer event, and each guide says exactly which ones.

Is TagManagerBuilder affiliated with Google, HighLevel, WooCommerce, or BigCommerce?

No. It is an independent tool and is not affiliated with, endorsed by, or sponsored by Google, HighLevel (GoHighLevel), Automattic, WooCommerce, or BigCommerce. Product names are used only to describe what each guide covers.

Meta Conversions API (CAPI)

Quick answer: Meta CAPI sends conversion events (Purchase, Lead, etc.) directly from your server to Meta, alongside the browser-based Pixel this wizard already generates. It recovers events lost to ad blockers, Safari ITP, and iOS App Tracking Transparency, and improves match quality using hashed customer data. It requires a Meta access token and either backend code or a server-side tagging setup - a browser-only GTM container can't do this alone.

Build my container →

The Meta Pixel this wizard generates fires from the visitor's browser. That works, but browsers increasingly block or restrict it - ad blockers strip the Pixel outright, Safari's Intelligent Tracking Prevention limits third-party cookies, and iOS App Tracking Transparency cuts off tracking for users who decline. CAPI sends the same events from your server instead, which none of those browser-side restrictions can touch.

How this relates to server-side tracking (GTM Server Container)

There are two separate paths to Meta CAPI, and it's worth knowing which one you're choosing:

Route it through a GTM server container - if you've already set up server-side tracking (see that guide), Meta publishes an official "Conversions API" tag template in GTM's Server Container template gallery. Add it as a tag in your server container and it sends events to Meta using the same data your client-side container already collects.
Send it directly from your backend - a WooCommerce order-completed hook (or similar) calls Meta's Conversions API endpoint directly with the order and customer data, with no GTM server container involved at all. This needs custom PHP code or a dedicated integration plugin.

What you need either way

A Meta Business Manager account with access to the Pixel/dataset you're sending events to
A CAPI access token, generated in Events Manager under your Pixel's Settings > Conversions API
Hashed (SHA-256) customer data - email, phone, or similar - for match quality, the same as Enhanced Conversions on the Google Ads side

The part people get wrong: deduplication

If both the browser Pixel and CAPI send the same Purchase event, Meta will count it twice unless you deduplicate. Both events need a matching event_id parameter - Meta uses that to recognize them as the same conversion and count it once. This is a common setup mistake worth checking for specifically in Meta's Events Manager test tool after going live.

Frequently asked questions

Does this wizard generate CAPI for me?

No - this wizard builds the browser-side Meta Pixel tag. CAPI is a separate server-to-server integration that needs either a GTM server container with Meta's official tag template, or custom backend code.

Do I still need the Pixel if I set up CAPI?

Yes - Meta recommends running both together, not CAPI alone. The Pixel captures rich browser-side behavioral data; CAPI recovers what the Pixel misses. Combined, with proper deduplication, they give the most complete picture.

Will this fix my declining ROAS from iOS tracking changes?

It helps meaningfully, since it recovers events lost to ATT opt-outs and ad blockers, but it won't recover data for users who've genuinely opted out of tracking - that data loss is a policy choice, not a technical gap CAPI can close entirely.