For mobile games
Lapsed players don't wait for your next update.
Offer a starter pack after a failed level. Welcome lapsed players back. No app update needed.
Third failed attempt: a sheet offers a starter pack.
Five moments a game should not miss.
Players who never paid
A sheet offers a starter pack
Anyone, once
A card opens the level 10 reward
Lapsed players
Three story slides show what changed while they were away
New installs
A short survey saves how they like to play
Updated to the new version
A What's new screen opens the new season
Every format lands on the game you already ship.
Sheets keep the board in view. Cards ask one thing. Stories and full screens take over between rounds.
Slides up from the bottom. The app stays visible behind it.
Design it. Pick the moment. Pick the players.
Try an easier plan
3 runs a week
Not now
Design
Build the offer sheet in the visual builder. No code, no release.
Trigger
Choose the event that opens it, like the third failed attempt at a level.
Audience
Decide who sees it. Paying players keep playing undisturbed.
Questions game teams ask.
One SDK: init, track(), a deeplink listener. Most campaigns reuse events and deeplinks that already exist. 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.
Yes. A survey made in the builder saves each answer as a custom property on that user. Later campaigns target on it, so someone who picked a goal or a play style gets the offer that fits it.
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 live-ops campaign doesn't need a release.
Integrate the SDK once. After that, offers, rewards and season screens go live from the dashboard.