Integration

Zembula + OneSignal

One person in OneSignal can hold several subscriptions across push, email and SMS, and Zembula can read them. Zembula can look the person up by external ID, OneSignal ID or custom alias.

It's our business to grow yours

Book a demo

What Zembula can read from OneSignal

OneSignal sends push, email, SMS and in-app messages. Zembula can read one person from OneSignal, with aliases, properties and subscriptions. The person record holds the tags of the person, the country, and the first and last active times. It holds the external ID and the OneSignal ID.

Each subscription is one push, email or SMS address of the person. Zembula can read each one, with its type, its enabled status, its session count and its session time. Zembula can look a person up by external ID, by OneSignal ID or by a custom alias. Zembula can also read the list of segments that your team saved in an app.

OneSignal also streams message events to a public endpoint. Those events include push clicks, email opens, email bounces, SMS failures and in-app impressions, and Zembula can take them through the webhook route. A per-app API key gives access to the API. Managing keys needs an Organization API key from your team.

DataDetailLooked up byHow fresh
TagsThe tags saved on one person in OneSignal.external ID, OneSignal ID or custom aliasopen time
CountryThe country saved on one person.external ID, OneSignal ID or custom aliasopen time
First and last active timesWhen a person was first and last active.external ID, OneSignal ID or custom aliasopen time
SubscriptionsEach push, email or SMS address of a person, with its type and status.subscription id or tokenopen time
Session count and timeThe session count and session time of a subscription.subscription id or tokenopen time
SegmentsThe saved groups of people in an app.segment idopen time
Message eventsPush, email, SMS and in-app events, such as sent, clicked and bounced.set at setupset at setup

How the data arrives

  • API: Zembula can read one person, with aliases, properties and subscriptions, from the OneSignal API.
  • Webhook: OneSignal streams message events to a public endpoint. Zembula can receive them there.
  • ESP merge tags: A merge tag of your email service provider carries the person’s ID in the image URL.

What you need

  • A per-app OneSignal API key. Managing keys needs an Organization API key.
  • An external ID or OneSignal ID for each person, sent as a merge tag in the image URL.
  • An API key or a data export from OneSignal. Zembula sets up the connection for you.

Ideas for email

  • Read the tags of a person to choose a banner variant for an email.
  • Read the country of a person to localize the banner copy.
  • Use click events to confirm which banner variant a person saw.

Last checked: 19 November 2026.

Performance marketing dials, inside email. For the first time.

See how we do it by booking a demo.