Amplitude

Integrate OneSignal with Amplitude to enable real-time, behavior-based targeting across push, in-app, email, and SMS. This app-level integration supports three data flows:

• Message events → Amplitude: Track delivery, clicks, failures, and more for all channels.
• Custom events → OneSignal: Send Amplitude events into OneSignal to trigger Journeys or Segments.
• Cohorts → OneSignal: Sync behavior-based Amplitude cohorts as targeting filters in OneSignal.

---

​

Requirements

• Amplitude Account
• OneSignal Paid Plan
• OneSignal app with Users and External ID set.

---

​

Setup

​

Add Amplitude to OneSignal (Outbound)

Sends OneSignal message events into your Amplitude project.

1. In OneSignal, navigate to Data > Integrations > Catalog and select Amplitude.
2. Click Settings, then open the Outbound tab.
3. Enter your Amplitude API token, select the message events you want to send, and click Save.

​

In Amplitude

1. Find your project API Key then copy-paste it into OneSignal.
2. If using Amplitude’s EU servers, check Send events exclusively to Amplitude’s EU Residency Endpoint. You can verify this by your Amplitude URL. If you see eu.amplitude.com then you are using Amplitude’s EU servers.

​

Add OneSignal to Amplitude (Inbound)

In your Amplitude Destinations, search for OneSignal. Amplitude provides two OneSignal destination types in the catalog:

• Cohorts: Sync cohorts from Amplitude to OneSignal.
• Events User Properties: Send custom events from Amplitude to OneSignal.

​

User ID mapping

The External ID in OneSignal must match the Amplitude user property you select (e.g., user_id). Verify this property is populated in both systems — cohort syncing and event tracking depend on an exact match.

​

Additional properties

You can include extra properties that will be attached to custom events in OneSignal. This is useful for conditional event processing.

---

​

Testing custom events

1. In the Amplitude > OneSignal Events Destination, click the Test Connection button.

2. Make sure the "user_id" in the payload is set to an existing User’s External ID in your OneSignal App.
3. Click the Send Test Event button.
4. The Response box should remain empty and you should see "OneSignal has successfully received test event."

5. In OneSignal, navigate to Data > Custom Events and verify the test event appears in the list.

​

Export Amplitude cohorts to OneSignal

Sync Amplitude cohorts to OneSignal using the matching External ID configured above. Exporting does not create Users — each User must already exist in OneSignal.

1. In Amplitude, create a cohort. See Amplitude’s docs on cohorts.
2. Click Sync and choose OneSignal as the destination.
3. Choose sync frequency.

​

OneSignal Segment creation

The synced cohort appears as an Amplitude Segment filter. OneSignal automatically creates a Segment for the cohort if:

• The Users in the Amplitude cohort also exist in OneSignal with a matching External ID.
• You have not exceeded your Segment limit in OneSignal.

---

​

Track message events in Amplitude

OneSignal sends the following message events to Amplitude in real time. Select which events to send in Data > Integrations > Amplitude > Outbound.

​

Event properties

Every event sent from OneSignal to Amplitude includes these properties:

---

​

FAQ

​

Why don’t my cohort and segment counts match?

1. Missing or mismatched External IDs Only Users with a matching OneSignal External ID and Amplitude User ID are included. This integration does not create Users or Subscriptions.
2. Unsubscribed Users OneSignal Segments only display the count for subscribed Subscriptions. Unsubscribed Subscriptions are available for Journeys or In-App Messages.

For example, if an Amplitude 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.

​

Do unsubscribed Users sync from Amplitude?

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.

​

Why doesn’t delivery data match?

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.

​

How can we send user/subscription events?

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 Amplitude:

• User State Observer: Mobile SDK, Web SDK
• Permission Observer: Mobile SDK, Web SDK

​

Why is the OneSignal Subscription ID added to Amplitude as a device_id?

Amplitude expects a device_id for deduplication. OneSignal uses subscription_id for this, which maps into device_id automatically. See Amplitude’s docs for more information.

---

​

Related pages

---