Catch the release that costs a client conversions
When a release costs a client sign-ups or sales, you want to see it first, with who it hit and what it costs. Metrickle puts every client’s web and mobile apps in one workspace with a portfolio across all of them, and gives each client a view of their own apps only.
| App and platform | Visitors | Change |
|---|---|---|
| quillmere.example Web | 42,480 | +9% |
| Quillmere for iOS iOS | 23,905 | +6% |
| Quillmere for Android Android | 17,925 | +38% |
Biggest mover: Quillmere for Android is up 38%, while the web and iOS apps moved by single digits.
Your Monday check-in, in three steps
A walkthrough on a made-up studio’s portfolio with sample data, built around a fictional client, Quillmere, and its web, iOS and Android apps. The portfolio fills in as soon as your apps send their first events.
Scan the portfolio
Every app you run, across every client, with visitors, conversion and revenue against the previous period, the latest release verdict and how each protected task is doing.
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 as Viewers limited to their own apps, or send a read-only link to one case or to their results. They see their apps and nothing of anyone else’s.
One workspace, with an app for each client product
Add each client’s website, iOS app and Android app as apps in your Agency workspace. Each app has its own write key, allowed origins, goals, funnels, protected tasks, surveys and integrations, so clients never share a setting that matters to their data.
Then choose who sees what. Under App access, limit each person to some apps: they see only those apps, in the dashboard, the API and notifications.
- Invite clients as Viewers. Viewers read results but can’t watch replays, see feedback screenshots or study participants’ details, or export raw events. Keep Member for your own team: members can do all of those.
- Limit each client to their apps. When you add another app for a client, add it to their access too.
- Custom roles for anything in between, such as a client who can triage feedback but change nothing else.
| Member | Role | App access |
|---|---|---|
| Studio lead (you) | Owner | All apps |
| Developer | Admin | All apps |
| Designer | Member | All apps |
| Quillmere marketing lead | Viewer | Quillmere’s 3 apps |
| Quillmere product owner | Viewer invitation pending | Quillmere’s 3 apps |
Quillmere’s team sees Quillmere’s three apps and nothing else. Your other clients’ apps don’t show up for them in the dashboard, the API or notifications.
Alerts and issues land where each client works
Integrations are set up per app, so each client’s alerts and issues go to their own channel and project, not one shared inbox.
- Slack, Teams and webhooks per app: a client’s release drops and task gaps post to their channel.
- Issue trackers per app: connect the client’s Jira, Linear, GitHub or other tracker account, and each app files into its own project or repository.
- Revenue per app: connect each client’s own Stripe or RevenueCat account, so the money lost so far is theirs.
- Releases per app: each app gets its own deploy hook, and native apps record a release for each new version on their own.
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. Native iOS, Android and React Native apps send no origin and are accepted on their write key alone, so keep web and mobile as separate apps.
Add data-cookieless to the script tag for cookieless mode: it 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
quillmere.examplealso coversapp.quillmere.example. - DNT and GPC respected, and visitor data can be erased on request, per app.
| App | Allowed origins | Mode |
|---|---|---|
| Web app | quillmere.example and subdomains | Cookieless |
| iOS app | None needed: native apps send no origin | Standard |
| Android 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 an AI assistant about any client, with your own access
Connect an AI assistant to Metrickle and it acts with your role and your app access. A client’s Viewer who connects one only reaches their own apps.
Ask for a weekly summary across the portfolio, which client app moved most, or where a client’s checkout loses people. With “read and draft” access it can also save goals and funnels, and draft tasks and surveys for a person to review.
- Per-person access: only a hash of each token is stored, and you can disconnect an assistant or revoke a token at any time.
- Never erases data: no assistant can erase a visitor’s data, delete an app, rotate keys, change settings or manage tokens. The most it can remove is a goal, a funnel, a release or a task draft.
The full product for every client app
Every client app gets the same research and conversion tools, so you can bring the same playbook to each one.
Release verdicts
Whether a client’s release cost them sign-ups or sales, what that costs a month, and who it hit.
Conversion optimisation
Funnels, goals, campaign attribution and the biggest drop-off in each client’s sign-up or checkout.
UX research
Tasks, friction, journeys, surveys, studies and replay, to show a client why a number moved.
Accessibility
Compare any task with people using no accessibility settings, for clients with obligations to meet.
Cookieless analytics
No client storage, no raw IPs and no cookie banner for analytics in cookieless mode.
Security
How data is stored, who can reach it, and how keys and tokens are handled.
See which release is costing you conversions, and who it broke for
Free to start. One script tag on the web, one SDK on mobile, and no cookie banner in cookieless mode.
Start free