Skip to main content

PostHog

👍Pro Integration

The PostHog integration is to all users signed up after September '23, the legacy Grow and Pro plans, and Enterprise plans. If you're on a legacy Free or Starter plan and want to access this integration, migrate to our new pricing via your billing settings.

PostHog can be a useful integration tool for seeing all events and revenue that occur for your app even if it’s not active for a period of time. You can use PostHog's product analytics to find patterns in customer behavior and inform marketing strategies.

With our PostHog integration, you can:

  • Create a behavioral cohort of customers based on specific actions, such as watching a specific episode of a show after subscribing. Follow a cohort throughout their lifecycle to realize overarching trends.
  • Measure the path of a user from marketing material to the purchase of a subscription.

With accurate and up-to-date subscription data in PostHog, you'll be set to turbocharge your product analytics ⚡️

Integration at a Glance

Includes RevenueSupports Negative RevenueSends Sandbox EventsIncludes Customer AttributesSends Transfer EventsOptional Event Types
Requires API keynon_subscription_purchase_event uncancellation_event subscription_paused_event expiration_event billing_issue_event product_change_event

Events

The PostHog integration tracks the following events:

EventDefault Event NameDescriptionApp StorePlay StoreAmazonStripePromo
Initial Purchaserc_initial_purchase_eventA new subscription has been purchased.
Trial Startedrc_trial_started_eventThe start of an auto-renewing subscription product free trial.
Trial Convertedrc_trial_converted_eventWhen an auto-renewing subscription product converts from a free trial to normal paid period.
Trial Cancelledrc_trial_cancelled_eventWhen a user turns off renewals for an auto-renewing subscription product during a free trial period.
Renewalrc_renewal_eventAn existing subscription has been renewed or a lapsed user has resubscribed.
Cancellationrc_cancellation_eventA subscription or non-renewing purchase has been cancelled. See cancellation reasons for more details.
Uncancellationrc_uncancellation_eventA non-expired cancelled subscription has been re-enabled.
Non Subscription Purchaserc_non_subscription_purchase_eventA customer has made a purchase that will not auto-renew.
Subscription Pausedrc_subscription_paused_eventA subscription has been paused.
Expirationrc_expiration_eventA subscription has expired and access should be removed. If you have Platform Server Notifications configured, this event will occur as soon as we are notified (within seconds to minutes) of the expiration. If you do not have notifications configured, delays may be approximately 1 hour.
Billing Issuesrc_billing_issue_eventThere has been a problem trying to charge the subscriber. This does not mean the subscription has expired. Can be safely ignored if listening to CANCELLATION event + cancel_reason=BILLING_ERROR.
Product Changerc_product_change_eventA subscriber has changed the product of their subscription. This does not mean the new subscription is in effect immediately. See Managing Subscriptions for more details on updates, downgrades, and crossgrades.

For events that have revenue, such as trial conversions and renewals, RevenueCat will automatically record this amount along with the event in PostHog.

Setup

1. Set PostHog User Identity

In order to associate RevenueCat data with a PostHog User, the RevenueCat $posthogUserId Attribute should be set in RevenueCat. If this field does not exist, RevenueCat will fallback to the RevenueCat app user ID. You can read more about PostHog user profiles in PostHog's Identifying users documentation.

2. Send RevenueCat Events to PostHog

After you've set up the Purchase SDK and PostHog SDK to have the same user identity, you can "turn on" the integration and configure the event names from the RevenueCat dashboard.

  1. Navigate to your app in the RevenueCat and find the Integrations card in the left menu. Select + New

  1. Choose PostHog from the Integrations menu
  2. Add your PostHog Project API key to the API key field in RevenueCat. The integration uses only public endpoints, so there is no need to set up personal API keys.
  3. Enter the event names that RevenueCat will send or choose the default event names
  4. Select whether you want sales reported as gross revenue (before app store commission), or after store commission and/or estimated taxes.

PostHog configuration page

📘PostHog sandbox environment

PostHog recommends having a production and sandbox project to separate live and testing environments. You can input both keys in the RevenueCat PostHog settings page.

Testing the PostHog integration

Make a sandbox purchase with a new user

Simulate a new user installing your app, and go through your app flow to complete the sandbox purchase.

Check that the PostHog event delivered successfully

While still on the Customer View, select the purchase event in the Customer History page and make sure that the PostHog integration event exists and was delivered successfully.

Check that the PostHog event was delivered

Check the PostHog dashboard for the delivered event

Navigate to your PostHog dashboard > People and groups. In the 'People & groups' tab, you will see the event's user created as a Person.

Check that a PostHog Person has been created

Navigate to your PostHog dashboard > Data management. In the 'Events' tab, you will see events RevenueCat has dispatched to PostHog.

Check that a PostHog Event has been created

Sample Events

Below are sample JSONs that are delivered to PostHog for events.

{
"api_key": "<PostHog project API key>",
"distinct_id": "$RCAnonymousID:87c6049c58069238dce29853916d624c",
"timestamp": "2024-10-22T08:34:56.123412Z",
"event": "rc_initial_purchase_event",
"properties": {
"insert_id": "d1dca188-6a16-4109-b663-778c0dfe9124",
"currency": "USD",
"revenue": 29.99,
"product_id": "premium",
"subscriber_attributes": {},
"period_type": "NORMAL",
"purchased_at": "2024-10-22T08:34:56Z",
"expiration_at": "2024-11-22T08:34:56Z",
"entitlement_id": null,
"entitlement_ids": null,
"presented_offering_id": null,
"transaction_id": "1123142348431",
"original_transaction_id": "1123142348431",
"aliases": ["$RCAnonymousID:87c6049c58069238dce29853916d624c"],
"app_user_id": "$RCAnonymousID:87c6049c58069238dce29853916d624c",
"original_app_user_id": "$RCAnonymousID:87c6049c58069238dce29853916d624c",
"store": "APP_STORE",
"app_id": "appe2a3da5a50",
"platform": "iOS",
"rc_subscription_status": "active"
}
}

Subscription Status Attribute

Whenever RevenueCat sends an event to PostHog, we'll update the rc_subscription_status user attribute with any applicable changes, using one of the following values:

StatusDescription
activeThe customer has an active, paid subscription which is set to renew at their next renewal date.
introThe customer has an active, paid subscription through a paid introductory offer.
cancelledThe customer has a paid subscription which is set to expire at their next renewal date.
grace_periodThe customer has a paid subscription which has entered a grace period after failing to renew successfully.
trialThe customer is in a trial period which is set to convert to paid at the end of their trial period.
cancelled_trialThe customer is in a trial period which is set to expire at the end of their trial period.
grace_period_trialThe customer was in a trial period and has now entered a grace period after failing to renew successfully.
expiredThe customer's subscription has expired.
promotionalThe customer has access to an entitlement through a RevenueCat Granted Entitlement
expired_promotionalThe customer previously had access to an entitlement through a RevenueCat Granted Entitlement that has since expired.
pausedThe customer has a paid subscription which has been paused and is set to resume at some future date.

For customers with multiple active subscriptions, this attribute will represent the status of only the subscription for which the most recent event occurred.

Please note that since this attribute is set and updated when events are delivered, subscribers with events prior to our release of this attribute (during November 2023) will not have this attribute set until/unless a future event (renewal, cancellation, etc) occurs.