Integration · Analytics
Amplitude
Amplitude is widely deployed at the Series-B–D mobile-growth teams we sell to. Metapolicy reads Amplitude events as reward signal and writes lift readouts back as user properties so your growth analyst can segment on "currently in the +9.3% cohort" inside Amplitude itself.
The contract
What flows in
- Amplitude HTTP API → reward events ingested by event name + property mapping
- Cohort definitions ingested as treatment-effect cuts (so the DR readout reports per the same cohorts your team already uses)
What flows out
- User properties written back: metapolicy_policy_snapshot, metapolicy_assignment, metapolicy_cohort
- Lift readout rows available as a cohort source so Amplitude charts can compare DR-confirmed cohorts
Setup
- 01In Metapolicy dashboard → Integrations → Amplitude, paste your Amplitude project API + secret keys
- 02Map the Amplitude events you treat as rewards (typically your Subscription Purchased / Plan Upgraded events)
- 03Optionally toggle user-property write-back
- 04Validate by checking that a fresh decision shows up as a metapolicy_assignment property on the user in Amplitude within 60 seconds
Cohort parity
Your team has likely already defined cohorts in Amplitude (high-LTV deciles, lapsed-then-returned, etc.). Metapolicy ingests these cohort definitions so the per-segment CATE readout speaks the same vocabulary — no naming reconciliation between platforms.
Other analytics integrations
Wire Amplitude in a 30-minute call.
We pair with your engineer, ship the integration live, and run the first decision on your stack.