Skip to Content
SourcesStripeStripe Metrics

Stripe Metrics

Customer ID Options

Choose one of three customer identifier types to sync data with Mixpanel:

  1. Stripe Customer ID: Automatically generated unique identifier for each customer in Stripe.
  2. Email: Customer’s email address, ideal for cross-platform identification.
  3. Metadata: Custom attributes stored in Stripe, which need to be synced with Mixpanel.

Events Synced to Mixpanel

EventDescription
Trial StartTriggered when a trial period begins as part of a subscription
Trial EndedTriggered when the trial period concludes
Trial ExtendedTriggered when a user extends their trial period
Account CreatedTriggered when a new customer record is created in Stripe (excludes guest purchases)
Payment ReceivedTriggered when a payment is successfully charged to a customer
Payment FailedTriggered when a customer’s payment attempt is unsuccessful
Payment RefundedTriggered when a payment is refunded by the business
Subscription StartedTriggered when the first payment for a subscription is received
Subscription Cancel RequestedTriggered when a customer requests to cancel their subscription
Subscription EndedTriggered when a subscription concludes
MRRTriggered monthly, calculating recurring revenue based on all payment frequencies. Net amount after Stripe fees, excluding refunds

User Properties

  • LTV (Lifetime Value): Total revenue generated by a customer (net amount paid, after subtracting Stripe fees and refunds).

Key Differences Between Stripe and Mixpanel Reporting

MRR

  • Mixpanel: Uses net payment amounts (Stripe fees are subtracted automatically).
  • Stripe: Shows invoice amounts, requiring manual subtraction of refunds.

LTV

  • Mixpanel: Reflects exact amounts paid, excluding refunds.
  • Stripe: May reflect invoice line items rather than payments.

Known Issues

  • Currency Adjustments: For some currencies (e.g., GBP, EUR, USD, AUD), amounts must be divided by 100 (e.g., 3900 becomes 39.00). In Vendo, all currencies are divided by 100.
  • Refund Timestamp Accuracy: Rarely, refund events may not have the correct timestamp due to reliance on the “last updated at” field.
Last updated on