A common situation we see with marketing teams is this:
You’ve created a Google Analytics 4 (GA4) property, your website already uses Google Tag Manager (GTM), but you don’t personally have access to the website code or the GTM container.
So how do you get GA4 installed?
The good news is that you usually do not need access to your website code.
If Google Tag Manager is already installed correctly, your developer or whoever manages GTM can add GA4 through the existing GTM container.
Here’s the simplest way to handle it.
What You Need Before You Start
You need your GA4 Measurement ID.
It will look something like:
G-XXXXXXXXXX
You can find it in GA4 under:
Admin → Data Streams → Web → Measurement ID
This identifies the GA4 web data stream that should receive data from your website.
If Google Tag Manager Is Already Installed
If GTM is already running on your website, you generally don’t need another website code change.
Send your developer or GTM administrator your GA4 Measurement ID and ask them to configure the Google tag in the existing GTM container.
You can send them this:
“Please add our GA4 Measurement ID to the existing Google Tag Manager container using a Google tag. Configure it to fire on all pages, test the implementation, publish the GTM container, and confirm that GA4 is receiving data.”
For an experienced GTM developer, that should provide enough direction.
What Your Developer Will Do
Your developer will typically:
- Open the appropriate Google Tag Manager container.
- Create a Google tag using your GA4 Measurement ID.
- Configure it to fire across the appropriate pages, typically all pages for the base GA4 implementation.
- Use GTM Preview mode to test the implementation.
- Publish the GTM container.
- Verify that data is reaching GA4.
You can use GA4 Realtime to verify that activity is reaching the property.
Keep in mind that standard GA4 reports can take longer to populate, so don’t assume something is broken simply because you don’t immediately see data in every report.
Don’t Accidentally Install GA4 Twice
This is particularly important with WordPress websites.
Before adding GA4 through GTM, make sure GA4 isn’t already being loaded another way.
For example, GA4 could already be installed through:
- Google Site Kit
- another WordPress analytics plugin
- your WordPress theme
- code inserted directly into the website header
- another tag-management plugin
- an existing Google tag inside GTM
Installing GA4 more than once can potentially result in duplicate pageviews or events and unreliable analytics data.
The goal isn’t simply to make GA4 fire.
The goal is to make sure GA4 fires correctly.
Do You Need WordPress Access?
Usually, no.
If Google Tag Manager is already installed correctly on the website, your developer can manage the analytics implementation through GTM without giving you access to WordPress.
It helps to think about the different systems separately:
WordPress or your CMS manages the website.
Google Tag Manager manages the deployment of many analytics and marketing tags.
Google Analytics 4 collects and reports your analytics data.
You may not need to personally manage all three.
However, there is an important distinction between managing the implementation and owning access to your analytics systems.
Your Organization Should Have Access to GA4 and GTM
Even if a developer or agency manages your analytics implementation, your organization should ideally retain appropriate access to both GA4 and Google Tag Manager.
This is something I see businesses overlook.
A developer sets everything up. Years later, the developer leaves, the agency relationship ends, or nobody remembers which Google account owns the GTM container.
Suddenly, making a simple tracking change becomes a much bigger project.
A better model is:
Your organization owns GA4 and GTM. Your developers and agencies receive the access they need to manage the implementation.
That way your analytics infrastructure stays with your organization even when vendors or employees change.
What Should You Ask Your Developer?
If you’re in this situation, you can send your developer something as simple as:
“Please make sure our GA4 property is implemented through our existing Google Tag Manager container and is receiving data. Also, please make sure my Google account has access to our GA4 property and GTM container.”
You don’t necessarily need access to edit the website itself.
You just want to make sure:
GA4 is implemented correctly → data is flowing → your organization has access to GA4 and GTM.
Getting Data Into GA4 Is Only the First Step
This is where many analytics implementations stop.
Someone installs the tag.
GA4 starts showing users and sessions.
Everyone assumes analytics is working.
But seeing data in GA4 doesn’t necessarily mean the data is reliable.
You can still have problems such as:
- missing or duplicate events
- incorrect key events
- unexpected
(not set)values - campaign tracking problems
- broken UTM parameters
- ecommerce tracking issues
- excessive Direct traffic
- configuration changes that affect reporting
- tags that stop firing after website changes
Marketing teams often don’t discover these issues until someone notices that a report suddenly looks wrong.
By then, you may have already lost days or weeks of useful data.
From Analytics Implementation to Analytics Confidence
Installing GA4 answers one question:
Are we collecting data?
A more important ongoing question is:
Can we trust the data we’re collecting?
That requires periodically checking your analytics configuration, monitoring important signals, and identifying changes before they turn into larger data-quality problems.
This becomes especially important when multiple people are involved in the website—developers, agencies, marketers, analytics teams, and outside vendors.
Changes happen.
Your measurement system needs a way to catch them.
Automatically Monitor Your GA4 Implementation
If you don’t want to manually check your GA4 implementation every week, GA Auditor by Optizent can help.
GA Auditor audits your GA4 configuration and data quality and continuously monitors your analytics implementation for changes and potential issues.
Instead of discovering a tracking problem weeks later while looking at a report, you can identify problems much closer to when they occur.
Audit your GA4 implementation and start monitoring your analytics data with GA Auditor.