For health & fitness apps
Missed workouts don't wait for your next release.
Offer an easier plan after missed runs. Ask for a rating after a personal best. No app update needed.
Third missed workout: a sheet offers an easier plan.
Five moments a fitness app should not miss.
On a beginner plan
A sheet offers an easier plan
Anyone, once
A card asks for a rating
Finished week one
Three story slides recap the week
New installs
A full-screen flow asks for a goal
Updated to the new version
A What's new screen shows the interval timer
Every format lands on the app you already ship.
Sheets keep the workout in view. Cards ask one thing. Stories and full screens take over when the moment is big.
Slides up from the bottom. The app stays visible behind it.
Design it. Pick the moment. Pick the people.
Try an easier plan
3 runs a week
Not now
Design
Build the sheet in the visual builder. No code, no release.
Trigger
Choose the event that opens it, like the third skipped workout.
Audience
Decide who sees it. Everyone else keeps training undisturbed.
Questions fitness teams ask.
One SDK: init, track() for the events you already log (workouts, plans, purchases), and a deeplink listener. From signup to live test in a day. The optional MCP + integration skill produce the wiring as a reviewable diff.
No. Once a build with the Amply SDK is live, you create, change and stop campaigns from the dashboard. Sheets, cards, stories and full screens made in the builder reach that build without another App Store or Google Play review.
No. Amply sees only the events and properties your app chooses to send, such as WorkoutCompleted or the plan a user is on. Target on those facts and keep sensitive health values out of the events.
Session state, device context (OS, app version, country), the user id and custom properties your app sets, a rolling buffer of recent events, and the published config cached for offline. Not a data warehouse: it stores what a decision needs and nothing else. Payment data, your analytics history, and anything your app doesn't explicitly send never reach Amply.
The app falls back to the default behavior you shipped. No matching campaign, no config, servers down: the worst case is your app as it is today.
FALLBACKapp as shippedStill have questions? [email protected]
Your next fitness campaign doesn't need a release.
Integrate the SDK once. After that, sheets, cards, stories and full screens go live from the dashboard.