Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsSome links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
The simplest supported way to install Google Analytics 4 (GA4) on WordPress is Google’s free Site Kit by Google plugin. Install and activate Site Kit, connect the Google account that can access your Analytics property, complete the setup, and verify that one Google tag is loading on your public pages. Your site must run WordPress 5.2 or newer and PHP 7.4 or newer, be publicly accessible, and expose a working WordPress REST API.
Before you install: check these prerequisites
- WordPress: version 5.2 or newer.
- PHP: version 7.4 or newer.
- Site status: a live production site, not a staging, maintenance-mode, password-protected, or otherwise private site.
- Browser: a current modern browser.
- REST API: available to Site Kit. Security rules or plugins that block it can prevent setup.
- Google access: an account that owns or can administer the required GA4 property.
Have your Analytics property ready, or be prepared to create one during the connection flow. A GA4 measurement identifier normally begins with G-. Site Kit can also display a Google tag identifier beginning with GT-, depending on the implementation.
![Google Workspace Guide: Unlock Every Google App – Elevate Efficiency with Exclusive Tips, Time-Savers & Step-by-Step Screenshots for Quick Mastery [II EDITION]](https://m.media-amazon.com/images/I/41CX0AjJhAL._SL160_.jpg)
Install GA4 with Site Kit by Google
- In WordPress, open Plugins > Add New.
- Search for Site Kit by Google, select Install Now, and then select Activate.
- Open Site Kit and choose the option to connect Google Analytics.
- Sign in with the Google account that owns or has access to the Analytics property.
- Complete the requested site-ownership verification and Search Console connection.
- Select the existing GA4 property and web data stream. If no property exists, follow the setup prompts to create Analytics.
- Open Site Kit > Settings > Connected Services > Analytics. Record the connected property and tag IDs so you can compare them with your Analytics account and page source.
Site Kit places the Google tag for you, so you do not normally paste the GA4 ID into a theme file. Keep the plugin active and avoid adding a second implementation through another plugin, a theme option, or a code snippet.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteChoose one tracking implementation
WordPress can load Analytics through several routes. Pick the route that matches your needs, and do not run overlapping snippets.
| Method | Setup effort | Custom events and tags | WordPress visibility | Main risk | Debugging approach |
|---|---|---|---|---|---|
| Site Kit | Lowest; guided Google connection | Basic connection only; custom work needs GA4 configuration or Tag Manager | Property and reports are visible in WordPress | Another plugin or theme may create a duplicate tag | Site Kit settings, page source, Analytics, and Tag Assistant |
| Google Tag Manager (GTM) | Moderate; container and tags must be configured | Highest control for events, WooCommerce actions, and multiple marketing tags | Container status is visible, but detailed configuration lives in GTM | Duplicate GA4 tags or an incorrectly installed container | GTM preview, Tag Assistant, page source, and Analytics |
| Manual Google tag | Highest technical responsibility | Flexible, but every event and change is maintained manually or through code | Little or no native WordPress dashboard visibility | Theme changes, caching, or a second plugin can remove or duplicate the code | Page source, Tag Assistant, and Analytics real-time data |
For a standard site, start with Site Kit. Use GTM when you need a managed collection of custom events, ecommerce actions, conversion tags, or other marketing scripts. A manual tag is appropriate only when you can safely maintain code and consent behavior.
Prevent duplicate page views
Site Kit can detect an Analytics snippet that is already present. If prompted, either connect to the existing implementation or allow Site Kit to place the snippet. Do not choose both.
Rank #2
![The Google Workspace Bible: [14 in 1] The Ultimate All-in-One Guide from Beginner to Advanced | Including Gmail, Drive, Docs, Sheets, and Every Other App from the Suite](https://m.media-amazon.com/images/I/41AWmhmGFuL._SL160_.jpg)
- The Google Workspace Bible: [14 in 1] The Ultimate All in One Guide from Beginner to Advanced Including Gmail, Drive, Docs, Sheets, and Every Other App from the Suite
- ABIS BOOK
- Check theme settings, header/footer code, analytics plugins, and GTM containers for an existing GA4 or Google tag.
- Leave exactly one active GA4 implementation for the property on each page.
- After changing methods, clear relevant page, CDN, and optimization caches before testing.
Two active snippets can send the same page view twice, making traffic and event reports unreliable.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Where to find and verify the GA4 ID
Find the connected ID in WordPress
Go to Site Kit > Settings > Connected Services > Analytics. Confirm that the property, web stream, and tag identifiers match the account you intended to use.
Check the public page source
- Open a public page in a private browser window or a browser profile where you are not logged in to WordPress.
- Use the browser’s View page source command.
- Search for the expected
G-orGT-identifier.
If the identifier is absent, the tag may be blocked by a consent choice, cache or optimization rule, security plugin, theme condition, or an incomplete Site Kit connection.
Confirm incoming data
Open the matching web stream in Google Analytics and check its real-time reporting while loading the public page. Use Google Tag Assistant to inspect whether the tag fires and whether events contain errors. Test with your production cache, optimization, security, and consent plugins enabled; a tag that works with those tools disabled is not a complete installation.
Configure events, conversions, and ecommerce
The basic Site Kit connection establishes Analytics but does not provide a complete custom-event system. For downloads, form submissions, WooCommerce actions, lead conversions, or several marketing platforms, choose one of these approaches:
- GA4 configuration: create or mark events and conversions in the Analytics interface when the required event data is already available.
- Google Tag Manager: deploy event tags and other marketing tags from a container, using triggers and variables suited to your site.
Validate completed events with Tag Assistant and then confirm that the expected event reaches the correct GA4 property. Keep event names and conversion definitions consistent across your forms, store, and reports.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Make consent work with your audience
Analytics installation is not the same as legal compliance. Your consent behavior depends on your visitors’ jurisdictions, your cookie and privacy policies, and the consent-management platform you use.
When Site Kit’s Consent Mode integration is enabled, visitors in the European Economic Area, Switzerland, and the United Kingdom are not included in Analytics and Ads tracking by default until the site’s consent requirements are satisfied. Site Kit can work with compatible consent-management plugins; its documentation gives Complianz as an example. Such integrations can block Analytics or Ads collection until a visitor consents through Google’s Consent Mode API.
- Choose a consent-management platform appropriate for your audience and legal obligations.
- Configure it to communicate consent states through the supported Consent API or integration.
- Ensure Analytics and advertising tags remain blocked when your policy requires prior consent.
- Test accept, reject, and withdrawal paths in a clean browser session.
No plugin installation alone guarantees compliance. Review the resulting behavior with your privacy lead or legal adviser, especially if you serve multiple jurisdictions.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Quick Recap
Troubleshoot a tag that is not showing
Site Kit setup will not complete
- Confirm the site is live and not password-protected or in maintenance mode.
- Check that WordPress and PHP meet the minimum versions.
- Test the REST API and temporarily review security rules that might block Site Kit requests.
- Sign in with the Google account that has access to the intended property.
The ID is missing from page source
- Check whether a consent banner is correctly withholding the tag before consent.
- Clear WordPress, plugin, server, and CDN caches.
- Inspect optimization settings that defer, combine, or remove scripts.
- Look for page-specific templates or login conditions that prevent the tag from loading.
Analytics reports duplicate or unexpected traffic
- Search page source and tag diagnostics for more than one GA4 or Google tag.
- Disable the competing plugin, theme snippet, or GTM GA4 tag, leaving one implementation.
- Retest real-time data after caches have expired or been purged.
Events do not arrive
- Verify the trigger and event parameters in GA4 or GTM.
- Run Tag Assistant while performing the action on the public site.
- Confirm the event is sent to the same property and web stream shown in Site Kit.
Installation checklist
- WordPress 5.2+ and PHP 7.4+ are installed.
- The production site is publicly reachable and its REST API works.
- Site Kit is connected to the intended Google account, property, and web stream.
- Exactly one Google tag implementation is active.
- The expected
G-orGT-identifier appears in public page source when consent permits tracking. - Tag Assistant reports the expected tag and events.
- Google Analytics real-time reporting receives a test visit.
- Consent, caching, optimization, and security behavior has been tested in its production configuration.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
