Measurement and Pro reliability

Shipped

• Tightened measurement around first-run setup, routine acquisition, activation, and workout completion.
• Connected public-site intent more cleanly to the app handoff, so a resource page can be judged by whether it helps someone start training.
• Kept private details out of the product analytics layer.
• Hardened the way checkout, trial, cancellation, and subscription state map back into the app.
• Kept Pro access tied to verified subscription state instead of trusting client-side price, plan, or lifecycle claims.

Why

Two parts of the product needed less guessing.

The first is activation. There is a big difference between someone who never opens the app, someone who opens it but cannot find a routine, someone who adds a plan but never activates it, and someone who trains once then disappears. Those are different product problems. They should not collapse into one vague retention number.

The second is Pro access. If someone starts a trial, opens checkout, cancels, or returns to the app after a payment handoff, the app should not infer the important parts from whatever the browser last saw. Subscription state has to come from the trusted side of the system.

Both changes are foundation work. Protocol needs to know whether setup works, and it needs account state to be explainable. It does not need raw workout notes, support message text, private coach context, body data, or sensitive identifiers in product analytics.

Notes

• Measurement is focused on setup, activation, workout completion, and public-to-app handoff.
• Pro state is account-backed and provider-verified before it affects access.
• This does not make Pro required for the core beta workout flow.

Next

• Use cleaner setup signals to decide where routine acquisition needs the next pass.
• Keep public billing copy boring, explicit, and tied to the state the app can verify.