Library·SOP·Analytics
Choose a Google Analytics 4 (GA4) setup for one WordPress site, check what your business already has, and write the next steps in order. This guide helps you plan the setup; the linked guides explain how to make each change.
Last reviewed: · Editorial review
Clarity, structure and references reviewed in this version. This is not a test in a live account.
Choose a Google Analytics 4 (GA4) setup for one WordPress site, check what your business already has, and write the next steps in order. This guide helps you plan the setup; the linked guides explain how to make each change.
This SOP covers:
This does not cover:
Google Analytics 4 (GA4) is where you read website visit reports. A GA4 property is the report space for your website; its web data stream is the feed from that website into the property. Google Tag Manager (GTM) is a separate place to manage tracking tags: small pieces of code that send website activity to Google or another service. A Web container groups tags for one website. Site Kit connects these services to WordPress and can place their code on your site.
Create a note named Website setup note where your team keeps website handoffs. Add Website URL, Method, Analytics details, Tag Manager details, Current site tags, Next steps, and Questions for owner as headings. Leave a detail blank if you cannot confirm it; write a question instead of guessing.
Write the website URL in Website setup note. If the team only needs GA4 reports about website visits, choose Site Kit Analytics. This is the simpler WordPress route, and Google recommends Site Kit's Analytics module when using Site Kit. Choose Google Tag Manager if the business already manages other website tags there or its tracking owner wants one place for those tags. Do not choose Tag Manager only because you want GA4. If neither choice fits, ask the website owner what the business already uses. Record your choice under Method.
Both methods need the right GA4 property and website stream. The stream's Measurement ID starts with G- and identifies where GA4 receives website activity.
Ask the Analytics owner which business account, GA4 property and website stream belong to this site. Record their names and the stream's full G- Measurement ID under Analytics details. If the team chose Site Kit Analytics, Site Kit can also create a missing account, property or stream during its setup. If you cannot confirm the intended destination, add the owner's name or question under Questions for owner.
Add the applicable next task to Next steps. Use the substeps to choose the task for your method and current setup.
If Method is Site Kit Analytics and the account, property or stream still needs to be selected or created, write Set up the Analytics destination with Site Kit in Next steps. The official Site Kit Analytics guide explains that setup when you begin it.
If Method is Google Tag Manager, an Analytics account exists, and it has no GA4 property for this site, write Create a GA4 property and Web stream in Next steps and follow the linked SOP when you begin that work.
If the GTM method is chosen and the right property already exists but has no website stream, write Ask the Analytics owner to add a Web stream to the existing property in Next steps. Use Google's instructions when you begin that work; do not create another property.
If the GTM method is chosen but the business has no Analytics account, or you cannot tell which account or property belongs to this site, write the exact question for the Analytics owner. Wait for the owner to confirm the account before choosing a property or adding a tag.
Use this milestone only when Method says Google Tag Manager. If you chose Site Kit Analytics, go to milestone 4 to record that route.
Ask the tracking owner which Tag Manager account belongs to this business. Write the correct account and Web container, or the appropriate setup task, under Tag Manager details and Next steps.
If the tracking owner confirms the business has no Tag Manager account, write Create a Tag Manager account and first Web container in Next steps. Follow the linked SOP when you begin that work.
If the business has the right Tag Manager account but no Web container for this website, write Create a Web container in the existing account in Next steps. Follow the linked SOP when you begin that work.
If a Web container for this website already exists, write its account name, container name and complete GTM- ID under Tag Manager details. Add Use the existing container in Next steps; do not plan to create another one.
Open Google Tag Assistant, enter the website's homepage URL and select Connect. Then choose the substep that matches the account and container details in your note. Record what Tag Assistant finds; this guide only updates your plan.
If step 3.1 identified the existing Web container and Tag Assistant shows the same full GTM- ID, record Container already installed under Current site tags.
If step 3.1 identified a Web container but Tag Assistant shows a different GTM- ID, record the detected ID and ask the tracking owner whether to keep or replace it. Do not plan another installation until the owner decides.
If the note has no selected GTM- ID yet because a container still needs to be created, record what Tag Assistant detects. If it finds any GTM ID, ask the owner whether that is the company's existing container to reuse before planning a new one. If it finds none, keep the create-container task followed by an installation task in Next steps.
If the selected Web container exists in the confirmed Tag Manager account and Tag Assistant connects successfully but finds no GTM container on the site, write Install the selected container with Site Kit under Next steps. Follow the linked SOP when you begin that work. If Tag Assistant finds a different container, keep the owner question from the previous substep instead of planning another installation.
This guide ends with a plan. Use the linked procedures when you are ready to make the changes.
If Method says Site Kit Analytics, write one next task in the note: Connect the confirmed Analytics account, property and stream with Site Kit. If the destination is missing, write Set up or create the Analytics destination with Site Kit instead. Follow the official Site Kit guide when you begin setup. If Site Kit is already connected to the matching property and stream, record Reuse the current Site Kit connection. If a different Analytics tag or property is active, ask the owner which one should receive website data before planning code changes.
If Method says Google Tag Manager, build the Next steps list from the substeps below. Write down only the tasks that are still missing; this guide does not perform them.
First, list the Analytics destination task from step 2.2 if it is missing. If the property and stream already exist, record their names and the G- ID as confirmed instead.
Next, list the Tag Manager account/container task from step 3.1 if one is needed. If the right Web container exists, record its full GTM- ID for reuse.
After choosing the container, list the WordPress installation step only if Tag Assistant connected successfully and found no GTM container at all. If it found the selected ID, record that the container is already installed. If it found a different ID or could not connect, keep the owner question from step 3.2 and do not list another installation yet.
If the owner confirms that an existing tag already sends data to the chosen G- stream, record Reuse the current GA4 setup and do not add another tag. If a different property is receiving data, record the owner's decision before planning a change.
If no existing tag sends data to the chosen stream, list GA4 through Tag Manager last only after the owner confirms the site's privacy and consent setup and there is no conflicting Analytics tag. Follow the linked SOP when you begin that work. If any detail is unclear, put the owner's question next instead.
