Metrickle

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.

PortfolioAgency workspace · last 30 days
Apps3
Visitors84,310▲ 13%
Conversion4.8%▲ 0.6 pts
Visitors per app and change against the previous 30 days
App and platformVisitorsChange
quillmere.example Web42,480+9%
Quillmere for iOS iOS23,905+6%
Quillmere for Android Android17,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.

  1. 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.

  2. 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.

  3. 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.
Team & workspaceMembers and app access
Apps12
Members5
Pending invitations1
Members of the agency workspace, their roles and their app access
MemberRoleApp access
Studio lead (you)OwnerAll apps
DeveloperAdminAll apps
DesignerMemberAll apps
Quillmere marketing leadViewerQuillmere’s 3 apps
Quillmere product ownerViewer invitation pendingQuillmere’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.

Show a client the result, in their colours

A share link is a read-only page for people outside the workspace. Send one case, so a client or their developer sees what’s broken, who for and what closes it, or an app’s results: what was fixed and verified, and which stories worked. Links expire, you can revoke them, and they never include recordings, visitor ids or anything people typed.

On Agency, white-label is included. Each app’s feedback widget, surveys and study pages can use the client’s brand colour and drop the “Powered by Metrickle” line.

  • One link per case or per app, emailed from Metrickle or copied and sent yourself, with a count of views.
  • Branding per app, so every client’s widget matches their product.

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.example also covers app.quillmere.example.
  • DNT and GPC respected, and visitor data can be erased on request, per app.
App settings: QuillmereIngest and privacy
Allowed origins and tracking mode for each Quillmere app
AppAllowed originsMode
Web appquillmere.example and subdomainsCookieless
iOS appNone needed: native apps send no originStandard
Android appNone needed: native apps send no originStandard

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.

What every client in the workspace shares

One workspace keeps setup simple, but some things are set once for the whole workspace. Check these before you add a client with strict requirements.

  • One data location. Every app in the workspace is stored in the same place, US or EU. A client who needs a different one needs a workspace of its own, on its own plan.
  • One set of workspace settings: sign-in rules and single sign-on, the retention setting, the warehouse export, the audit log, and the plan and its usage.
  • The member list. Anyone with the Viewer role can see who else is in the workspace. To hide it from clients, give them a custom role without “See members, invites and roles”.
  • Apps can’t move to another workspace yet. If a client takes their analytics in-house, they start a new app in a workspace of their own, and the history stays in yours.

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.

How AI assistants work

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