| Page Properties |
|---|
| Document status | |
|---|
| Document owner | |
|---|
|
Overview
We communicate with Wonder (7MW) users over their journey, via a few mechanisms. This doc outlines the content of these communications.
The systems required for delivery of these communications are covered by Journey Triggers and
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 0698f136-3f0e-3c87-aa9c-4d9605606272 |
|---|
| key | AF-61 |
|---|
|
.Communication Types
- Scheduled notifications
- Post-workout activity articlesarticle sequence
- Post-workout notifications
Scheduled notifications
...
A sequence of APNs are scheduled for each user, to be delivered based on numbers of days since first run. The purpose is to improve retention by providing tips and motivation regardless of workout activity. They are triggered by the Journey Trigger system and full model data is in this Google Docs sheet. They are delivered as follows:
Post-workout activity article sequence
Post-workout activity article sequence
Full-form articles are sent to the user after workouts. Full They are triggered by the Journey Trigger system and full model data is in this Google Docs sheet. They are triggered delivered as follows:
For Original 7MW routine:
For Supercharged routine:
For all routines: