Identity created. This starts the measured funnel, but it is not setup complete.
The outcome we want (lagging metrics)
The scoreboard. These tell us whether COPY is becoming a repeat behavior, not just a thing people try once.
Repeat conversations
Conversations people came back to, not just tried once.
47%
up 10 percentage points
Good
Repeat conversations
Conversations people came back to, not just tried once.
Means: active conversations in the last 28 days that also had voice activity before this 28-day window divided by all active conversations in the last 28 days. Window: Jul 11, 2026 12:00 AM to Aug 7, 2026, 2:41 PM MST.
Read: Good: Repeat conversations is moving in the right direction (up 10 percentage points vs comparison).
Week-4 message-active retention
Shows whether newly registered devices keep finding value after the novelty window.
3%
flat
Watch
Week-4 message-active retention
Shows whether newly registered devices keep finding value after the novelty window.
Means: registered devices in a signup cohort that were message-active four weeks after registration divided by registered devices in the same signup cohort. Window: mature signup cohorts only; newer cohorts show a dash until enough time has passed. Message-active means sent, played, or acknowledged a message.
Read: Watch: Week-4 message-active retention is roughly steady or not decisive (flat vs comparison).
2+ people participated
Conversations are more valuable when another person actually joins in.
92%
up 3 percentage points
Watch
2+ people participated
Conversations are more valuable when another person actually joins in.
Means: active conversations where at least two registered devices sent, played, or acknowledged a message divided by all active conversations in the last 28 days. Window: Jul 11, 2026 12:00 AM to Aug 7, 2026, 2:41 PM MST. This means two people participated; it does not necessarily mean both people sent messages back and forth.
Read: Watch: 2+ people participated is roughly steady or not decisive (up 3 percentage points vs comparison).
Invite reproduction
Measures whether accepted invitees later create their own invite within 24 hours.
28%
up 2 percentage points
Watch
Invite reproduction
Measures whether accepted invitees later create their own invite within 24 hours.
Means: registered devices that accepted an invite and then created another invite within 24 hours divided by registered devices that accepted an invite in the last 28 days. Window: Jul 11, 2026 12:00 AM to Aug 7, 2026, 2:41 PM MST. This is anonymized device-level behavior, not a person-level social graph.
Read: Watch: Invite reproduction is roughly steady or not decisive (up 2 percentage points vs comparison).
The signals we think predict it (leading metrics)
The levers. These are earlier behaviors we can improve now and test against the scoreboard later.
First conversation within 24h
Early channel creation is the first sign that setup turned into intent.
57%
up 3 percentage points
Watch
First conversation within 24h
Early channel creation is the first sign that setup turned into intent.
Means: newly registered devices that started a conversation within 24 hours of registration divided by newly registered devices in the last 28 days. Window: Jul 11, 2026 12:00 AM to Aug 7, 2026, 2:41 PM MST.
Read: Watch: First conversation within 24h is roughly steady or not decisive (up 3 percentage points vs comparison).
Invite events (activity ratio)
Raw invite event volume. The matched acceptance floor below is the conversion read.
15%
down 14 percentage points
Context only
Invite events (activity ratio)
Raw invite event volume. The matched acceptance floor below is the conversion read.
Means: invite_accepted events divided by invite_created events. Window: Jul 11, 2026 12:00 AM to Aug 7, 2026, 2:41 PM MST. Activity, not conversion: creations fire before the share sheet opens and re-fire on re-issues, accepts are unmatched to their invite, and recent invites have not matured. Use the historical acceptance floor for conversion.
Read: Unknown: Invite events (activity ratio) needs more sample before reading the movement.
First playback milestone
Playback is the first evidence that voice reached the other side.
21%
down 13 percentage points
Needs focus
First playback milestone
Playback is the first evidence that voice reached the other side.
Means: newly registered devices that reached the first-message-received milestone divided by newly registered devices in the last 28 days. Window: Jul 11, 2026 12:00 AM to Aug 7, 2026, 2:41 PM MST. This is a milestone proxy for first playback, not a complete message-by-message play rate.
Read: Needs focus: First playback milestone is moving the wrong way (down 13 percentage points vs comparison).
Second person participated
The strongest hunch for a durable conversation is another person participating.
92%
up 3 percentage points
Watch
Second person participated
The strongest hunch for a durable conversation is another person participating.
Means: active conversations where at least two registered devices sent, played, or acknowledged a message divided by all active conversations in the last 28 days. Window: Jul 11, 2026 12:00 AM to Aug 7, 2026, 2:41 PM MST. This is participation, not a strict back-and-forth sender count.
Read: Watch: Second person participated is roughly steady or not decisive (up 3 percentage points vs comparison).
Historical acceptance floor (mature matched cohort)
Of fresh 1:1 invite channels created at least 7 days ago, the share that gained a second participant within 7 days. The channel and inviter floors only count creations made after second-participant instrumentation went live; earlier channels cannot be judged on an event that did not exist yet. This is a floor, not delivered-invite conversion: dismissed share sheets stay in the denominator. Full audit data ships beside this page as the invite-floor artifact.
The floors
| Channel floor (second participant, post-instrumentation cohort) | unavailable (sampled data; 9 of 97 raw, diagnostic only) |
|---|---|
| Corroborating floor (invite accepted, full window) | unavailable (sampled data; 100 of 478 raw, diagnostic only) |
| Inviter success floor (post-instrumentation cohort) | unavailable (sampled data; 8 of 54 raw, diagnostic only) |
| Fan-out failures (28d) | 0 |
| Redemption latency p50 / p95 (ok) | 326 ms / 2,975 ms |
Server redemption outcomes (28d)
| Outcome | Count | Share |
|---|---|---|
| ok | 62 | 100% |
Latency counts, shares, and percentiles are weighted by Analytics Engine sampling intervals (max interval 2).
Cohort audit waterfall
| Filter step | Rows | Weighted |
|---|---|---|
| All invite_created rows in window | 564 | 582 |
| Source is create_and_invite (excludes group add-member re-shares) | 496 | 514 |
| Channel type is 1:1 | 496 | 514 |
| Fresh token only (existing = 0 drops idempotent re-issues) | 496 | 514 |
| One member at creation | 496 | 514 |
| Deduplicated by anonymized channel prefix | 496 | 514 |
| Created at least 7 days before the reporting cutoff | 478 | 492 |
| Created after second-participant instrumentation went live (channel/inviter floors only) | 97 | 105 |
Duplicate creation rows dropped: 0. Channel prefixes seen under multiple inviters: 0. Sampling NOT verified (max interval 2).
This is a historical floor, not delivered-invite conversion: dismissed share sheets cannot be removed from the denominator with historical data.
Identities and channels are 8-character anonymized prefixes; collisions are detected and reported but cannot be repaired.
Analytics Engine sampling detected (max _sample_interval 2). Matched floors are unavailable: creation and outcome rows sample independently, so a missing outcome row is indistinguishable from a real non-conversion. Counts and weights are published for diagnosis only.
Onboarding / activation
The path from identity creation to real use. Registered device means an identity was created. It is not the same as fully completing onboarding.
Permission setup failures are a reliability guardrail. Lower is better; zero is the goal.
83 devices started a conversation within 24 hours.
43 new devices reached first-message-sent.
30 new devices reached first-message-received.
Share of active conversations with at least two participating devices.
Coarse mic/push bridge failures. Lower is better; zero is the target.
What people do in the app
The last 28 days. Reach is the share of devices with a measured product session that did each action at least once.
101 devices across 1,103 measured sessions.
Who found the main customization surface. People who did this averaged 4.7 times.
Who moved from settings into appearance choices. People who did this averaged 3.1 times.
Who actually applied a different skin. People who did this averaged 2.9 times.
Who applied a different color variant. People who did this averaged 1.8 times.
Who moved the dial to another channel at least once. People who did this averaged 20.2 times.
Platform
Activity split by the platform prefix on updated app builds. Legacy rows stay visible instead of being guessed.
| Platform | Active devices | Sessions | Messages |
|---|---|---|---|
| iOS | 139 | 1,091 | 2,061 |
| Android | 3 | 12 | 15 |
Age of active devices
Days between registration and the latest measured session in this window. Limited to registrations in the 90-day report history.
| Device age | Active devices |
|---|---|
| 0-6 days | 33 |
| 7-13 days | 12 |
| 14-27 days | 16 |
| 28+ days | 24 |
Unlock progression
5 of 123 observed active identities completed all three (4%). Completion includes an earned achievement with no reward available, so progress is not mistaken for a missing claim.
| Unlock | Locked | Earned | Claimed | Completed |
|---|---|---|---|---|
| First Contact | 59 not earned | 33 ready to claim | 30 claimed a reward | 31 (25% complete) |
| Three's Company | 98 not earned | 18 ready to claim | 6 claimed a reward | 7 (6% complete) |
| Operator | 100 not earned | 14 ready to claim | 9 claimed a reward | 9 (7% complete) |
Usage over time
Weekly conversation activity. Default is 90 days; use shorter views to inspect recent movement.
Cohort retention
Percent of each signup cohort that was message-active in later weeks. A dash means that week has not happened yet.
| Signup week | W0 | W1 | W2 | W4 |
|---|---|---|---|---|
| Jun 27-Jul 3 74 | 53% | 5% | 4% | 3% |
| Jul 4-Jul 10 58 | 24% | 2% | 0% | - |
| Jul 11-Jul 17 77 | 39% | 9% | 4% | - |
| Jul 18-Jul 24 39 | 26% | 3% | - | - |
| Jul 25-Jul 31 16 | 19% | - | - | - |
| Aug 1-Aug 7 14 | - | - | - | - |
Hypothesis tracker
These are beliefs we are testing, not facts we should overstate.
| Hypothesis | Rationale | Evidence | Status |
|---|---|---|---|
| Groups retain better | Group channels create more chances for repeat voice use. | 17% of sends are in group conversations. | Mixed |
| Fast social activation matters | Channels become useful when another person joins quickly. | The mature matched invite floor is not yet quotable. The raw accept-to-create ratio is activity only, not conversion. | Unknown |
| Second participant predicts return | A conversation with two participating people is more likely to become repeat use. | 92% of active conversations had 2+ people participate. | Mixed |
| Playback closes activation | A sent voice note matters more when someone hears it. | 21% first playback milestone rate. | Mixed |
Focus this week
Three practical reads from the current data. These are meant to guide product attention, not to be public copy.
Repeat conversations
Repeat conversations is currently marked good. Keep the work that supports this moving.
First playback milestone
First playback milestone is the clearest improvement area. Treat it as this week's product question.
First conversation within 24h
First conversation within 24h is watch. Watch it, but do not make it the whole story yet.
Social Pulls
Short lines Matt can send Alan or post as-is. They keep the numbers, but they should still sound like COPY and not like a dashboard.
47% of active COPY conversations in the last 28 days were repeat conversations. People are coming back to the same channel. That matters more than a one-off spike.
57% of new devices started a conversation within 24 hours. The first day still decides whether COPY feels alive or just feels like setup.
21% of new devices reached first playback. A sent note starts to matter when somebody actually hears it.
Metric glossary
Definitions used throughout this page. Counts are anonymized device or channel signals, not named people.
- Leading metric
- An earlier behavior we believe should predict a better product outcome later. These are hypotheses, not proof.
- Lagging metric
- An outcome that tells us whether COPY is already becoming useful and repeatable. It usually moves after the product experience changes.
- Percentage point
- The direct difference between two percentages. Moving from 20% to 30% is up 10 percentage points, not up 10%.
- Message-active identity
- An anonymized device identity that sent, played, or acknowledged a message during the window.
- Active conversation
- A conversation with voice activity during the window. This is a channel-level behavior, not a person count.
- Repeat conversation
- An active conversation that also had voice activity before the current window. This is the main repeat-behavior proxy.
- New conversation
- An active conversation with no earlier voice activity observed before the current week in this 90-day view.
- 2+ people participated
- A conversation where at least two anonymized identities sent, played, or acknowledged a message during the window. This is participation, not necessarily two-way sending.
- Cohort retention
- For each signup week, the share of those devices that were message-active in week 0, week 1, week 2, or week 4 after signup.
- WAU / MAU
- Weekly message-active identities divided by 28-day message-active identities. Higher means more of the recent audience is active this week.
- Registered device
- A device identity created on the server. This starts the measurable onboarding funnel, but does not prove the person finished setup.
- Onboarding permission failure
- A coarse mic or push permission bridge failure mirrored from client diagnostics. It excludes raw native error text and should be read as a reliability guardrail.
Archive policy
Pulse is the rolling live read. Weekly and monthly scorecards are frozen to completed Phoenix periods, with dated URLs so the comparison does not move after the period closes. The public archive is regenerated from recent Analytics Engine history each night; GitHub artifacts and Cloudflare deployments remain the deeper audit trail.