Run in-app growth experiments
without an app release.
Move remotely where your app shows paywalls, surveys, ads, or any custom function. Your growth team experiments live, without waiting on engineering or App Review.
Map events once, ship campaigns anytime.
Engineering sends product events into Amply once. Growth then turns those events into experiments — paywalls, surveys, offers — without another release.
Install
Engineering Team
Install Amply once, then start sending the events your growth team can act on.
Create
Growth Team
Create campaigns in the dashboard. Choose the audience, message, offer, timing, and destination — 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.
Already shipping with Amply.
We’re pre-launch. These apps are already live with the SDK. Take the next spot.
Seabook
Fish ID & LogHappens
Voice journalStillFrame
Video frame grabberYour app
Take the next spotStart with the moments that shape growth.
Run experiments across onboarding, monetization, engagement, and the custom actions your app already depends on.
Paywall after intent
Someone finishes a high-value action, and Amply shows the right upgrade offer at that moment.
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 player runs out of access, currency, or progress, Amply can test the next best offer.
Test the actions behind the 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
AnyStart with familiar experiments like paywalls, surveys, and ads, then extend the same workflow to server syncs, rating prompts, entitlement checks, or any custom function your team registers.
Works with the stack you already use.
Amply sits beside your subscription, analytics, attribution, and ad tools. Nothing to replace.
Use RevenueCat for subscriptions. Use Amplitude or Mixpanel for analytics. Use AppsFlyer or Adjust for attribution. Keep your ad mediation stack. Amply controls when in-app logic fires.

Simple beta pricing.
Start with the plan that matches how many experiments your team wants to run.
Start for free
1 project · 1,000 MAU · 3 experiments — free forever
Core
For apps ready to optimize
Growth
For apps scaling conversion
Core
For apps ready to optimize
Growth
For apps scaling conversion
Enterprise
What to know before you install.
Do we need to rebuild our paywalls or surveys?
No. Amply can trigger 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, your 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. 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 waitlist to live test in a week.
No procurement loop. No six-week kickoff. Engineering ships the SDK once — your growth team takes it from there.
Day 1
Day 2
Day 7
Ongoing
You're in
Dashboard access and SDK docs land in your inbox. No procurement loop, no demo gate.
No credit card. Beta cohort opens monthly — limited spots.