The reason your GA4 numbers look inflated is almost always the same: two things are firing the same Measurement ID. A plugin adds the Google tag, and a snippet you pasted into your theme header adds it again, so every pageview is counted twice. Fixing it takes three moves: pick exactly one delivery method, remove what you had before, then verify with Tag Assistant that the tag fires once.
This guide walks through creating your GA4 account and web data stream, compares the four install routes (Site Kit, a GA4 plugin, a hardcoded Google tag, and Google Tag Manager), and ends each route with a one-tag verification test. Nothing here covers report reading or BigQuery exports, the goal is clean collection first.
The path in 6 steps
The steps of this page, in order.
-
01 Create the property Set up your GA4 account and web data stream, then copy the G-XXXXXXXXXX Measurement ID.
-
02 Pick one route Choose Site Kit, a GA4 plugin, a hardcoded Google tag, or GTM, not two of them.
-
03 Remove the old tag Deactivate the previous plugin or delete the header snippet so nothing double-fires.
-
04 Place the new tag Follow the exact placement steps for the route you chose.
-
05 Verify a single fire Use Tag Assistant and GA4 Realtime to confirm one tag fire per page load.
-
06 Filter and consent Exclude logged-in admins and editors, and check that your banner talks to Consent Mode.
01 / 11
How do I create a GA4 property and get my Measurement ID?
You create one account, one property, one web data stream, and Google hands you a Measurement ID that starts with G-.
Start at analytics.google.com: create an account for your business, then a property inside it, then a Web data stream for your domain. The stream is what generates the G-XXXXXXXXXX Measurement ID, that ID is the only thing every install route below needs, so copy it into a note before you close the screen. If you later paste a different ID into a plugin than the one in your theme, you are looking at two properties, not one.
Leave Enhanced Measurement switched on unless you have a reason not to: it collects pageviews, scrolls, outbound clicks, and video plays without extra code. One property, one stream, one ID, keep that chain intact from here on.
-
Create the account
Sign in to Google Analytics, click Admin, then Create account. Name it after your business and set your data-sharing preferences.
-
Create the property
Inside the account, choose Create property. Set your reporting time zone and currency, then answer the industry and business-size questions.
-
Create the Web data stream
Choose Web, enter your site URL and a stream name such as your domain. The stream appears under Data streams.
-
Review Enhanced Measurement
Leave it on to capture pageviews, scrolls, outbound clicks, and video plays. You can switch individual events off later.
-
Copy the Measurement ID
In the Web stream details, find the Measurement ID that starts with G-. Save it where you keep site credentials, you will type it into one install method only.
Going further
How GA4 differs
Concept
Why GA4 counts events, not sessions
GA4 is event based rather than session based, so every pageview, click, and scroll is an event, which is why a second tag doubles counts so visibly.
In Universal Analytics, the pageview was the unit that sessions were built around. GA4 flipped that: everything you collect is an event, and a pageview is simply one event named page_view.
Scrolls, outbound clicks, video plays, and form interactions are their own events too. A session in GA4 is derived from events that share a user and fall within a 30-minute window of inactivity, not from a pageview chain.
This matters for troubleshooting. A second GA4 tag does not add sessions in a subtle way; it duplicates every event sent, so page_view counts can look close to double. That is a tracking problem, not a traffic spike.
- Confirm event-based logicRead Google's developer documentation on how GA4 events and sessions are defined before you treat a duplicated page_view as a traffic change.
- Watch only one event per actionA single pageview should produce one page_view event, not two. Counts that match 2x are a signal to check tags.
02 / 11
Which install method should I use on WordPress?
Pick the route that matches what you want to run later, and choose only one.
Think in terms of what you want to run later. Site Kit, Google's own connector, keeps a free, official link between your site and your GA4 property, but it won't manage an ads stack. A GA4 plugin puts a settings screen and basic dashboards inside wp-admin, which suits owners who dislike hopping between tabs.
The hardcoded Google tag fits a child theme and no plugin appetite; Google Tag Manager (GTM), a container that fires tags from one snippet, fits anyone adding ads, pixels or event tags later. Whichever you choose, switch the other three off, that is what keeps counting single.
Install method: cost, effort, and who it fits
| Method | Typical cost | Setup effort | Choose this if | What it blocks later |
|---|---|---|---|---|
| Site Kit (Google connector) | Free | Low, connect your Google account | You want an official, free link and no ads stack | Complex ad, pixel and event tag setups |
| GA4 plugin | Free core; paid tiers per site, see the vendor's pricing page | Low, paste Measurement ID in a settings field | You want a wp-admin settings screen and basic dashboards | Nothing major, but heavy tag logic |
| Hardcoded Google tag | Free | Medium, edit functions.php in a child theme; editing the parent theme risks losing changes on update | You have a child theme and no plugin appetite | Non-developers changing tags later |
| Google Tag Manager | Free | Medium, add one container snippet, then configure tags in the GTM UI | You will add ads, pixels or event tags later | Nothing; it is the most flexible, but the most to learn |
Plugin prices change: confirm the current figure on the vendor's pricing page before you buy.
03 / 11
What should I do before I install anything?
The most important step on this page comes before installation: find out what is already tracking your site.
Open Plugins and note every analytics or tag-management tool that is active. Then check your theme's header.php and any header/footer code plugin for a Google tag snippet, the script that carries your Measurement ID. If you find both a plugin and a snippet, you already have duplicate tracking, so remove one setup before you add another.
You need an administrator login on WordPress and edit access to your GA4 property. Write down what you will delete first, so a plugin tag and a hardcoded tag never fire together.
Plugin present?
List every active analytics or tag-manager plugin.
Snippet present?
Search header.php and your header/footer code plugin for a Google tag.
Theme file checked?
Confirm whether the tag lives in the theme and will survive an update.
GA4 access ready?
Sign in to the GA4 property with edit rights before you change anything.
04 / 11
Where exactly does the tag go in each method?
Each route has one correct placement, and one place where a second tag usually sneaks in.
With Site Kit or a GA4 plugin, you paste or select the Measurement ID in the plugin's own settings screen and let it insert the tag. Never also paste the snippet into your theme, that is where the second tag sneaks in. For the manual Google tag, add the gtag.js snippet through a wp_head hook in a child theme or a code-snippets plugin, not directly in header.php.
Already double-tracking? Capture the current Measurement ID first. Deactivate the plugin OR remove the hardcoded snippet, never both at once. Clear your cache, then re-verify. A plugin tag and a hardcoded tag must never coexist.
Site Kit by Google
Connect your Google account and paste or select the Measurement ID in Site Kit's settings. Site Kit inserts the tag for you, do not also paste the snippet into your theme.
- Placement
- Site Kit settings screen
- Warning
- Do not add the snippet to the theme
Key pointLet Site Kit own the tag; keep your theme clean.
GA4 plugin
Enter the Measurement ID in the plugin's settings screen. The plugin writes the tag, so it replaces, never joins, a header snippet.
- Placement
- Plugin settings screen
- Warning
- Do not also keep a hardcoded tag
Key pointOne plugin, one Measurement ID, zero theme snippets.
Hardcoded Google tag
Paste the gtag.js snippet via a wp_head hook in a child theme or a code-snippets plugin. This survives theme updates and avoids duplicate inserts.
- Placement
- wp_head hook (child theme or code snippets)
- Warning
- Never paste directly into header.php if a plugin is active
Key pointUse a hook, not the raw header file.
Going further
Migrating a double setup
Method
If you already have a tag in header.php and a plugin active
If you already have a tag in header.php and a plugin active, fix it in a clear order so data keeps flowing without double counts.
You are double-tracking. First, find your current Measurement ID in GA4 or in the existing tag. Write it down. Then deactivate one side only, either the plugin or remove the hardcoded snippet from header.php. Do not remove both at the same time, or you will stop tracking.
After deactivating one side, clear any caching plugin and your browser cache. Then run a verification step: open your site in an incognito window and check GA4 Realtime or use a tag inspector to confirm exactly one tag fires with your Measurement ID.
If you still see two tags, check for a second snippet in header.php, a plugin that injects its own tag, or a Google Tag Manager container that also loads GA4. Remove the duplicate source.
- Capture the IDCopy the Measurement ID from GA4 or the active tag before changing anything.
- Deactivate one sideDisable the plugin OR remove the hardcoded snippet, not both.
- Clear cachePurge caching plugin and browser cache so changes take effect.
- Re-verifyUse GA4 Realtime or a tag inspector in an incognito window to confirm one tag fires.
05 / 11
How do I prove only one tag is firing?
Load one page with Tag Assistant open and watch how many times your Measurement ID appears, one is correct, two means trouble.
Tag Assistant records every tag that fires on a page load. You want exactly one Google tag carrying your G-XXXXXXXXXX Measurement ID (the identifier GA4 assigns to your data stream). Two entries mean a plugin tag and a hardcoded tag are both active.
GA4 Realtime is your second check. Open your site in another tab, load a page, and confirm a single page_view event lands, not two. Repeat on a post or product page, since a sitewide plugin and a theme-only snippet can behave differently.
Tag Assistant first
Open Tag Assistant in Chrome, load one page, and count how many times your G-XXXXXXXXXX Measurement ID appears. One is correct; two means duplicate tracking.
Then GA4 Realtime
Open your site in a second tab and load a page. In GA4 Realtime, confirm a single page_view event appears for that visit rather than a doubled count.
Run it on multiple templates
Check the homepage, a post, and a product page. A plugin may load sitewide while a snippet loads only on the theme template, so different templates can show different tag counts.
Clear cache, then repeat
Clear your caching layer before retesting. A cached page can keep serving old tags and hide the fix you just made.
06 / 11
Why are my pageviews still doubled?
Match the symptom to the cause, most duplicate tracking traces back to four common mistakes.
A plugin tag and a hardcoded Google tag both load gtag.js, and they fire the same Measurement ID, that is the classic failure mode. Disable one, then confirm in the page source that only one gtag.js request carries your ID.
Watch for a plugin installed twice, a snippet plugin duplicating a theme hook, a cache or staging copy serving a tracked page, or a GTM container that also holds a GA4 tag left over from a migration. If you later consolidate into GTM, GA4 must live in one place only.
Symptom-to-cause troubleshooting
| Symptom | Likely cause | First check |
|---|---|---|
| Doubled pageviews | Plugin tag and header snippet both load gtag.js with the same ID | View page source; count gtag.js loads |
| Doubled events | GA4 tag fires twice inside one container, or two containers on the page | Open Tag Assistant; list every GA4 tag firing |
| Only some pages doubled | A staging or cached copy serves the tracked page with the tag still active | Compare a live page and a staging URL side by side |
Illustrative troubleshooting map; causes are common patterns, not measured prevalence.
Going further
Later, with GTM?
Special case
Adding Tag Manager later without breaking GA4
Adding GTM later is fine, provided GA4 ends up in exactly one place.
If you migrate to Google Tag Manager, either place a GA4 tag inside the container or keep a standalone Google tag, never both. The sibling GTM guides walk through the container setup and the tag configuration in that order.
Before deleting the old tag, confirm the container tag fires with the same Measurement ID and reaches DebugView; only then remove the previous snippet or plugin output.
- One place onlyGA4 lives either in a GTM tag or as a standalone Google tag, never both.
- Container verifiedThe GA4 tag inside the container fires and appears in DebugView before you remove the old tag.
- Old output removedDelete the previous snippet or plugin tag output once the container is live.
07 / 11
Should I exclude logged-in admins and set up consent?
Yes to both: your own visits and unconsented hits are the two quietest ways to skew GA4 data.
Excluding logged-in sessions keeps your own admin and editor activity out of reports, but it does not remove the tag. The tag still loads in your browser; GA4 just ignores those hits, so external traffic is unaffected.
If you run a cookie banner, check that it is wired to Consent Mode, the signal that tells Google which storage it may use. A banner that blocks cookies but not the tag still sends hits. Test both states yourself in Tag Assistant instead of trusting the banner's default.
Exclude logged-in users
A plugin setting that tells GA4 to skip hits from signed-in WordPress accounts. It hides your own admin and editor sessions without touching your visitors' data.
- Who it affects
- Logged-in administrators and editors
- Where to set it
- GA4 plugin settings page, then save
Key pointTurn it on and open your site in a logged-out browser window to confirm the hit still fires for normal visitors.
Consent Mode with a cookie banner
A signal that tells Google whether a visitor has accepted analytics storage. Without it, a banner can block cookies yet still allow GA4 hits to be recorded.
- What to check
- Banner vendor documentation and Google's current Consent Mode help page
- How to test
- Tag Assistant, comparing accepted and declined states
Key pointConfirm the banner and the GA4 tag share the same consent state before you trust the reports.
08 / 11
Do I need to pay a plugin or hire someone?
Site Kit is free, a premium plugin costs from about $99 a year (Analytify StartUp, two sites, October 2026 price), and hiring someone is only worth it if you're adding a tag manager or custom events.
Site Kit is free and inserts the Google tag for you, which covers most blogs and small stores. Paid GA4 plugins usually bill annually per site, so treat any quote as an order of magnitude rather than a fixed rate.
Hiring help pays off when you stack a tag manager container, ad pixels, or WooCommerce ecommerce events on top. A single hardcoded tag in a child theme stays a do-it-yourself job.
Worked example
Cost breakdown: free vs. paid plugin vs. one-off setup help
- Free route
- Site Kit plugin, $0
- Paid route
- premium plugin, e.g. Analytify StartUp at $99/year for two sites (vendor price, October 2026)
- Do-it-yourself tag in a child theme
- one evening of your time, $0 in licenses
-
Site Kit for one year$0
0 × 12
The plugin inserts the Google tag for you. Free is enough when you only need pageviews.
-
Paid plugin for one year$99/year
100 + 0
Analytify StartUp price published by the vendor in October 2026; other plugins differ.
-
One-off setup helpyour quote + $99/year
one project + 100 + 0
Worth it when you add a tag manager container, ad pixels, or WooCommerce ecommerce events.
09 / 11
So which setup should I lock in?
Choose one method, remove every other, verify a single tag fire, and only then start reading your reports.
For a blog or content site, Site Kit or a GA4 plugin covers pageviews with logged-in admins excluded. A WooCommerce store needs a plugin that sends ecommerce events, or GTM if you will add ads and pixels. If a tag manager is in your future, install nothing extra now and start from the GTM guides instead.
Whichever you pick, end with one test: load a page with Google Tag Assistant or GA4 Realtime and confirm exactly one tag fires. That single check is what makes the reports trustworthy.
One method chosen
Pick exactly one delivery path: Site Kit, a GA4 plugin, or GTM. Never leave a plugin tag and a hardcoded Google tag active together.
Old tag removed
Delete any hardcoded gtag.js snippet or duplicate plugin tag from your theme, header, or another plugin. Confirm no second Measurement ID is loaded.
Single fire verified
Use Google Tag Assistant or GA4 Realtime on a test page. You should see one page_view per load, not two. Test a second page.
Consent handled
If you serve EU or UK visitors, set up a consent banner and Consent Mode so GA4 respects the choice. Check Google's official consent help page for current setup steps.
10 / 11
Frequently asked questions
11 / 11










