Data & Analytics
A metric dropped. Know where to look in minutes.
When a metric moves unexpectedly, ZeroTwo queries your database and decomposes it across every available dimension: geography, plan type, acquisition channel, device, signup cohort.
What changes
Time to isolate segment
Half a day to a full day of manual investigation
ZeroTwo checks every dimension and reports the driving segment
Dimensions checked
Whatever the analyst thinks to check, one at a time
Every available dimension in schema tested
Traceability
An answer with no way to verify it
Every decomposition query and result attached
Analyst time
A full day on one question, everything else blocked
Segment identification automated; analyst focuses on fix
Activation is down 12%. Can you look into it?
You manually segment data by plan type, geography, channel, device, browser, and cohort. The process takes approximately four hours of investigation to narrow results, ultimately identifying that the drop is concentrated in free-tier signups from organic search on mobile.
Finding the segment took a full day. Actually fixing the issue takes 30 minutes once you know where to look. The investigation is the bottleneck, and it blocks everything else on the analyst's plate.
How ZeroTwo investigates metric changes
Parses the question and plans a dimensional decomposition
GoogleZeroTwo identifies the metric, timeframe, and magnitude, then maps every available dimension in your schema for systematic testing.
Decomposes the metric across every segment
SupabaseActivation rate computed by plan type, geography, channel, device, browser, and signup week. Each dimension tested for whether it explains the decline. SQL logged.
Isolates the segment driving the change
GoogleZeroTwo pinpoints which segment accounts for most of the decline -- or reports that the drop is broad-based. Intersections like 'mobile AND free-tier' are tested too.
Posts the investigation to your channel
SlackZeroTwo delivers the driving segment, its contribution magnitude, and when the drop started -- with every decomposition query attached for verification.
Get started in under 10 minutes
Connect your tools
One-click OAuth for each integration. No API keys, no engineering.
Describe what you need
“Daily active users dropped 12% this week. Check every dimension -- plan tier, geography, device type, signup cohort -- and tell me which segments drove the decline.”
It runs on schedule
On demand. Ask whenever a number moves and the answer lands in minutes.
Frequently asked questions
ZeroTwo identifies which segment is driving the metric change: which plan type, geography, channel, device, etc. This narrows the investigation from 'why did activation drop?' to 'why did activation drop for free-tier mobile users from organic search?'
ZeroTwo reads your schema during setup and catalogs available columns. When you ask about a metric change, it decomposes across all dimensions automatically.
ZeroTwo tests combinations. If the drop is specific to 'mobile AND free-tier AND organic' but not 'mobile' alone, it reports the intersection. Segments are ranked by magnitude of overall change they account for.
Yes. Every decomposition query is logged with the SQL, execution time, row count, and result. You can re-run any query manually or extend the investigation by editing the SQL.
Any metric derivable from your database. Activation, revenue per user, conversion rate, feature adoption. You describe the metric in plain language and ZeroTwo maps it to the right columns and tables.
Related workflows
- Data & AnalyticsData Quality Monitor
- Data & AnalyticsFunnel & Behavior Analysis
- Data & AnalyticsScenario Modeling
Stop doing the work your tools should do for you.
Set it up once. ZeroTwo runs it every time.