Paywall integrations
Send RevenueCat Paywall events to your analytics platforms and webhooks
This page lists the integrations that receive RevenueCat Paywall events, the events each one supports, and how to turn them on. Paywall events are delivered alongside your standard subscription lifecycle events, so paywall engagement and revenue land in the same destination.
Supported integrations
| Integration | Use case |
|---|---|
| Amplitude | Analyze paywall engagement alongside subscription lifecycle events in your Amplitude project |
| Mixpanel | Track paywall views and interactions in your Mixpanel project for cohort and funnel analysis |
| PostHog | Combine paywall events with your product analytics in PostHog |
| Segment | Route paywall events through your Segment workspace to your warehouse and downstream destinations |
| Webhooks | Receive paywall events on your own server for custom processing |
Paywall events
All five integrations support the same set of paywall-specific events, in addition to the standard RevenueCat subscription lifecycle events they already track:
| Event | Default name | Description |
|---|---|---|
| Paywall impression | paywall_impression | Fired when a paywall is displayed to a Customer |
| Paywall close | paywall_close | Fired when a Customer closes a paywall |
| Paywall cancel | paywall_cancel | Fired when a Customer dismisses the payment confirmation on a paywall |
| Paywall exit offer | paywall_exit_offer | Fired when an exit offer is shown on a paywall |
| Paywall component interaction | paywall_component_interacted | Fired when a Customer changes a paywall control (tab, package, purchase button, sheet, etc.). See the component interaction reference for field details |
You can customize the name for each event in the integration settings. Webhooks send the event type in uppercase (for example, PAYWALL_IMPRESSION) unless you configure custom names; see the webhook event types reference for the fields included in each event.
Paywall events are not purchase lifecycle events. They don't include transaction fields such as product_id, price, or transaction_id.
Enabling paywall events
Paywall event delivery is opt-in, and you enable it per integration. Set the integration up first using the integration-specific docs linked above, then:
- Navigate to Integrations in your project and open the relevant integration
- Click the Paywall Events tab
- Check Send Paywall events
- Optionally customize the event names
- Save your changes
Next steps
- Display a Paywall in your app so it starts generating events
- Create a Paywall on the Dashboard if you don't have one yet
- Analyze funnel integrations if you also run RevenueCat Funnels