Install PureMetrix on WordPress

Get PureMetrix Analytics running on your WordPress site in a few minutes: install the plugin, complete the setup wizard (Connect → Go live), then check that pageviews—and WooCommerce purchases, if you run a shop—arrive.

What you need

A PureMetrix account (register).
Administrator access to your WordPress site.
Optional: WooCommerce, if you want purchases recorded server-side.

Create the site first (optional)

If you want to connect manually with a key, first add your website in your PureMetrix account using the address of your live site. The one-click connection in the wizard can create the site for you. If you also measure a test site (staging), set it up as a separate site.

Install and setup wizard

In WordPress, go to Plugins → Add New, search for PureMetrix Analytics, click Install Now, then Activate (or upload the ZIP file).
The setup wizard opens (you can find it later under PureMetrix → Setup).
Connect — use the one-click button to connect with PureMetrix, or paste your site’s Public key from the Sites page of your PureMetrix account.
Go live — optionally click Send test pageview, then Open Dashboard.
If you skipped the test: open a public page of your site while logged out and check that a pageview arrives.

Privacy settings

Exclude the Administrator and Editor roles from tracking (PureMetrix → Settings → Privacy). PureMetrix sets no cookies; visitors are counted using a random value (salt) that changes every day.

Optional same-origin proxy

With Ad-Blocker Defense (Same-Origin Proxy), the script and events are served from your own domain (via /px). Check pageviews again afterwards and allow /px in your security plugin.

WooCommerce

Check under Plugin integrations that WooCommerce is switched on, place a test order, and confirm the Purchase event. Track conversions.

Go-live checks

Pageviews arrive while logged out
Admins are excluded
Goal or purchase checked, if needed
Dashboard link ready for everyone who needs the numbers

After go-live

Bookmark the PureMetrix dashboard and the dashboard inside WordPress for your client. After one week, check that events still arrive—especially after changes to caching plugins. Note where the site key is stored so the next developer does not reconnect blindly.

Order of steps that avoids false alarms

Create the PureMetrix site first (or use the one-click connection)
Install the plugin and complete Connect → Go live in the wizard
Exclude admin roles under PureMetrix → Settings before you browse the shop yourself
Switch on the same-origin /px proxy if ad blockers are a concern
Check pageviews from a private window
Add goals or WooCommerce purchase tracking

Caching plugins that serve logged-out visitors old pages without the tracking script are the most common reason for “it never tracks.” Clear your caches after connecting. Security plugins that block unknown paths can block /px—allow it after switching on the proxy.

Hand-off notes for agencies

Give clients shared dashboard links instead of CSV files by email. Note which roles are excluded and which thank-you URLs are goals, so the next agency does not “fix” a working setup.

Test site and live site keys

Use a separate PureMetrix site for your test site (staging). Otherwise test traffic and plugin experiments end up in client dashboards. Connect the test site first, check pageviews from a private window, then connect the live site with its own exclusions.

After go-live, save a filter for the tracking path (direct or /px) in the Network tab of your browser’s developer tools. When someone says tracking has stopped, you can check within a minute whether the script is in the page.

Common WordPress gotchas

Full-page caching serves logged-out visitors pages from before the connection.
Optimisation plugins combine or delay scripts in the wrong order.
Security firewalls block /px after the proxy was switched on.
Multilingual plugins create extra thank-you paths without matching goals.
Custom WooCommerce thank-you templates skip the purchase hook.

Fix these before you discuss how cookieless measurement works. In meetings, setup errors are easily mistaken for “privacy tools count too little.”

A verification checklist you can paste into tickets

Private window, logged out → open the home page → check the tracking request in the Network tab → open the thank-you test URL → confirm the goal → for shops, place a WooCommerce test order → confirm the purchase → check that an excluded role sends nothing. Note the times. That settles most “is it working?” questions without a call.

If connecting fails, try the one-click connection again, or copy the Public key again and check that your WordPress site address matches the domain in your PureMetrix site settings—mismatched domains cause more support tickets than product bugs.

Monitoring after installation

For the first two weeks, compare daily pageviews roughly with your server logs. A sudden drop to zero usually means caching or a firewall, not a problem with cookieless counting. Note the connection status and the last four characters of the site key in your project wiki so the next developer does not have to guess.

If connecting fails behind a firewall, allow outgoing HTTPS connections to app.puremetrix.org and collect.puremetrix.org, then retry the one-click connection before pasting the key manually.