Metrickle

Find the release that cost you conversions, then find out why

Every release gets a verdict on what it cost you in sign-ups and sales, and who it hit. Around that, Metrickle puts conversion and UX research for all your web and mobile apps in one place: start from the whole portfolio, drill into one app, then see where the experience breaks and who it breaks for.

PortfolioAll workspaces · last 30 days
Visitors69,500▲ 20%
Conversion5.2%▲ 0.6 pts
Stickiness29%▼ 1 pt
Visitors per app with the change on the previous 30 days
AppPlatformVisitorsChange
quillmere.example (biggest mover)Web48.2k▲ 27%
Quillmere iOSiOS12.9k▲ 9%
Quillmere AndroidAndroid8.4k▲ 4%

The biggest mover comes first. Click any app to open its own dashboard.

Pick the question you need answered

Each guide covers what the feature measures, how it works and what it deliberately leaves out.

Release verdicts

A verdict on every release: did it cost you sign-ups, sales or onboarding, what that costs a month, and which browsers, devices or accessibility settings it hit.

Protected tasks

Protect the tasks that make you money. After every release, see whether everyone still gets through, including people using an accessibility setting, and get a case with the revenue lost so far and, on paid plans, the recordings when one breaks.

Funnels and goals

Goals from any event or page, funnels of two to ten steps with drop-off and median time per step, and the biggest drop-off named.

Friction report

Eight signals, from rage, dead and error clicks to slow controls, u-turns, up-and-down scrolling, form errors and form abandons, captured automatically and ranked by element and page.

User journeys

How people really move through your site or app, anchored at any page or screen, filtered by accessibility setting, device or survey answer.

In-app surveys

NPS, CSAT, effort, rating, choice and open-text surveys, targeted and timed, plus an always-on “report a problem” widget.

Heatmaps and replay

Click heatmaps and scroll depth per device width, and session replay that is opt-in, consent-gated and masked by default. On the web, from Growth.

Integrations

Feedback and alerts in Slack or Teams, issues in Jira, Linear, GitHub, GitLab, Azure DevOps, Asana and more, release markers, and whether each fix worked.

AI assistants (MCP)

A remote MCP server: ask your AI assistant about your analytics and let it save funnels, and draft tasks to protect, fixes and surveys for you to review.

Cookieless analytics

Nothing stored on the device, a daily-rotating salted hash instead of an id, and raw IP addresses never stored.

Every app you run, on one screen

Most analytics tools show one app at a time. Metrickle starts with all of them: every app across every workspace, each with its change on the previous period and a trend line, and the biggest movers surfaced for you.

  • DAU, WAU, MAU and stickiness across the portfolio.
  • New versus returning visitors per app and in total.
  • Roles and app access: owner, admin, member and viewer roles, custom roles, and people limited to the apps they need, such as a client who sees only theirs.

See your portfolio

Drill into one app, then one page

Each app has its own dashboard. Click any row to filter every chart by it, so “visitors are up” becomes “this campaign’s visitors are leaving at pricing” in a couple of clicks.

The numbers

Visitors, sessions, bounce rate, session length, conversions, conversion rate and revenue, compared with the previous period.

Breakdowns

Pages, entry and exit pages, referrers, UTM source, medium and campaign, country, device, browser, OS, app version and events.

Journeys and retention

Sankey journey flows anchored at any page, daily and weekly retention cohorts, per-visitor timelines and a live event stream.

Tasks

Success rate, median time on task, how long the slowest 10% take, and where abandoned attempts stopped.

Accessibility settings

Every event carries the settings seen on the device, so any report splits by keyboard navigation, zoom, large text or reduced motion.

Built for client work

Every client’s apps in one workspace, each client limited to their own, with the whole portfolio still in view.

One line on the web. One SDK on mobile.

Pick the option that fits each app. They all send the same events, so web and mobile apps sit side by side in the portfolio.

  • Script tag: about 16 KB gzipped and deferred. Pageviews, single-page app navigations, web vitals, outbound links, JS errors, friction and accessibility settings are automatic.
  • npm package for bundled web apps, with the same options as the script tag.
  • React Native SDK for iOS and Android apps built with React Native, including rage taps, u-turns, form errors, headless surveys and feedback.
  • Native SDKs for iOS (Swift Package Manager), Android (Maven Central, with Compose helpers) and Flutter (pub.dev), with automatic screens, rage taps, dead taps, u-turns, form errors, surveys in an accessible native sheet, and feedback with a built-in “report a problem” sheet.
  • HTTP batch protocol for servers and anything else.
  • Extra code loads only when used: heatmaps, replay and the feedback widget are switched on per app under Settings → Research, and surveys go live from the Surveys page. Until then their code stays off the page.
<!-- Web: script tag, about 16 KB gzipped -->
<script defer
  src="https://app.metrickle.com/m.js"
  data-key="mk_pub_…"></script>

// Web: npm
import { init } from "@metrickle/sdk";
init({ writeKey: "mk_pub_…" });

// React Native
import { init } from "@metrickle/sdk/react-native";

# iOS: Swift Package Manager
https://github.com/metrickle/metrickle-swift

// Android: Maven Central
implementation("com.metrickle:metrickle:0.2.0")

# Flutter: pub.dev
flutter pub add metrickle

# Servers and anything else: HTTP
POST https://in.metrickle.com/v1/batch

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