Amplitude
A product-analytics tool for events, funnels and user behaviour.
What it reads
- Your visible events and their weekly totals: events list; hidden, deleted and inactive events are dropped, the three biggest by weekly total are counted
- Daily unique users per top event: event segmentation, measure uniques, one-day steps, last 7 days up to yesterday
- Daily event totals per top event: event segmentation, measure totals; yesterday's value
- Daily active users: the active user count per day, last 7 days
Moments
- A day's top event has unique users. Event name and numbers are examples; the real line uses your event's name and Amplitude's count for the last full day.
- Daily active users are counted. Number is an example; the real line is Amplitude's active user count for the last full day.
- Unique or active users in a day cross 100, 1k, 10k or 100k. Fires once per level, the first time a top event's daily unique users, or daily active users, in the last 7 days reach it.
Set up
- Open Settings, Projects, your project, General tab.
- Click Manage next to API Key and copy it.
- Click Manage next to Secret Key, generate one if needed and copy it at once; it is shown only when made.
- Paste apikey:secretkey into FoxPlug; type eu in the region box for EU projects.
What it never reads
- User profiles, user activity streams or user search (those endpoints are never called)
- Event properties or the raw event export (the export endpoint is never called)
How it differs
Amplitude gives counts per named event and a daily active user figure, so FoxPlug reports your biggest events by name and your active users. Unlike PostHog it never reads a person table.
What does FoxPlug need from Amplitude?
The project's API key and secret key, pasted as apikey:secretkey. Amplitude shows a secret key only when it is generated.
Does FoxPlug read my users?
No. It asks for event counts, unique-user counts and the daily active user count. No profile, email, user ID or event property is requested.
My project is on the EU servers. Does that work?
Type eu in the region box. The reader then calls Amplitude's EU address.
Fathom
A paid, privacy-first web analytics service with a simple dashboard and no cookies.
What it reads
- Unique visitors per day: uniques, stored as visits
- Visits per day: visits, stored as sessions
- Pageviews per day: pageviews
- Average duration: avg duration per day, averaged across days that reported one, flagged as a mean
- Bounce rate: bounce rate per day, averaged across reporting days (not session-weighted)
Moments
- Visits fall after a deploy. Fathom's daily uniques averaged 120 before a deploy and 70 since.
- Arrivals more than halve between halves of the 30 days. Uniques 300 in the first half and 120 in the second raise the card.
- Owner presses for the brief. Because totals are summed from the same daily list, the totals and the series on screen cannot disagree.
Set up
- Open app.usefathom.com/api.
- Click Create new, name it FoxPlug, set permissions to Read only (all sites) or Site-specific, then Save changes.
- Copy the token now.
- Optionally copy the Site ID of the site to read.
- Paste the key (and Site ID) into FoxPlug.
What it never reads
- Pages, referrers or goals (the aggregation asks for five metrics by day)
- Sites other than the Site ID given
How it differs
Fathom returns uniques, visits, pageviews, average duration and bounce rate per day from one aggregation call, with the site chosen by Site ID. Plausible does the same over a different API and needs the domain; Fathom is the one whose API calls count against your pageview quota.
Does reading Fathom cost me pageviews?
Fathom counts every API request against your monthly pageview allowance, so FoxPlug reads only when you press, not continuously.
Where is the Site ID?
In your Fathom dashboard for the site: a short run of letters like ABCDEFGH.
Is the token read-only?
The guide has you create it with Read only permission.
Firebase
Google's app platform; Google Analytics for Firebase reports mobile and web app events through a linked GA4 property.
What it reads
- Daily users: totalUsers per date, mapped to visits
- Daily sessions: sessions per date
- Daily pageviews: screenPageViews per date (runReport, 30 days)
- Average session duration: averageSessionDuration per day, averaged across days into one mean seconds figure, flagged as a mean
- Bounce rate: bounceRate per day (a 0 to 1 fraction), averaged across days and shown as a percentage
Moments
- Visits fall after a deploy. Daily totalUsers from the linked property averaged 120 before and 70 since. The same thresholds as every tool apply.
- Arrivals more than halve across the 30 days. Users 400 in the first half and 150 in the second raise the question.
- First pull right after linking Firebase to Analytics returns nothing. Google says data can take 24 hours to flow after linking, so an empty first pull may be that rather than a broken connection (connect guide text).
Set up
- Firebase console: Project settings, Integrations, Google Analytics card; read the linked GA4 Property ID.
- Google Cloud (same project): APIs and services, Library, enable Google Analytics Data API.
- IAM and Admin, Service Accounts, create one, Keys tab, Add key, Create new key, JSON.
- Copy the full JSON contents.
- analytics.google.com Admin, Property access management for the linked property: add the service account's client email as Viewer.
- Paste the Property ID and the JSON key into FoxPlug.
What it never reads
- App event names or custom events (only five metrics by date are requested)
- Properties other than the one linked property you give
How it differs
Identical to Google Analytics 4 in what FoxPlug reads: lcnc-ga4-pull serves both keys with one report (users, sessions, screen page views, average session duration, bounce rate by day). The only differences are the connect panel's steps, which start in the Firebase console, and the label.
Is Firebase read differently from GA4?
No. A Firebase Analytics property is a GA4 property, and the same function reads both with the same report; the saved connection records which of the two it is.
Where do I find the property ID?
In the Firebase console under Project settings, Integrations, on the Google Analytics card.
Why is my first pull empty?
If you only just linked Firebase to Analytics, Google says data can take up to 24 hours to flow.
Google Analytics 4
Google's web and app analytics product, reporting users, sessions, sources and conversions for a property.
What it reads
- Daily users: totalUsers per date, mapped to visits
- Daily sessions: sessions per date
- Daily pageviews: screenPageViews per date (runReport, 30 days)
- Average session duration: averageSessionDuration per day, averaged across days into one mean seconds figure, flagged as a mean
- Bounce rate: bounceRate per day (a 0 to 1 fraction), averaged across days and shown as a percentage
Moments
- Visits fall after a deploy. GA4's daily totalUsers averaged 120 before a Tuesday deploy and 70 since. Needs at least 3 days before, 2 after and 10 a day before.
- Arrivals more than double between the halves of the 30 days. Users 210 in the first half, 460 in the second. The card shows both halves.
- Arrivals more than halve. Users 500 in the first half and 180 in the second raise the question, with both figures on the card.
Set up
- In the Google Cloud Console (right project selected): APIs and services, Library, enable Google Analytics Data API.
- IAM and Admin, Service Accounts, create a service account named FoxPlug; it needs no Cloud role.
- Open it, Keys tab, Add key, Create new key, JSON; a.json file downloads.
- Copy the entire JSON contents.
- In analytics.google.com Admin, Property access management: add the service account's client email as Viewer on that property.
- Property details: copy the Property ID (digits).
- Paste the Property ID and the full JSON key into FoxPlug.
What it never reads
- Traffic sources, campaigns, conversions or event-level data (the report asks for five metrics by date only)
- Other properties on your Google account (only the saved Property ID is queried)
How it differs
Same puller and same API call as Firebase; GA4 is the website property. Compared with Plausible, Fathom and Umami it needs a service-account JSON key and a Viewer grant instead of an API key, and its bounce rate and session length are averages of daily values.
Why a service account instead of signing in with Google?
FoxPlug reads GA4 with a service-account JSON key that you add as a Viewer on the property. That is the credential the connect panel asks for.
Which ID is the Property ID?
A plain number from Admin, Property details. A code starting G- is a Measurement ID and will not work.
Does FoxPlug see my conversions or traffic sources?
No. The report asks only for users, sessions, pageviews, average session duration and bounce rate by day.
Matomo
An open-source web analytics platform, available as Matomo Cloud or self-hosted.
What it reads
- Unique visitors, whole range: VisitsSummary.get over the last 30 days: nb uniq visitors (only if Matomo returns it for the range)
- Visits: nb visits, stored as sessions
- Average time on site: avg time on site, a mean in seconds, flagged as a mean
- Bounce rate: bounce rate (visits with one action), parsed from a string like 66%
- Daily visits: VisitsSummary.get per day: nb uniq visitors and nb visits
- Daily pageviews: Actions.get per day: nb pageviews; the total is their sum
Moments
- Visits fall after a deploy. Matomo's daily visitors averaged 120 before a deploy and 70 since; Matomo goes through the same rule as the other tools.
- Arrivals more than double. Daily nb uniq visitors 140 in the first half and 330 in the second.
- Matomo refuses the request. A wrong Site ID or a token without View access returns Matomo's error text (first 160 characters), so the owner can reconnect.
Set up
- In your Matomo open Administration, Personal, Security.
- Create New Token and confirm your password.
- Describe it FoxPlug and choose the View access level.
- Copy the token (shown once).
- Administration, Websites, Manage: note the ID column for your site.
- Paste your Matomo address, the Site ID and the token into FoxPlug.
What it never reads
- Individual visits, visitor logs or page-level reports (Actions.get is asked for pageview totals by day only)
- Sites other than the Site ID given
How it differs
Matomo is the one in this group where FoxPlug makes three calls (range summary, daily summary, daily pageviews) against an address you provide, so it works for self-hosted installs as well as Matomo Cloud. It gives bounce rate, average time on site and unique visitors where available; Umami and Plausible are read on their own hosts or by key alone.
Does FoxPlug work with self-hosted Matomo?
Yes. The Matomo address is part of the saved connection, so cloud and self-hosted installs are both read from the address you enter.
What access does the token need?
The View access level, the lowest. The token only reads the sites your user can see.
Is my token exposed?
The pull sends it in the body of a POST request rather than in the URL.
Mixpanel
A product-analytics tool for events, funnels and retention.
What it reads
- Your top events by name: names of today's top events (type general, up to 10); when today is still empty, the 31-day event-name list
- Daily unique users per top event: Aggregate Event Counts, type unique, unit day, last 7 days up to yesterday
- Daily event totals per top event: the same call with type general; yesterday's value
- Largest single-day unique count: the highest daily unique-user figure over the 7 days, across the top events
Moments
- A day's top event has unique users. Event name and numbers are examples; the real line uses your event's name and Mixpanel's count for the last full day.
- Unique users in a day cross 100, 1k, 10k or 100k. Fires once per level, the first time a top event's daily unique users in the last 7 days reach it.
Set up
- Open your Mixpanel project settings, Service Accounts (Owner or Admin needed).
- Add a service account named FoxPlug and copy the username and secret at once; the secret is shown once.
- Open Organization settings, Projects, your project, and copy the Project ID.
- Paste username:secret into FoxPlug, then the Project ID (add |eu or |in for those regions).
What it never reads
- User profiles, emails or user IDs (the people endpoints are never called)
- Event properties or the raw event stream (the export endpoint is never called)
- Saved reports (the Insights query needs a saved report id and is not used)
How it differs
Mixpanel gives counts per named event, so FoxPlug reports your top events by name and the unique people behind each, rather than page visits. Unlike PostHog it never reads a person table, and unlike Plausible or Fathom it needs no website.
What does FoxPlug need from Mixpanel?
A service account username and secret, and your Project ID. Mixpanel shows the secret once, when the account is made.
Does FoxPlug read my users?
No. It asks for event counts and unique-user counts only. No profile, email, user ID or event property is requested.
My project is in the EU or India. Does that work?
Add a bar and eu or in after the Project ID. The reader then calls the matching Mixpanel address. Mixpanel says a project's region cannot be changed once it is made.
Plausible
A lightweight, privacy-friendly web analytics tool, cloud or self-hosted.
What it reads
- Visitors: visitors metric over the last 30 days (Stats API v2 aggregate call)
- Visits: visits metric (stored as sessions)
- Pageviews: pageviews metric
- Bounce rate: bounce rate, labelled as percent of visits with one pageview
- Visit duration: visit duration, a mean in seconds, flagged as a mean
- Views per visit: views per visit, kept in the extra block
- Daily series: visitors, visits and pageviews by time:day, a second call over the same range
Moments
- Visits fall after a deploy. Plausible's daily visitors averaged 120 before a Tuesday deploy and 70 since.
- Arrivals more than double. Visitors 90 in the first 15 days, 260 in the last 15.
- Brief summarises shipping against traffic. The brief's status line is told to put plain-words figures from connected tools next to what shipped; Plausible supplies visits like any other tool.
Set up
- Select the team that owns the site, open account settings, API Keys.
- Click New API Key, choose Stats API, copy the key (shown once), then Create API Key.
- Note the site domain as Plausible lists it (example.com, no https://).
- Paste the key and the domain into FoxPlug.
What it never reads
- Page-level or source-level breakdowns (only totals and a daily series are requested)
- Other sites in your team (one site id per request)
How it differs
Compared with Fathom, Umami and Simple Analytics, Plausible's v2 query returns visitors, visits, pageviews, bounce rate, visit duration and views per visit in one call, plus a daily series in a second. Its bounce rate and duration come ready-made (duration is a mean). It needs a Business-plan API key and always reads plausible.io.
Do I need a paid Plausible plan?
Plausible's own docs call the Stats API a Business plan feature, so a cheaper paid tier will not do, per FoxPlug's connect guide.
What goes in the site box?
The bare domain exactly as Plausible lists it, such as example.com, with no https:// and no trailing slash.
Does it work with self-hosted Plausible?
The pull's host is fixed to plausible.io, so the code reads only the cloud service. The guide says self-hosted steps match, but the code shows no host setting.
Simple Analytics
A privacy-first, cookie-free web analytics service.
What it reads
- Visitors: visitors over the last 30 days from the Stats API (version 6)
- Pageviews: pageviews total
- Daily histogram: per day: date, visitors and pageviews
Moments
- Visits fall after a deploy. Simple Analytics' daily histogram shows visitors falling from 120 to 70 a day after a Tuesday deploy.
- Arrivals more than double. Histogram visitors 80 in the first half and 210 in the second.
- Fields Simple Analytics does not have. This API has no session, duration or bounce figure, so those fields stay empty and no rule uses them.
Set up
- Open your Simple Analytics account settings (not a site).
- Create an API key; it starts sa_api_key_ (needs a trial or a plan with API access).
- Copy it.
- Note the site as listed, for example example.com without https://.
- Paste the key and the site into FoxPlug.
What it never reads
- Pages, referrers or events (the fields requested are pageviews, visitors and histogram only)
- Sessions, session duration or bounce rate (the API has none)
How it differs
The leanest of the privacy-first group: one call returns only visitors, pageviews and a daily histogram. There are no sessions, no session length and no bounce rate (Plausible, Fathom and Matomo give them), and the key belongs to your user rather than a team.
What is the 'site' field?
The domain exactly as Simple Analytics lists it, such as example.com. FoxPlug strips https:// and any path before using it.
Does a public site need a key?
The code sends the key when one is saved and notes that a public site answers without it, but FoxPlug's connect form requires the key.
What is missing compared with Plausible?
Simple Analytics' Stats API gives no sessions, session duration or bounce rate, so FoxPlug reads only visitors and pageviews.
Umami
An open-source, privacy-focused web analytics tool, run as Umami Cloud or self-hosted.
What it reads
- Visitors: stats.visitors, last 30 days
- Visits: stats.visits (stored as sessions)
- Pageviews: stats.pageviews
- Bounces: stats.bounces, a count; converted to a percentage as bounces divided by visits only when visits is present
- Total time: stats.totaltime; divided by visitors into a mean seconds figure, flagged as a mean
- Daily pageviews and sessions: the /pageviews call with unit=day, timezone UTC
Moments
- Visits fall after a deploy. The brain page describes this rule for any connected tool with a daily series. Caution: Umami's daily rows store pageviews and sessions but an empty visits value (see notes), so do not promise it fires for Umami.
- Bounce count is high against visits. 60 bounces over 150 visits stores 40.0 percent. No rule in the code fires on it.
- Self-hosted install. Leave host blank for Umami Cloud (api.umami.is) or enter https://analytics.example.com.
Set up
- From the side-nav profile button choose Settings, then API keys.
- Click Create key (Umami may ask you to upgrade first).
- Copy the key.
- Open the website; its Website ID is the UUID in the address bar.
- Paste the key, Website ID and, if self-hosted, your host.
What it never reads
- Events, session lists or individual visitor records (two aggregate calls only)
- Other websites in your Umami (a single Website ID is queried)
How it differs
Umami returns bounces as a count and total time as a sum, so FoxPlug converts them (bounces divided by visits; total time divided by visitors, labelled a mean). Plausible and Fathom hand back rates and means directly. Its daily list has sessions and pageviews but no daily visitors, and it can point at a self-hosted host.
Does this work with self-hosted Umami?
The pull supports a host field and sends both header styles. FoxPlug's own guide says the key steps are only confirmed for Umami Cloud.
What is the Website ID?
The UUID in the address bar when you view that website in Umami, not its name.
Why did Umami ask me to upgrade?
FoxPlug's guide notes this gate was seen when creating a key, and it does not attribute it to Umami's documentation.
Vercel Web Analytics
Vercel's built-in visitor and pageview analytics for projects deployed on Vercel.
What it reads
- Daily visitors and pageviews: visits/aggregate by day, up to 100 rows, over 30 days
- Total pageviews: sum of the daily pageviews
- Distinct visitors: visitors summed over a by-device-type breakdown (up to 20 rows); each visitor has one device type on a visit, so it is the distinct count to within people using two devices
Moments
- Visits fall after a deploy. Vercel's daily visitors show 120 a day before a Tuesday deploy and 70 since.
- Arrivals more than halve. Daily visitors 260 in the first half and 90 in the second.
- Vercel was disconnected. The pull fetches the current Vercel token each time, so reconnecting Vercel needs nothing else here.
Set up
- Make sure Vercel is connected under Your deploys.
- In Vercel, check Web Analytics is switched on for the project.
- Open Settings, General and copy the Project ID (starts prj_).
- If a team owns it, copy the Team ID or short name.
- Paste the Project ID (and team) into FoxPlug.
What it never reads
- Preview or development traffic (production only, as Vercel defines it)
- Pages, referrers or countries (only the day and device-type breakdowns are requested)
How it differs
The only tool in this group with no key of its own: it borrows the Vercel deploy connection. It makes two aggregate calls (by day, by device type) and returns only visitors and pageviews, like Simple Analytics, but covers production traffic of one Vercel project and depends on your Vercel plan for look-back.
Do I paste a Vercel token for analytics?
No. FoxPlug uses the Vercel connection you already made under Your deploys and only asks for the Project ID.
Does it count preview deployments?
No. Only production traffic counts, as Vercel defines it.
Why are there no sessions or bounce rate?
The aggregates read give pageviews and visitors only, so session and bounce fields stay empty.
FoxPlug reads this tool only when you press Check for what's new, and only to read. Plans and limits are on the pricing page. Questions: support.