Hi @inout-4dd00c,
Thanks for reaching out. I’m happy to help.
At the moment, the Placement identifier is not included as an event property on the Mixpanel integration events, and the Mixpanel integration schema isn’t customizable.
That said, you can still get at “where did this purchase happen?” with one of these approaches:
-
Track a client-side Mixpanel event with placement
When you show a paywall, send your own Mixpanel event, for example:
-
event: paywall_shown
-
properties: { placement: "onboarding" }
Then, because both your app and RevenueCat use the same Mixpanel distinct_id, you can:
-
Build a funnel from paywall_shown (by placement) -> rc_initial_purchase_event, or
-
Attribute the purchase to the most recent paywall_shown event for that user.
-
Store placement as a user/profile property
As an alternative, you can update a Mixpanel user property like last_paywall_placement = "onboarding" right before starting the purchase flow. Since the RevenueCat integration uses the same distinct_id, you can then segment rc_initial_purchase_event by that profile property inside Mixpanel.
I know it would be cleaner to have the Placement key attached directly to the RevenueCat events themselves, so I’ve noted this as a feature request on our side so the team can consider adding Placement context to integration payloads in the future.
Hope this helps, let me know if you have any other questions, I’m happy to assist.
Best,
Hussain