Connect Google Analytics, Plausible or Umami
Bring each site's traffic into WP Foreman from your own Google Analytics (GA4), Plausible or Umami account.
Updated Nov 2, 2026
WP Foreman doesn’t add another tracking script to your sites. It reads the numbers from the analytics you already use and shows them on each site’s Analytics page, next to its backups and updates.
Supported: Google Analytics 4, Plausible (plausible.io or Community Edition) and Umami (Umami Cloud or self-hosted).
Google Analytics (GA4)
- Open Settings › Analytics and click Connect Google Analytics.
- Sign in with the Google account that can see your GA4 properties, and allow See and download your Google Analytics data. That’s read-only: WP Foreman can’t change anything in Analytics.
- Back in WP Foreman, open a site, choose Analytics, and pick its property from the list (WP Foreman suggests the one whose name looks like the site). Or type the property ID: numbers only, from GA Admin › Property details. The
G-XXXXmeasurement ID won’t work here.
One Google connection covers every property that account can see. If a client owns their own GA property, ask them to add your Google account as a Viewer in GA Admin › Property access management.
Universal Analytics (the old UA- properties) stopped collecting data in 2023 and isn’t supported.
Plausible or Umami, step 1: connect your account
- Open Settings › Analytics and click Connect Plausible or Umami.
- Pick Plausible or Umami, then Their cloud or Self-hosted.
- Paste the key (see the table below). For self-hosted, also enter its address, starting with
https://. - Click Connect. Umami keys are checked straight away. Plausible keys are checked when you pick a site, because Plausible’s API needs a site to test against.
| Service | What to paste |
|---|---|
| Plausible (cloud or Community Edition) | A Stats API key: in Plausible, Account settings › API Keys › New API Key, type Stats API. |
| Umami Cloud | An API key: Settings › API keys › Create key. |
| Umami self-hosted | An API key if your version offers them. Otherwise the username and password of an Umami user that can view the sites. We suggest a view-only user just for WP Foreman. |
One connection covers every site in that account, so most people connect once.
Plausible or Umami, step 2: pick each site
- Open a site and choose Analytics in the left menu.
- Choose the account. For Umami, pick the website from the list; WP Foreman suggests the one whose domain matches the site. For Plausible, type the site’s domain exactly as it appears in Plausible (it’s pre-filled from the site’s address).
- Click Connect. WP Foreman checks it can read that site, then shows its traffic.
To change it later, click Change source. Switch off stops showing traffic for that site.
What WP Foreman can and can’t do
- It only reads totals, daily numbers, top pages and top sources. It never changes settings, goals or sites in your analytics.
- Keys and passwords are stored encrypted and are never shown again after you save them. To change one, disconnect and connect again.
- Self-hosted addresses must be public
https://addresses. Private and local network addresses are refused. - Numbers are fetched when you open the page and kept for 15 minutes, to stay well inside Plausible’s and Umami’s rate limits.
Disconnecting Google Analytics in Settings › Analytics also cancels WP Foreman’s access on your Google account. For Plausible or Umami it only removes the key from WP Foreman, so delete the key there too if you’re done with it.
If you disconnect by mistake
Disconnecting a connection unlinks every site that used it, so their dashboards and client reports lose their visitor numbers. WP Foreman remembers which property each site had. Connect the same account again (the same Google account, or the same Plausible or Umami server) and those sites are linked back automatically, with nothing to pick.
Until then:
- The morning report lists each site under Needs you, and does the same when a connection stops working (for example, access was removed on the Google account).
- Scheduled reports aren’t emailed to clients without their visitor numbers. The rule still makes the report, emails you to say it was held and why, and notes it in the site’s log. Fix the link, then make the report again and send it from the site’s Reports page.
Switching Analytics off on one site (Switch off on its Analytics page) is treated as on purpose: that site isn’t relinked later and its reports aren’t held.
Troubleshooting
| Message | Fix |
|---|---|
| “turned the key down (401)” | The key is wrong, revoked, or (Plausible) not a Stats API key. Make a new one. |
| “couldn’t find that site” | Plausible: the domain must match exactly, without https:// or www. unless Plausible has it that way. Umami: the user or key can’t see that website. |
| “Couldn’t reach …” | The self-hosted address is wrong or not reachable from the internet. |
| “Google Analytics refused (403)” | The Google account you connected can’t see that property. Have it added as a Viewer, or connect the right account. |
| “Google ended WP Foreman’s access” | The access was revoked in your Google account, or (during early access) expired after 7 days. Click Connect Google Analytics again. |
| “asking too often” | Wait a few minutes. Plausible allows 600 requests an hour per key. |
Thanks. If something was missing, tell us what.