Send in-app purchase events to Mixpanel
Connect iOS and Android purchase and subscription activity to Mixpanel so product analytics reflect what happened at checkout, during trials, at renewal, and when access ends.
The event set below is a practical checklist for building reports and alerts without guessing which lifecycle moment an event represents.
What the integration helps you do
Use the integration to answer three questions in Mixpanel. First, when and why does a user convert? Interactive reports can place purchase activity alongside product behaviour. Second, did a release help or hurt retention? Track the relevant lifecycle events before and after launch. Third, where is performance weak? Split results by store, country and subscription plan rather than relying on a single blended total.
A practical reading order
Start with the lifecycle in order: trial or first purchase, conversion or renewal, cancellation or uncancellation, then billing trouble or expiration. That sequence prevents common misreads. Cancellation during a trial is not the same as cancellation during a paid period, and a billing issue is not expiration. A repurchase after a lapse counts as a renewal event, while a one-off purchase is separate from subscription activity.
Checklist for reliable reporting
Build a small decision checklist before creating dashboards: confirm whether each event fires for auto-renewing subscriptions or one-off products, separate trial-period actions from paid-period actions, and keep billing issues distinct from expiration. For product changes, do not assume immediate effect; verify the effective timing in the subscription-management guidance. Finally, compare the same event across store, country and plan so a localised problem is not hidden by overall volume.
| Event | What it means | Reporting note |
|---|---|---|
| Initial Purchase | First purchase of an auto-renewing subscription without a free trial | Use as the paid starting point for non-trial cohorts |
| Trial Started | Start of a free trial for an auto-renewing subscription | Start of trial cohorts |
| Trial Converted | Free trial moves to a normal paid period | Measure trial-to-paid conversion |
| Trial Cancelled | Renewals turned off during the free trial | Separate from paid-period cancellation |
| Renewal | Subscription renews, or is repurchased after a lapse | Includes win-back repurchases |
| Cancellation | Renewals turned off during the normal paid period | Access timing depends on the paid period |
| Uncancellation | User re-enables auto-renew status | Use to measure recovery after cancellation |
| Non Subscription Purchase | Purchase of a product that is not an auto-renewing subscription | Keep separate from subscription lifecycle events |
| Billing Issues | A charge attempt failed; subscription may not have expired if a grace period is enabled | Do not treat as expiration |
| Expiration | Subscription has expired and access should be removed | End-of-access signal |
| Product Change | User changed the subscription product; new subscription may not be effective immediately | Verify timing for upgrades, downgrades and crossgrades |
Definitions apply to auto-renewing subscription products unless the event is Non Subscription Purchase; Product Change does not guarantee immediate effect.
Frequently asked questions
Which subscription events are sent to Mixpanel?
It covers the first paid purchase without a trial, trial start, trial conversion, trial cancellation, renewal or repurchase after a lapse, cancellation during a paid period, re-enabling renewals, one-off purchases, billing problems, expiration, and product changes.
Does a billing issue mean the subscription has expired?
No. A billing issue means a charge attempt failed; access may continue when a grace period is enabled. Expiration is separate and means access should be removed.
Does a product change take effect immediately?
A product change records that the user changed the product, but the new subscription is not necessarily effective immediately. Check the linked subscription-management guidance for upgrades, downgrades and crossgrades.
How should I use these events in Mixpanel?
Use the events to build interactive reports on conversion timing and reasons, watch how retention responds after a feature release, and break results down by store, country and plan to surface weak areas.