Product analytics in Vexo: segment once, reuse everywhere
Saved segments, funnels, retention, and custom dashboards — built on one shared filter context
August 20, 2026
Jump to section
Most analytics tools make you rebuild the same audience over and over — once for a chart, again for a funnel, again for a retention report. Vexo takes the opposite approach: you define a slice of users once, save it, and every view in the product respects it. Segments, funnels, retention, and custom dashboards all read from the same filter context, so the work you do to narrow down “power users on iOS 18” carries everywhere without a copy-paste.
This post walks through the four pieces of Vexo's product-analytics depth as they ship today, and how they fit together into a single loop: segment, funnel, retain, compose.
Saved segments: define an audience once
Every Vexo view sits behind the same filter bar — date range, app version, operating system, country, and your own custom-event filters. A segment is simply that combination of filters, given a name and saved for reuse. Click the bookmark icon in the filter bar, hit “Save current filters”, name it, and it appears as a pill you can apply with a single click.
The important part is what happens after you apply it. A segment is stored as the exact set of filter parameters it was saved from, and every screen in Vexo reads those same parameters. So a segment you apply on the dashboard carries — unchanged — into session replays, funnels, and retention. You never re-enter the audience; you pick it once and move between views with it intact.
- Save current filters — turn any combination of date, version, OS, country, and custom-event filters into a named segment.
- One-click apply — saved segments show as pills; click to apply, click the
×to remove. - Reused everywhere — the applied segment travels with you across the dashboard, replays, funnels, and retention.
Start broad (“everyone this week”), then save the slices you keep coming back to — a paid-acquisition cohort, a specific app version, users in a single country after a launch. The segment becomes the lens for every other tool below.
Funnels: measure conversion step by step
A funnel in Vexo is an ordered sequence of 2 to 8 steps, where each step is either a Screen or a Custom Event. Pick your steps — for example onboarding → checkout_start → purchase — and Vexo counts how many users progress from one step to the next within a rolling 30-day conversion window.
Each step renders as a bar sized to its conversion percentage relative to the first step, with the raw user count alongside it. The drop between two bars is where you're losing people. Because Screen and Custom Event steps are clickable, you can jump straight from a step to the screens or event behind it and start digging.
- Screen or event steps — mix automatically-tracked screens with your own custom events in one funnel.
- Drag to reorder — grab any step and drop it into a new position; the funnel re-computes on the new order.
- Conversion at a glance — every step shows its user count and its percentage of the entry step.
- Click through — tap a step's number to open the underlying screen or custom-event view.
Apply a segment first and the funnel answers a sharper question: not “how does checkout convert?” but “how does checkout convert for users on the version we shipped last week?”
Retention: are they coming back?
The Retention widget answers the question a funnel can't: once someone shows up, do they return? Vexo groups users into a cohort and reports how many come back on Day 1, Day 7, Day 14, and Day 30 — the classic day-based retention curve.
Each row is one day bucket. It shows the return rate as a percentage, how many users were eligible to return by that day, and how many actually returned. A shaded bar behind each row tracks the rate, and buckets that haven't fully matured yet are drawn lighter so you don't over-read a Day-30 number that isn't complete. Retention needs at least two days of activity before there's anything meaningful to show.
| Bucket | What it tells you |
|---|---|
| Day 1 | Did the first session earn a second one? The earliest signal of an onboarding problem. |
| Day 7 | Whether the app has become part of a weekly habit. |
| Day 14 | Mid-term stickiness — where novelty either converts to habit or fades. |
| Day 30 | Durable retention, the number that predicts long-term growth. |
Retention reads from the same filter context as everything else, so an applied segment reshapes the cohort on the spot. Compare Day 7 for one app version against another, or for one acquisition source against another, without building a separate report.
Custom dashboards: compose the view you actually watch
Segments, funnels, and retention are most useful side by side. Custom dashboards let you place the widgets you care about on one canvas — funnels next to custom-event trends — and arrange them by dragging. Instead of clicking between pages, you build the single screen your team checks every morning.
- Add the widgets you need — funnels and custom-event trend widgets live together on the same board.
- Drag to arrange — reorder widgets (and funnel steps within them) so the layout matches how you read it.
- One shared context — the global filters at the top of the dashboard apply to every widget at once, so changing the date range or app version re-queries the whole board consistently.
A dashboard filtered to a saved segment becomes a purpose-built report: “new users, this release, this country” — with the acquisition funnel, the events they fire, and their retention all answering for the same population.
How the pieces fit together
The four features aren't four separate tools — they're one loop built on a shared filter context:
- Segment the audience you care about and save it.
- Funnel that segment to find where it drops off.
- Retain — check whether the users who convert actually come back.
- Compose a dashboard so the segment, its funnel, and its retention live on one screen.
Because the segment travels through every step, you spend your time reading the data instead of re-defining the audience at each stop.
Getting started
Everything above is available today. Install the Vexo React Native SDK to start capturing screens and custom events, then open your dashboard, apply a filter, and hit the bookmark to save your first segment. From there, add a funnel widget, watch the Retention panel fill in, and arrange the board around the questions your team asks most. New to Vexo? Create a free account and connect your app in a few minutes.
Coming soon: behavioral cohorts with a full retention grid, user-path flow (Sankey) visualization, and formula-based custom metrics are in active development and will build directly on the segment context described here.
Frequently asked questions
What exactly gets saved in a segment?
The current combination of filters — date range, app version, operating system, country, and any custom-event filters — stored under a name you choose. Applying it reapplies that same combination, which is why it carries across every view.
How many steps can a funnel have?
Between 2 and 8, in any order you like. Each step is either a Screen or a Custom Event, and conversion is measured over a rolling 30-day window.
Which retention days does Vexo report?
Day 1, Day 7, Day 14, and Day 30 — the classic day-based cohort model. Each bucket shows the return rate, the number of eligible users, and how many returned. You need at least two days of activity before retention has anything to show.
Do funnels and retention respect my saved segment?
Yes. All of Vexo's product-analytics views read from the same filter context, so an applied segment reshapes your funnels, retention, and dashboards at the same time — no rebuilding the audience per view.
