Decide which experience each user gets,
without an app release.
Your app already has the screens and actions. Amply decides who sees each one, and when, from a dashboard your growth team owns.
iOS
Android
React Native
Unity(soon)
Flutter(soon)Live campaigns running on Amply.
Happens
Rate review promptWhen
this event fires
MoodTracked
Who
matches this audience
All users
What
gets triggered
Native review prompt
RateReview
StillFrame
Rewarded ad gateWhen
this event fires
ExportTapped
Who
matches this audience
is_premium
(Boolean)
=
false
What
gets triggered
Rewarded ad
stillframe://rewarded-ad/export
Seabook
Premium upsellWhen
this event fires
DiveLogged
Who
matches this audience
is_premium
(Boolean)
=
false
What
gets triggered
Premium intro
seabook://premium/intro
Connect events once, launch campaigns anytime.
The setup autopilot wires Amply into your app and dashboard once. Growth then turns those signals into experiments — paywalls, surveys, offers — without another release.
Connect
Engineering Team
Run the setup autopilot in your editor. It installs the SDK, wires up events, and provisions your dashboard — one engineering sign-off, no integration sprint.
Create
Growth Team
Create campaigns in the dashboard. Pick the audience, the trigger, and the action — without another release.
When
this event fires
OnboardingCompleted
Who
matches this audience
@device.country
=
"US"
AND
@custom.goal
=
"weight_loss"
What
gets shown to them
Paywall
paywall_weight_loss
Goal-specific copy, pricing, and CTA — only this audience sees it.Run
Growth Team
Launch, measure, and adjust. Ship the integration once, then test new experiments as your growth strategy changes.
Start with the moments that drive growth.
Onboarding by entry
Users arriving from different campaigns get different first sessions.
Survey after friction
When a user abandons setup or skips a key step, Amply can ask why before the context is gone.
Offer at the upgrade point
When a user hits a limit, Amply can test the next best offer.
Test the actions behind each screen.
Amply can trigger more than UI. Use dashboard experiments to call the app logic you already own.
Amply rule fires
UI surfaces
What users seePaywall
Survey
Ad
App logic
What runs underneathServer sync
Rating prompt
Entitlement check
Custom function
AnyWorks alongside your stack.
Keep RevenueCat, Amplitude, Mixpanel, AppsFlyer, Adjust, and your ad mediation stack. Amply controls when in-app logic fires.
Plans matched to your experiment pace.
Starter
1 project · 1,000 MAU · 3 experiments — free forever
Core
For early teams testing core flows
Growth
For teams running more campaigns across more users
Core
For early teams testing core flows
Growth
For teams running more campaigns across more users
Enterprise
What to know before you install.
Do we need to rebuild our paywalls or surveys?
No, Amply triggers flows your app already owns. You decide what can be opened or fired; Amply decides when, where, and for whom.
Will Amply slow down the app?
No, experiment config is fetched remotely and cached locally. If Amply is unreachable, the app falls back to the default behavior you shipped.
Is Amply a payment, analytics, or ad platform?
No, keep RevenueCat, Amplitude, AppsFlyer, Adjust, and your ad mediation stack. Amply controls where in-app logic fires while your existing tools keep doing their jobs.
Does Amply replace our existing backend systems?
No, Amply does not run your in-game economy or item catalog. It controls when registered experiences and functions are triggered, while your existing systems remain the source of truth.
From signup to live test in a day.
Register, point the setup autopilot at your repo, ship the integration. Your growth team controls the rest from the dashboard.
Step 1
Step 2
Step 3
Ongoing
Sign up
Create an account, register your company, add your app. No demo gate, no procurement loop.
Free to start, no credit card. Setup autopilot does the wiring for you.