Every client app in one view, each in its own workspace
Metrickle starts from your whole portfolio. See every site and app you run, across every client, with the change against last period and the biggest movers called out. Then drill into any one of them.
| App and platform | Visitors | Change |
|---|---|---|
| northwind.com Web | 22,480 | +9% |
| Northwind iOS iOS | 11,905 | +38% |
| bloom.shop Web | 18,260 | −21% |
| Orbit iOS iOS | 14,730 | +6% |
| acme.com Web | 13,812 | +11% |
| side-project.dev Web | 3,123 | −2% |
Biggest movers: Northwind iOS is up 38% and bloom.shop is down 21%, the only app falling by more than a few points.
Your Monday check-in, in three steps
A walkthrough on a made-up studio portfolio with sample data, including a demo client called Northwind. The portfolio fills in as soon as your apps send their first events.
Scan the portfolio
Every app across every workspace, with visitors, conversion and revenue against the previous period, sparkline trends, DAU, WAU, MAU and stickiness.
Open the mover
The biggest risers and fallers are listed for you. Click through to the app and every chart filters together: pages, sources, campaigns, devices and app versions.
Bring in the client
Invite the client’s team to their own workspace with a link. They see their apps and nothing of anyone else’s.
One workspace per client, with the right people in each
Create a workspace for each client, or one per company if you run your own products. Each holds its own apps, members, goals, funnels and surveys.
You see all of your workspaces together in the portfolio. Your clients see only theirs.
- Owner, admin and member roles. Owners and admins manage apps, keys, members and settings. Members work with the analytics.
- Invite links: invite by email, then share the link with your teammate or client.
- Web and mobile together: a client’s website, iOS and Android apps sit in one workspace and one portfolio.
| Member | Role |
|---|---|
| Studio lead (you) | Owner |
| Developer | Admin |
| Designer | Member |
| Client marketing lead | Member invite pending |
The client sees only the Northwind workspace. Owners and admins manage its apps and keys. Your other clients live in their own workspaces.
Settings you can hand over without worrying
Each app has its own write key and its own list of allowed origins. Events from any other site are refused, so a snippet copied onto the wrong domain doesn’t pollute a client’s data.
Cookieless mode stores nothing on the visitor’s device and never keeps raw IP addresses. Visitors are counted with a salted hash that rotates daily, so client sites don’t need a cookie banner for analytics.
- Rotate write keys any time, for example when a contractor rolls off or a snippet leaks.
- Allowlists include subdomains, so
northwind.comalso coversshop.northwind.com. - DNT and GPC respected, and visitor data can be erased on request.
| App | Allowed origins | Mode |
|---|---|---|
| Website | northwind.com and subdomains | Cookieless |
| Shop | northwind.com and subdomains | Cookieless |
| iOS app | None needed: native apps send no origin | Standard |
Events from any other site are refused, even if someone copies the snippet. The web write key was rotated 3 days ago, and the old one stopped working straight away.
In cookieless mode surveys and replay stay off, because they need memory and consent. Use standard mode on the apps where you want them.
Ask Claude about any client, with your own access
Metrickle is a remote MCP server. Each person creates their own token, and it acts with their role in each workspace, so an assistant can only see the clients that person can see.
Ask for a weekly summary across the portfolio, which client app moved most, or where a client’s checkout leaks. With “read and draft” access it can also draft goals, funnels, tasks and surveys for a person to review.
- Per-user tokens: only a hash is stored, and you can revoke a token at any time.
- Drafts, never deletes: no token can erase data, rotate keys, change settings or manage tokens.
The full product in every workspace
Every client app gets the same research and conversion tools, so you can bring the same playbook to each one.
Conversion optimisation
Funnels, goals, campaign attribution and the biggest leak for each client’s signup or checkout.
UX research
Tasks, friction, journeys, surveys and replay, to show a client why a number moved.
Accessibility
Compare any flow against people using no accessibility settings, for clients with obligations to meet.
Cookieless analytics
No client storage, no raw IPs and no banner for analytics.
AI assistants
Portfolio and per-app questions answered over MCP, with each person’s own access.
Common questions
Can I give a client access to their apps only?
Yes. Put each client’s apps in their own workspace and invite the client as a member. Members see that workspace’s analytics and nothing else. You, as owner or admin of every workspace, see them all together in the portfolio.
How do origin allowlists work with mobile apps?
Allowlists apply to browsers, which send the page’s origin with every request. Native iOS, Android and React Native apps send no origin, so they are accepted with the app’s write key. Keep mobile and web in separate apps and rotate a key if it’s ever exposed.
Do client sites need a cookie banner?
Not for Metrickle in cookieless mode. Add data-cookieless to the script tag and nothing is stored on the device, raw IPs are never kept, and visitors are counted with a daily-rotating salted hash. Surveys and replay stay off in that mode.
If I connect Claude, can it see every client?
It sees what you see. Tokens are personal and act with your role in each workspace. A teammate’s token only reaches the workspaces they belong to, and no token can delete data or change settings.
See where your apps break, and who they break for
Free to start. One script tag on the web, one SDK on mobile, and no cookie banner in cookieless mode.
Start tracking for free