Mixpanel StrawberryCatch the funnel that has read zero since the mobile release
A weekly pass over every event volume in the project, with anything that fell off a cliff flagged against the release it lines up with. Ten minutes nobody has, run for you.
Product analytics fails quietly. Somebody renames `Signup Completed` to `signup_completed` in a refactor, the funnel keeps rendering, the last step reads zero, and because zero is plausible for a step nobody watches, it stays wrong for a quarter. Then a decision gets made on it.
The pass that catches it is dull: list events by volume, flag anything whose count collapsed, say which release it lines up with. A companion runs that weekly through an account you connect, and reads every event rather than the ten you remembered.
What breaks in a Mixpanel project over time?
Event names, mostly.
Then property names, then property values that were free text and are now an enum with three of the old values still in the data. Each one is invisible in the interface, because Mixpanel shows you what arrived and has no opinion about what should have arrived.
A weekly pass that lists events by volume and flags anything whose count fell off a cliff catches this in days. It takes a person ten minutes they never have, and it is the highest-value thing anyone does with a product analytics tool.
What can a companion do with Mixpanel connected?
The actions Mixpanel’s API exposes, listed in the Available tools section of the Mixpanel entry under `strawberry://settings/integrations`, with the read-only ones marked. Alongside it, the Permissions block sets each action to Ask every time, Always allow, or off.
Any action that writes events or updates user profiles is a data-quality risk rather than a security one. A test event sent into a production project pollutes the dataset permanently, and an ingested event cannot be un-ingested. Leave the write side off unless you have a reason.
- Reads for event volumes, funnels and cohort counts: the low-risk, high-value half.
- Writes that ingest events or set profile properties: permanent, so treat them as consequential.
- A service account scoped to one project rather than an organisation-wide credential.
- Check the Available tools list first, because the published action set is the actual boundary.
Join the drop to the thing that caused it
Mixpanel tells you activation dropped for users who signed up on Tuesday.
It does not tell you that Tuesday is when the onboarding email stopped sending, that a release went out at 14:00, or that support got nine tickets about a broken invite link.
A companion holding the Mixpanel connection plus your signed-in Linear, Sentry and support accounts reads all four and writes the join. The recurring form is a weekly metrics digest, and the diagnostic form is closer to churn analysis.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents