Skip to content
AppDues
Log in
Contact salesSign up

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.

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.

Mixpanel events and how to interpret them
EventWhat it meansReporting note
Initial PurchaseFirst purchase of an auto-renewing subscription without a free trialUse as the paid starting point for non-trial cohorts
Trial StartedStart of a free trial for an auto-renewing subscriptionStart of trial cohorts
Trial ConvertedFree trial moves to a normal paid periodMeasure trial-to-paid conversion
Trial CancelledRenewals turned off during the free trialSeparate from paid-period cancellation
RenewalSubscription renews, or is repurchased after a lapseIncludes win-back repurchases
CancellationRenewals turned off during the normal paid periodAccess timing depends on the paid period
UncancellationUser re-enables auto-renew statusUse to measure recovery after cancellation
Non Subscription PurchasePurchase of a product that is not an auto-renewing subscriptionKeep separate from subscription lifecycle events
Billing IssuesA charge attempt failed; subscription may not have expired if a grace period is enabledDo not treat as expiration
ExpirationSubscription has expired and access should be removedEnd-of-access signal
Product ChangeUser changed the subscription product; new subscription may not be effective immediatelyVerify 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.