Updated September 2026: this guide covers Google Analytics 4 (GA4), the Google tag and current verification steps. Universal Analytics and old UA- tracking IDs are not the implementation to use for a new setup.
Quick answer: create a GA4 web data stream, copy its G- Measurement ID and choose one installation owner: Site Kit, the Google tag in code, or Google Tag Manager. Do not load the same ID through two methods. Verify page views in Realtime and test business events separately.
Before installing Google Analytics
You need a Google Analytics account, a GA4 property and a web data stream for the exact website you want to measure. In Google Analytics, open Admin → Data streams → Web, create or select the stream, and copy its Measurement ID.
Decide who owns the Analytics account before connecting WordPress. The business should normally own the property and grant access to employees or agencies. Avoid placing a critical analytics property only inside a freelancer’s personal account.
Write a short measurement plan before adding code. For a service website, useful outcomes may include successful contact forms, signup completion and plan selection. For a store, start with product views, add-to-cart, checkout and purchase.
Choose one installation method
| Method | Best fit | Main risk |
|---|---|---|
| Site Kit by Google | Owners wanting a guided WordPress connection | Duplicate tracking if another tool already inserts the tag |
| Google tag in theme or site integration | Simple sites with a developer-managed implementation | Theme updates or incorrect placement if added carelessly |
| Google Tag Manager | Teams managing several tags and event rules | Unpublished containers, duplicate tags and weak governance |
Google’s own troubleshooting guidance recommends choosing either a direct Google tag implementation or Tag Manager rather than unintentionally loading both for the same measurement.
Method 1: connect GA4 with Site Kit by Google
Site Kit by Google is the official Google plugin for WordPress. It is suitable when a site owner wants a guided connection and basic Analytics and Search Console information inside WordPress.
- Back up the site and confirm access to the correct Google account.
- Check the page source or Tag Assistant for an existing Google tag.
- Install Site Kit from Plugins → Add New and confirm the author is Google.
- Complete the ownership verification flow.
- Open Site Kit → Settings → Connect More Services → Analytics.
- Select the correct account, GA4 property and web data stream.
- Confirm whether Site Kit should place the tag or use an existing implementation.
Method 2: add the Google tag directly
A direct installation is useful when tags are managed in code and you want to avoid another runtime plugin. In the GA4 web stream, choose View tag instructions → Install manually and copy the complete Google tag supplied for the property.
The tag belongs immediately after the opening <head> element on every public page you intend to measure. Do not paste it into one page and do not edit a parent theme file that will be overwritten by an update. Use a maintained child theme or a site-specific integration.
Never copy a tag from a tutorial. Use the code generated for your property so the correct ID and current format are preserved.
Method 3: use Google Tag Manager
Tag Manager is appropriate when a team needs governed deployment of analytics, advertising or other tags. Install the container once, create the GA4 configuration or Google tag inside the container, configure its trigger and publish the container version.
Preview mode is not publication. After testing, submit and publish the container, then verify the production website. Document who can publish changes so an agency handoff does not leave nobody responsible.
Consent and privacy
Analytics can have privacy and consent implications. Review the requirements that apply to the business and its visitors before collection begins. The consent interface, Google tag and any consent-mode configuration must agree; a banner that does not control the tag is only visual decoration.
Test both states:
- before the visitor makes a consent choice;
- after analytics consent is granted;
- after consent is refused or withdrawn.
Use legal advice for the business’s specific obligations. A WordPress plugin cannot decide compliance on the owner’s behalf.
How to verify GA4
- Open the website in a private window without an ad blocker.
- Use Google Tag Assistant to confirm the expected tag and events.
- Open GA4 Realtime and visit several public pages.
- Confirm that page views appear in the correct web data stream.
- Inspect posts, landing pages and checkout templates—not only the homepage.
- Test each important form or ecommerce event and verify its parameters.
Google notes that initial collection may take time. Realtime is useful for implementation checks, but standard reports can take longer to process.
Common WordPress analytics problems
Duplicate page views
The same Measurement ID is often loaded by two systems—for example Site Kit and a theme option, or Tag Manager and another analytics plugin. Choose one owner for tag placement and remove the duplicate.
No data in Realtime
Confirm the ID matches the selected stream. Then test without an ad blocker, review consent behaviour, publish Tag Manager changes and clear page cache after modifying code.
Form submissions are not measured
A page view on a thank-you URL can work for simple forms, but AJAX forms may not navigate. Track a confirmed success state rather than a button click; clicking Submit does not prove that the server accepted the enquiry.
WooCommerce revenue is missing
Basic page-view tracking does not create a complete ecommerce implementation. Purchase, checkout and product events need a compatible integration and should be tested with a sandbox order, including currency, value and transaction ID.
Measure B2B outcomes, not page views alone
For a B2B website, the useful events usually reflect progress through a longer decision journey: a qualified form submission, meeting request, pricing interaction, account signup or completed purchase. Document the final success state and verify that it reaches the inbox, calendar, CRM or order system instead of counting only the button click.
Review those events by landing page, source and device, then investigate the pages where qualified visitors stop. The guide to finding conversion leaks in WordPress provides a practical diagnostic sequence. If tracking or forms fail after site changes, a defined WordPress support workflow gives the issue an owner and escalation path.
Frequently asked questions
Do I need a WordPress plugin to install GA4?
No. GA4 can be installed with Site Kit, a direct Google tag or Google Tag Manager. Use one method that fits the site’s maintenance workflow.
Where do I find the GA4 Measurement ID?
In Google Analytics, open Admin, select the correct property, open Data streams and choose the web stream. The Measurement ID begins with G-.
Why does GA4 show duplicate page views?
The most common cause is that the same tag is installed in more than one place. Check Site Kit, Tag Manager, theme settings, header scripts and other analytics plugins.
How do I know whether GA4 conversions work?
Complete the real action in a test environment or controlled session, confirm the event appears with correct parameters, and only then mark the appropriate event as a key event in GA4.
Need help with a clean implementation?
If Analytics is duplicated, missing from templates or reporting the wrong outcomes, treat it as an implementation problem rather than adding another plugin. CodaStudio can review active tags, remove duplication and verify important journeys through ongoing WordPress support.
