What does Google Tag Manager actually manage?

GTM manages tags and the rules that control when they run. A tag is a small piece of code used to collect or send information. Google's introduction describes support for Google Analytics, Google Ads and third-party tags. Google's product overview.

Learn the vocabulary through one task

Consider a hypothetical home cleaning company measuring quote requests. Use the following table as a planning worksheet. Replace the example with the action that matters on your own website.

The underlying definitions come from Google's explanation of containers, triggers and variables. Before creating anything, explain your proposed measurement using those four rows.

GTM versus Google Analytics

Use GTM to manage the sending of measurement information. Use Google Analytics to examine the information received. HubSpot illustrates tags sending information to Analytics and other destinations in its introductory tutorial.

Write down the report you want before configuring the tag. For help choosing a meaningful outcome, use the small business KPI guide. Avoid a first project whose only goal is collecting more numbers.

What should you prepare before creating an account?

Prepare an inventory of existing measurement code and assign an owner. Ask your website provider which analytics and advertising tools are already installed. Record where each setup is managed and who can change it.

Google says migrated tags can run alongside tags managed outside GTM. Treat the move as a planned handover between installations. Google's migration guidance.

• Choose a business-controlled Google login.
• Identify the person who can change the website.
• Confirm access to the intended analytics or advertising account.
• List existing tags and their purposes.
• Choose one action to measure first.
• Name the person responsible for testing and publishing.

Specify the boundary around customer information. For this introductory project, keep names, email addresses and message contents out of the event plan. If the website offers consent choices, ask the implementer to document how those choices affect measurement.

My recommendation is to keep the initial scope small enough to review in one sitting. A written brief should identify the page, the action, the destination and the expected result. Leave advanced purchase tracking for a separate brief when you can describe its requirements clearly.

How do you install the GTM container?

Work through account creation, container installation, tag configuration and verification in that order. These are separate stages in Google's getting-started navigation. Google's setup sequence.

1. Name the account after the business

Google generally recommends one account per organization, which can administer more than one website or app. Account organization guidance. Use a name your colleagues will recognize and document who owns access.

2. Create a container for the website

Select the web option for a website container and give it a recognizable name. HubSpot's setup walkthrough describes account details and the choice of target platform. Account creation walkthrough. Follow the field labels in your current interface rather than relying on an old screenshot's button colors.

3. Place the supplied snippets

The first snippet goes high in the page's <head>. The second goes immediately after the opening <body> tag. These locations are described in HubSpot's installation instructions.

Google specifies adding the two snippets to each page. Google's installation requirement. Ask your implementer to check service, contact and confirmation pages as well as the homepage.

Use the code supplied by your own container. If your website platform provides a dedicated integration field, have the implementer confirm what that field expects. Record the chosen installation method before adding another plugin or another copy of the code.

4. Give the developer a checkable brief

Install this website container across the relevant page templates. First list the existing measurement tags and propose how each will be retained or replaced. Our first acceptance test is a successfully submitted quote request reaching the intended analytics destination.

Request evidence of the checked pages and the selected account. Keep that evidence with the brief so a future colleague can understand the setup without reconstructing it.

How should your first event and advertising measurement work?

Define success before choosing the trigger. An event is the action you want to record, such as a completed enquiry. Describe exactly what the visitor must finish for that event to count.

Hypothetical example: a local repair service

Suppose a repair service wants to measure requests for a callback. Write separate entries for opening the form, pressing its button and successfully submitting it. Ask the implementer to show which signal confirms the completed submission.

1. Choose the outcome: an accepted callback request.
2. Identify the confirmation signal with the website developer.
3. Configure the tag and its trigger around that signal.
4. Check that an incomplete form does not produce the success event.
5. Verify the resulting event in the intended destination.

GTM can manage Google Analytics and Google Ads tags. Google's supported examples. For the Analytics connection, follow the current Google tag setup route linked from Google's introduction and use the identifier from your own account.

For advertising, write which event will count as a conversion, meaning the outcome you want the campaign to produce. Review the Google Ads duplicate conversion guide when checking whether the same outcome is being counted through more than one route.

Plan campaign naming separately. The UTM parameter guide is a useful next step for organizing campaign links. Agree on names before different team members start creating their own versions.

How do you know the setup is ready to publish?

Require a recorded test with an expected and an observed result. Google's introduction points to verification and publishing as a distinct setup stage. Verification in Google's workflow.

• Visit the page without submitting anything.
• Try an incomplete submission.
• Complete one valid test submission.
• Click an unrelated button.
• Repeat the intended journey on a phone.
• Check each consent choice against the agreed measurement plan.

For every test, record whether the event appeared where expected. Ask for an explanation of unexpected events before publishing. Do not approve the setup solely because a tag appears in the management interface.

If Preview, the testing view, will not connect, use the GTM Preview diagnosis guide. Resolve that problem before treating the test as complete.

After publishing, repeat the same customer journey. Keep a short record of what changed and who checked it. If the result differs from the approved test, pause further additions and investigate that difference first.

Once collection is working, use the conversion rate optimization guide to plan improvements to the enquiry journey. Keep implementation checks and business improvement decisions as separate tasks in your project notes.

What should you receive at the end of the first week?

Aim for one verified measurement and a usable handover. Request the container name, installation method, event definition, destination and test results. Include the name of the person responsible for future changes.

My suggested schedule is to inventory the current setup first, install the container next, then spend the remaining time configuring and testing one event. Do not promise a time saving before comparing actual work. Record the time spent on setup, testing and corrections.