How to set up Google Tag Manager: step-by-step GTM setup

You configure Google Tag Manager after the container is already installed on the site. Below is a practical base set for owners in the US, Canada and the UK who need reliable ads and analytics data for a Google Ads campaign audit without constant developer tickets.

A minimal working set usually includes:

• a Google Analytics tag (GA4 / Google tag);
• a Conversion Linker tag when the container does not already load a Google tag site-wide or a separate Linker is otherwise needed;
• a 15-second engagement signal;
• a conversion tag (thank-you page, form submit or key click).

How to add Google Analytics while setting up GTM

Open your GTM container. Left menu: Tags → New. Then:

1. Trigger: All Pages (built-in; no need to create it). Name the tag clearly, for example GA4 or Google tag.
2. Tag configuration: choose Google tag / Google Analytics: GA4 Configuration from the type list (wording varies slightly by UI).
3. Measurement ID: paste the GA4 Measurement ID (G-XXXX) from Admin → Data streams. Save the field or a settings variable.
4. Publish: Submit → Publish. Draft tags do not fire for real users.

How to add Meta (Facebook) Pixel in Google Tag Manager

Many accounts also need Meta Pixel for remarketing. Trigger: All Pages again. Name: Meta Pixel. Tag type: Custom → Custom HTML. Paste the base pixel code from Meta Events Manager. Save. Always check Preview so you do not double-fire a pixel that was already hard-coded in the theme.

How I design a GTM container

I treat the container as a system of agreements, not a folder of tags. For each item I record purpose, firing condition, consent dependency and business owner, then enforce one naming structure. That lets me read the container without opening every tag and separate production setup from temporary tests.

Architecture notes are in Google’s docs on Tag Manager.

How to add the Conversion Linker tag in GTM

Conversion Linker stores ad click data (for example in first-party _gcl_* cookies) so conversion tags can attribute later conversions. Google’s Tag Manager help also states that if the container already loads a Google tag on every page, a separate Conversion Linker tag is not required (Google Ads / Floodlight tags load a Google tag first). Use a dedicated Linker only when you need the tag type itself or do not yet have a site-wide Google tag:

1. Tags → New.
2. Trigger: All Pages.
3. Name, for example Conversion Linker.
4. Configuration: Conversion Linker (under recommended / advertising tags).
5. Almost no extra fields: Save, then publish with the rest of the container.

How to track that someone stayed on the site for a set time

A common setup: fire when a user has been on the page for at least 15 seconds. This is an engagement signal, not a sale. Steps:

1. In Triggers create “15 seconds”:
   • type: Timer;
   • interval: 15000 ms;
   • limit: leave blank or set 1 if you want a single fire;
   • enable when: always true, for example Page URL matches RegEx .*.
2. In Tags create “GA4: engaged 15s”:
   • trigger: the timer you just made;
   • configuration: GA4 Event (or Google tag event, depending on UI);
   • event name: for example engaged_15s;
   • advanced settings: fire once per page, otherwise a long-open tab floods analytics;
   • save and publish.

Once pageviews and engagement fire cleanly, the next useful step is a real business action (thank-you page, form submit, “Order” click) so Google Ads optimises on outcomes, not only visits.

How to set up a conversion in Google Tag Manager

The simplest path: after checkout the user lands on a thank-you page. Trigger on that URL. Fire a GA4 event (and/or a Google Ads conversion tag if you implement it in GTM).

Often you must capture a button click or a form submit instead.

For a click:

1. Trigger → New → name it “Click Order”.
2. Type: Click – All Elements (not only links). Buttons are often not <a> tags.
3. Some clicks, not all clicks: otherwise the tag fires on every click on the page.
4. Condition from built-in click variables: Click Text is usually safest. Paste the button label exactly as in the HTML, for example “order now”. Class and ID often repeat across buttons.
5. Multiple buttons: use one Click Text condition with matches RegEx, for example ^(order now|book a consult)$. Separate condition rows are combined with AND, not OR.

Copy the button text from the HTML, including spaces and case. If the string does not match, the tag will not fire and analytics will stay empty.

Then create the event tag:

1. Name: “GA4: click order”.
2. Type: GA4 Event.
3. Event name: for example click_order.
4. Optional parameters: button_text, page_path.
5. Trigger: Click Order. Save, Preview, publish.

In GA4 mark the event as a key event / conversion if that is the business signal. If the same action also feeds Google Ads, verify arrival in DebugView or Tag Assistant, not only a green fire in GTM Preview.

Takeaways on setting up Google Tag Manager

1. This is only a base layer. GTM can track scroll depth, form submits, purchases, phone clicks, add-to-cart and pop-ups. The event map should follow the business, not a maximalist checklist.
2. Container and tag docs live in Google Tag Manager help and related posts (what GTM is, Consent Mode, enhanced conversions).
3. GA4 metrics later drive bidding and remarketing. Without events, automation optimises noise, and $ is spent blind.
4. After the one-time container install, most changes do not need a developer. Preview and versions make rollback possible. Developers are mainly needed at install time or for a proper dataLayer.

Related articles

ROAS Formula: Calculate It in Two Minutes and See Where It BreaksROAS in Google Ads: Formula, Break Even Point, and a Good ROASROAS vs ROI vs ACoS: Three Numbers People Confuse and What It Costs