Install GA4 on WordPress: Site Kit, GTM or a Manual Google Tag
Published:
Last Updated:
Category: Web Analytics
Authors: Shusaku Yosa
Choose a WordPress GA4 installation method after checking existing tags and ownership. Site Kit, dedicated plugins, GTM and manual deployment each have maintenance requirements. Whatever you choose, test delivery from public pages to the intended destination rather than treating a saved setting as verified measurement.
Check the account, web stream and existing tags first
Confirm the GA4 account, property and web stream, then record its G- measurement ID. This identifies the stream, not a GTM container. Use the official ID guidance to avoid entering the wrong type of identifier.
Potential owner | Inventory | Decision |
|---|---|---|
Site Kit | Connection and placement switch | Dashboard connection, placement or both |
Other plugin | Tag ID and event settings | Required features and maintainer |
Theme | Input type and output templates | Checks after replacement |
GTM | Container, tags, triggers and version | Current destinations |
Creating a new property unnecessarily separates reporting history. If permissions or ownership are unclear, ask the administrator rather than guessing an ID or creating another destination.
Compare Site Kit, plugins, GTM and manual installation
Method | Management focus | Selection condition |
|---|---|---|
Site Kit | WordPress connection and supported placement | Permissions and existing-tag detection |
Dedicated plugin | Vendor-specific settings and features | Current functionality, cost and maintenance |
GTM | Container tags and release versions | Container placement and publishing rights |
Theme or manual | Site templates | Ownership of update and replacement tests |
Advertising or event measurement does not universally require GTM. The Site Kit event-tracking guidance illustrates other configurations. Choose around existing architecture and success-event requirements, and verify plugin features in the edition you plan to use rather than assuming paid capabilities.
Connect Site Kit to the intended property
Install and activate Site Kit in WordPress, complete Google authentication and site verification, then select the intended Analytics account, property and web stream. Reuse the established destination when appropriate. The Analytics connection documentation explains available connection options.
Displaying dashboard metrics and placing code are separate operations. According to Site Kit’s placement guidance, detection of the selected existing tag can automatically turn placement off. Check the final placement state and actual public-page delivery after connection; do not infer them solely from a successful login.
Configure and publish the Google tag through GTM
Decide how the GTM container itself reaches WordPress. Within the intended container, configure the current Google tag, its destination and trigger. Older guides referring only to a GA4 configuration tag can use obsolete interface terminology.
- Confirm the container and currently published version.
- Design the Google tag and required event conditions.
- Use preview with the intended pages and consent states.
- Review, publish the container and retest production.
Follow the Google tag setup instructions. GTM version control does not make deployment immune to theme, plugin, caching or consent changes that affect the container on the site.
Check theme-based and manual deployment requirements
A theme field may expect an ID or a complete snippet. Check its current GA4 support before entering anything; a legacy UA field does not become compatible simply because a G- ID was entered.
For direct installation, place the complete Google tag immediately after the opening <head> tag on each target page, as described in Google’s manual installation guidance. Avoid outputting it both from a shared template and individual article fields. Include theme updates and replacements in the release test plan. Saving the setting is separate from verifying delivery.
Diagnose duplicates by destination and event delivery
The presence of both Site Kit and GTM does not by itself establish duplication. Test whether one operation sends repeated equivalent events to the same destination. Intentional delivery to another property is a separate case.
For a fictional ordinary page-load test, opening one post should produce the one page_view expected by that design. If two reach the same measurement ID and URL, inspect placement sources and triggers. One active user or one library load cannot settle the question. Use Tag Assistant and DebugView to inspect event delivery.
Check caching, consent, logged-in exclusion and filters
Symptom | Condition to inspect | Next action |
|---|---|---|
Saved setting, old tag | Public HTML and caches | Verify release and refresh relevant cache |
Only admins missing | Logged-in exclusions | Run a separate logged-out test |
Some pages missing | Template and consent state | Review target coverage |
Exclude internal visits | Identification and data filter | Test before activating exclusion |
The internal traffic documentation separates identification rules from data filters. Active exclusion permanently removes matching data during processing; it cannot later be restored in Analytics or BigQuery. Changing IPs can fall outside an existing rule. Also distinguish consent-related noncollection from a broken installation.
Test WordPress templates and document ownership
For a fictional acceptance test, log out, use a consistent consent-granted state and open one post, one static page and one category page. With ordinary page loads, record the expected page_view, destination, URL and actual count for each. Test administrator exclusion separately.
Template | Expected check | Record |
|---|---|---|
Post | page_view to intended destination | Date, URL and count |
Static page | Receipt under the same conditions | Template and count |
Category | Delivery within designed coverage | Count and any exclusion reason |
Verify submission or purchase success under a separate acceptance criterion. Clicks and key events are not counts of people. Hand over tag ownership, published version, exclusions, unresolved checks and updates that require another test.
Continue with the guide that matches your next task: What Is a Tracking Code? GA4, Google Tags and Verification; GA4 Free vs Analytics 360: Limits, Costs and When to Upgrade; Time on Page vs GA4 Engagement Time: How to Measure and Interpret It.
