How to track website analytics in WordPress

Decide which questions your reports must answer before adding tracking. Start with page views, users, sessions, traffic sources, popular content and key actions such as contact submissions, downloads or purchases.

Choose between a cloud service such as Google Analytics 4 and locally hosted analytics. A local option keeps reports closer to your WordPress installation, while Google Analytics offers a wider reporting and marketing ecosystem.

For Google Analytics, create or select a GA4 property, add a web data stream for the exact site domain, and copy its Measurement ID. Google says the ID is found under Admin, Data streams and Stream details; it normally starts with G-.

Keep one tracking method per property. Adding the same tag through a plugin, the theme and Google Tag Manager can double-count page views.

The manual route works without an analytics dashboard plugin: place the provider's tracking snippet in the front-end HTML of every page, normally in the document head. In WordPress, a custom plugin or child theme can output code through the wp_head action, provided the active theme calls wp_head().

Do not edit the parent theme, because an update can overwrite your change. This route is fine for basic page-view reporting, but you must handle consent blocking, logged-in-user exclusions, custom events and future code changes yourself.

If you want reports inside WordPress, install an established analytics integration and connect it to the property or local data store. Google's Site Kit can connect Analytics, place the tag across the site and show key reports in the WordPress dashboard. It also warns when another Analytics snippet is already present.

For event tracking beyond standard measurements, configure events in Google Analytics 4 or through Google Tag Manager; Site Kit alone does not configure every custom event.

Decide whether analytics should wait for consent, and classify the scripts correctly in your consent tool. If tracking is blocked until consent, visitors who reject analytics will not appear in the reports. Site Kit includes consent-mode settings for certain regions, but your banner and analytics configuration still need to agree.

Exclude administrators and other internal users where possible. Also check that caching, script delay, minification or a security rule is not moving, combining or blocking the tracking code. These changes commonly leave the site looking normal while reports stop receiving data.

Open the site in a private browser window, visit several pages and trigger any actions you configured. Then check the provider's real-time or debug report. Confirm that the correct property receives the visit, the tag appears once in the page source, and consent changes actually stop or allow tracking.

Do not expect historical data to appear after installation. New properties can take a day or two to populate, and Google notes that missing data can result from an absent tag, an incorrect tag, no traffic or processing delay.

For a quicker setup with reports inside WordPress, use Burst Statistics Pro. It is suited to sites where data ownership matters because it provides privacy-focused, locally hosted analytics and real-time reports, with configurable reporting and export options.

Install the plugin from Plugins in the WordPress dashboard, activate it, complete its setup prompts and confirm that visits appear in its dashboard. If you also connect Google Analytics, use one clear source for each metric and test for duplicate tracking.