Integration guideSourcesAvailable

OneSignal

Managed OneSignal source imports for subscriber profiles, notification history, segments, and user identity enrichment.

Last reviewed July 13, 2026

Managed source - Vendo can import OneSignal data for early-user and custom implementations. This is available through high-touch setup, not broad self-serve setup.

What Vendo Syncs

Vendo reads OneSignal data through the OneSignal REST APIs and writes source tables into BigQuery.

Stream	Description
Profiles	Device and subscription records, tags, push tokens, device metadata, and external user IDs
User identities	v2 identity enrichment that resolves canonical OneSignal user IDs from external user IDs
Notifications	Sent push, email, and SMS notifications with delivery and engagement stats
Segments	Segment definitions, filters, and subscriber counts

Requirements

Before setup, confirm you have:

A OneSignal app ID
A OneSignal REST API key
Access to the OneSignal dashboard
Permission for Vendo to read subscriber, notification, segment, and user identity data
A Vendo workspace with BigQuery warehouse access configured

Setup

OneSignal source setup is currently managed by the Vendo team.

Share the OneSignal app ID and REST API key through the approved secure credential handoff.
Confirm which streams should be imported: profiles, notifications, segments, and user identities.
Confirm the historical backfill window for notifications.
Vendo creates or upgrades the OneSignal app connection with source access.
Vendo triggers the first import and validates the BigQuery tables.

Expected Tables

Table names include the OneSignal source prefix and connection identifier.

Table pattern	Contents
`onesignal_*_profiles`	Subscriber and device profile records
`onesignal_*_user_identities`	External user ID to OneSignal ID enrichment
`onesignal_*_notifications`	Notification delivery and engagement records
`onesignal_*_segments`	Segment definitions and metadata

Validation

After the first import, check:

The source status is active
Profiles and user identities have non-zero row counts
Notification rows match the selected backfill window
Segment rows match the OneSignal dashboard
Identity Resolution can map external_user_id or onesignal_id where available

Troubleshooting

Symptom	What to check
Missing profiles	Confirm the REST API key can read players/subscriptions for the app ID
Missing user identities	Confirm profiles include external user IDs before identity enrichment runs
Missing notifications	Check the selected backfill window and notification history in OneSignal
Permission error	Regenerate the REST API key or confirm the app ID/key pair belongs to the same OneSignal app