M-Analytics needs two things to show your site's data: your Matomo server's address, and an API token.
https://analytics.example.com. Paste it however you have it; the app will find the right API path itself.No Matomo server yet? Point the app at https://demo.matomo.cloud with the token anonymous to see it running against live demo data first.
This means your API token can view general site traffic but hasn't been granted access to identify individual logged-in users. Everything else in the app keeps working — only the Recent Users panel and the map's member markers depend on that permission. If you want that data too, ask whoever manages your Matomo installation for a token with broader access.
The Recent Users panel is built on Matomo's User ID, and a stock WordPress install doesn't record one — it has to be set explicitly. If your site runs the Matomo for WordPress plugin, turn on its "Track User ID" setting and it will set the User ID to each visitor's WP username automatically the moment they log in. You'll also need the Live plugin enabled on the Matomo side, and an API token with access to the userId segment (see the permission question above). Once those are in place, logged-in members start showing up in Recent Users and as member markers on the visitor map — visitors who never log in still won't have a User ID, which is expected.
Not using that plugin — a manual tracking snippet, a different Matomo integration, or another CMS? Call setUserId before the tracker's page-view call, for any logged-in user, with whatever identifier you want to see in the panel (a username, an account ID — it doesn't have to be the WP username):
_paq.push(['setUserId', currentUserIdentifier]);
_paq.push(['trackPageView']);
Only add this where you already know who's logged in — typically inside a template conditional, so logged-out visitors never get a User ID set for them.
If a report gets enabled on your Matomo server after the day's archives were already built, Matomo doesn't retroactively fill in that history — it only starts appearing from the next scheduled archiving run onward. This isn't a bug in the app; it's how Matomo's archiving works. Check back after Matomo's next archiving pass, or ask your Matomo admin to trigger one manually.
Yes. The app allows plain HTTP connections specifically for this case — a self-hosted install on a local network often doesn't have a certificate. Just enter the address as-is.
No — they're separate apps with separate storage, so your server, token, and preferences are set up independently on each device. This is also true for privacy: nothing you enter on one device is visible to the other, or to us.
Actions counts every interaction Matomo tracks — pageviews, downloads, outbound link clicks, events, and site searches. Pageviews is just the page-load count on its own, so it's normal for it to be the smaller of the two.
In Settings → Panels, toggle off anything you don't want to see. On the Mac, this only affects the menu bar popover — the full window always shows everything, and panels there can be dragged to reorder. On iPhone, hidden panels also stop appearing in the scrolling dashboard, but keep updating in the background so they're current if you turn them back on.
Send a description of what you're seeing, and your Matomo version if you know it: