Integrate OneSignal with Mixpanel to sync behavioral cohorts, track message events, and target Users across push, email, SMS, and in-app channels.
Integrate OneSignal with Mixpanel to enable real-time, behavior-based targeting across push, in-app, email, and SMS. This app-level integration supports two data flows:
Message events → Mixpanel: Track delivery, clicks, failures, and more for all channels.
Cohorts → OneSignal: Sync behavior-based Mixpanel cohorts as targeting filters in OneSignal.
The OneSignal External ID must match the Mixpanel User ID Property you select (for example, user_id). Cohort syncing and message event tracking only work when this mapping is exact.
1
Select the User ID Property in Mixpanel
In the Mixpanel OneSignal connector, choose the User ID Property that holds the same value as the OneSignal External ID.
Mixpanel dashboard for setting the OneSignal properties
2
Confirm the property exists on Mixpanel user profiles
Open Mixpanel > Users and verify the User ID Property you selected appears in user profile properties.
Mixpanel > Users > User Profile Properties
3
Confirm values match the OneSignal External ID
Open the User in OneSignal > Audience > Users and confirm the External ID matches the Mixpanel User ID Property value exactly.
OneSignal > Audience > Users > External ID
If you map the Mixpanel $distinct_id to the OneSignal External ID, only the top value in the Distinct ID list matches.In the example below, only 890ea9b1-9024-4fb9-a92f-152ba67dd21a will match. The integration cannot match 109768518080488203109 or $device:1880c06821f1b3-052354675cde95-1d525634-1fa400-1880c06821f1b3.
Use caution when setting Distinct ID if used for the User ID Property mapping
Click Continue when finished. You can now export cohorts from Mixpanel to OneSignal and collect message events from OneSignal in Mixpanel.
Sync Mixpanel cohorts to OneSignal using the matching External ID configured above. Exporting does not create Users — each User must already exist in OneSignal.
1
Create a cohort in Mixpanel
In Mixpanel, create a cohort containing the Users you want to target.
2
Export to OneSignal
Click Options > Export to… > The OneSignal Connection name.
How to export a Mixpanel cohort to OneSignal
3
Choose a sync frequency
Select how often Mixpanel should sync the cohort, then click Begin Sync.
The synced cohort appears as a Mixpanel Segment filter. OneSignal automatically creates a Segment for the cohort if:
The Users in the Mixpanel cohort also exist in OneSignal with a matching External ID.
You have not exceeded your Segment limit in OneSignal.
OneSignal requires at least one matching User to create the Segment. After creation, the Segment remains in OneSignal even if the cohort later has no Users — it shows as empty until matching Users are added again.
OneSignal sends the following message events to Mixpanel in real time. Select which events to send in Data > Integrations > Mixpanel.To test, send yourself a message from OneSignal, then navigate to your user profile page in Mixpanel. Within the Activity Feed, you should see the events populate.
Mixpanel activity feed with OneSignal message events
Missing or mismatched External IDs
Only Users with a matching OneSignal External ID and Mixpanel User ID are included. This integration does not create Users or Subscriptions.
Unsubscribed Users
OneSignal Segments only display the count for subscribed Subscriptions. Unsubscribed Subscriptions are available for Journeys or In-App Messages.
For example, if a Mixpanel cohort has 10 Users but the OneSignal Segment shows 8 Subscriptions, the 2 missing Users may:
Not exist in OneSignal or have an incorrect External ID.
Have unsubscribed Subscriptions.
To verify, check the Audience > Users tab in OneSignal to see if the Users exist and have active Subscriptions.
Yes, but they are excluded from the OneSignal Segment counts at this time. You can still message them via Journeys or In-App Messages if they have other Subscriptions or their Subscription type supports it.
A single User may have multiple Subscriptions (push devices, email addresses, phone numbers). Each Subscription generates its own delivery event. For example:
1 user = 2 Android + 1 iOS + 2 Web = 5 push Subscriptions
1 push message = up to 5 sent/received/clicked events
Use the subscription_id in event properties to trace the exact source.To troubleshoot missing events:
Ensure OneSignal.login is called whenever a user is identified to set the External ID.
Verify that OneSignal.logout isn’t removing the External ID.
Check API requests or CSV uploads that may alter the External ID.
Can I send custom events from Mixpanel to OneSignal?
Not natively. The Mixpanel integration supports message events (OneSignal → Mixpanel) and cohort syncing (Mixpanel → OneSignal), but does not include a built-in custom event destination. Unlike Amplitude, Mixpanel has no native OneSignal events destination.To route Mixpanel behavioral events into OneSignal as custom events that trigger Journeys or Segments, use a third-party connector like Vendo.
User and subscription-level events (e.g., permission granted, user login/logout) are not automatically sent.The OneSignal SDK has event listeners that can be used to track these events for you to send to Mixpanel:
