IN-APP DECISION LAYER
Decide who sees what. Without engineers or releases.
Your app already has the screens. Amply lets your team decide who sees each one, and when — from the dashboard.
A real session of your app, exactly as shipped. The user taps Pacelog open.
Campaigns you can read aloud.
When trial_state flips to expired, users installed in the last 30 days see the comeback offer — once.
Different users, different first screens.
Match the first screen to a deeplink, a product page, or a saved goal — no app release.
Who
SETUP
Your sets it up.
Point your AI agent at Amply — integrated in minutes. The open-source skill and the Amply MCP wire the SDK up as a reviewable diff. Prefer to do it yourself? It is still one pass.
Install Amply skill
amply-integration skill installed
$
Add the SDK, init, track(), a deeplink listener — once.
Most campaigns reuse events and deeplinks you already have. The full quickstart, every platform, lives in the docs.
Open the quickstart docs →Works alongside your stack.
Keep your subscriptions, analytics and attribution. Amply only controls when in-app logic fires.
Live in production.
Happens
voice journal
Asks for a rating the first time a user logs a mood — at a positive moment, not at random.
StillFrame
video frame grabber
Free exports pass through a rewarded ad — and if the ad fails to load, the export runs anyway.
Seabook
fish ID & dive log
Shows free divers the premium intro the first time they log a dive.
The docs are the demo — recipes, SDK reference, the gating guide. Read them before your engineers ask. →
No logo wall yet — these are real campaigns in real apps, and the control room above is the same product they run. Amply is onboarding early teams now; yours could be next to them.
Start free. Upgrade when real traffic begins.
1 project · 1,000 MAU · 3 experiments — free forever. No credit card.
Core
(billed annually)
(billed annually)
For small teams running their first live campaigns
- 3 projects
- 25,000 MAU / project
- 20 experiments / project
- Remote price changes
Growth
Recommended(billed annually)
(billed annually)
For teams running more campaigns across more users
- 10 projects
- 100,000 MAU / project
- Unlimited experiments
- Remote price changes
Enterprise
TailoredCustom limits · Remote price changes · Dedicated support
The questions your team will 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. Amply renders nothing. Your screens, your design, your code — Amply decides who sees them and when.
You decide what can be opened or fired; Amply decides when, where, and for whom.
Rules evaluate locally on the device against config fetched between sessions. No network call in the hot path, no webview, no remote code.
No. Keep RevenueCat for billing, Amplitude for measurement, AppsFlyer for attribution. Amply is the layer that decides which in-app flow fires.
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.
If Amply is unreachable, the app falls back to the default behavior you shipped. No matching campaign, no config, servers down — the worst case is the status quo.
FALLBACKapp as shippedFlags toggle code paths. The campaign grammar on top — live audiences, event triggers with param conditions, repeat rules, frequency limits, an instant Cancel — is the internal tool teams keep almost building: it loses the roadmap fight and scatters across flags with no owner. Amply ships it ready-made, operable by the team that owns the metric — no engineer in the loop.
In the analytics tool you already trust. Forward the same events to Amplitude or Mixpanel; run different campaigns to different segments and read the funnels there.
Still have questions? [email protected]
GETTING STARTED
What happens after signup
From signup to a live test in a day. Your growth team runs the rest from the dashboard.
Step 1
Step 2
Step 3
Ongoing
Sign up
Create an account, add your app. No demo gate.
Step 1
Sign up
Create an account, add your app. No demo gate.
Step 2
Setup autopilot
Your AI agent wires the SDK — the console above is the real flow.
Step 3
First test live
Growth ships its first experiment from the dashboard — paywall, onboarding fork, or a flow you already own.
Ongoing
You stay in control
Move audiences, swap variants, cancel instantly. The dashboard stays in your team’s hands.
Go on — press it.
Your next campaign doesn't need a release.
Integrate once. From then on, audiences, triggers, surfaces, and fallbacks are dashboard edits — live in minutes, on the app version your users already have.