Plans & Programs
Events for workout plans and programs.
| Event | Data Fields | Description |
| plan_opened | id: string | A plan's details loaded: the plan page and its week page, and the plan onboarding result (goal-based and personalized plans). Sent each time the plan is fetched, so it can repeat for the same plan; dedupe on id |
| plan_workout_selected | workout_id: string, workout_title: string, plan_id: string, plan_title: string | User tapped a workout inside a plan (sent when the plan's id and title are known) |
| plan_onboarding_question_answered | data: { question: string, answer: any } | One plan-onboarding answer. question is "goal", "health_issues", "injuries", "duration" or "lifestyle". answer is a string for goal, a string array for health_issues and injuries, a number or null for duration, a string or null for lifestyle |
| plan_onboarding_survey_completed | data: { goal, healthIssues, injuries, duration, lifestyle } | The plan-onboarding survey is finished. data holds all answers (note the camelCase healthIssues) |
| plan_onboarding_plan_created | data: { plan_id: string, plan_type: string } | A new plan was created from onboarding/assessment. plan_type is "goal-based" or "personalized". Does NOT fire on revisits to an existing personalized plan |
| plan_progression_saved | data: { planType: string, weekNumber: number, dayNumber: number, source?: string } | Plan day progression was saved successfully after a plan workout finished. planType is "goal-based" or "personalized". source: "offline_outbox" is present only when the save was recovered after a lost connection; live saves omit it |
| plan_progression_failed | data: { planType: string, error: string } | Plan progression save failed (network/server error) |
| personalized_plan_exit | data: { workout: string, date: string } | The user left the results screen of a personalized plan workout (after workout_completed); KinesteX goes back to the plan |
| remind_me_later_clicked | - | User tapped "Remind me later" on the Assessment screen inside the plan-onboarding flow. Only fires from the plan-onboarding page |
Note on plan tracking: When you launch a plan workout directly via the SDK, you can pass planId, planType, and progressWorkoutId in the initial PostMessage configuration so the SDK associates the workout session with the correct plan. After the workout finishes, you'll receive either plan_progression_saved (success) or plan_progression_failed (error). See Plan Context configuration for details.
Offline save recovery: if a save fails (e.g. the user loses connection on the results screen), the result is stored locally and automatically re-sent when the connection returns or the app is reopened. plan_progression_saved (and workout_session_saved) can therefore arrive after a delay instead of only at save time: make your handler idempotent and treat source as optional.