All products
Data Analytics
Connect
Open in MixpanelActive users (last 30 days)
244
+56% vs previous 30 days
Features measured
7 of 9
The rest send no events yet
Key tasks measured
6 of 7
Features with a success event
Tracking plan coverage
47%
38 of 81 planned events arrive
Needs attention
HEART by feature
HealthyWatchPoor
| feature | HHappiness | EEngagement | AAdoption | RRetention | TTask success |
|---|---|---|---|---|---|
| 11, Poor | 6.9 | 43% | — | 67%, Poor | |
| 4.3, Watch | 8.5 | 36% | — | 95%, Healthy | |
| 0.0, Healthy | 29 | 36% | 59%, Healthy | 64%, Poor | |
| 0.1, Healthy | 15 | 28% | 46%, Watch | 88%, Watch | |
| 31, Poor | 11 | 6% | 11%, Poor | 7%, Poor | |
| 0.0, Healthy | 4.8 | 4% | — | — | |
| 4.5 | 33 | 1% | — | 20% | |
 AlertsNot tracked yet | No events reach Mixpanel yet; the tracking plan lists 46. | ||||
 ProfileNot tracked yet | No events reach Mixpanel yet; the tracking plan lists 7. | ||||
How it’s measured
- Happiness
- Errors and cancels per 100 of the feature’s events. There’s no survey yet, so friction stands in.
- Engagement
- The feature’s events per user in the last 30 days.
- Adoption
- Share of Connect’s active users who used the feature in the last 30 days.
- Retention
- Users who came back to the feature the week after their first use, averaged over 8 weekly cohorts.
- Task success
- The feature’s key task: successes out of successes and errors.
From Mixpanel project NXTG Connect PROD, Oct 7 to Nov 6. Each feature is the events whose names start with its prefix; plan names match regardless of spacing and the “(Mobile)” suffix. Anything with fewer than 10 users gets no status.
Tracking plan rules
- All CTA should have an event tied to it
- Need to know if CTA was successful/unsuccessful
- All CTA should give response in 3 seconds
- All pages should load in 3 seconds
- Need to track the type of user (roles)