Devices
iOS, Android, and browser registration
Store provider tokens, app version, device model, OS, locale, timezone, and enabled state. Token refresh keeps identity and tags attached.
Connect devices, shape audiences, send rich notifications, automate follow-ups, and measure meaningful user behaviour without stitching together separate systems.
Anonymous devices can become known users after login while preserving useful device context.
Store provider tokens, app version, device model, OS, locale, timezone, and enabled state. Token refresh keeps identity and tags attached.
Attach an external user ID, aliases, tags, and properties. Identify after login, remove a registration on logout, and optionally verify identity with short-lived ES256 tokens.
Filter by platform, locale, timezone, app version, tags, device dates, lifecycle events, or named custom events. Estimate the audience before sending.
The same restricted registration and event boundary is available across native, cross-platform, and browser clients.
Use APNs directly from an iOS 15+ Swift package or Firebase Messaging helpers from the Android Kotlin library.
Register the correct APNs token on iOS and FCM token on Android, preserve identity through refreshes, parse payloads, and report lifecycle events.
Generate a restricted public key and paste-ready hosted-SDK snippet from the dashboard, use the Web SDK directly, or install a package for WordPress, Magento, Drupal, or Joomla. Each path supports a root-scoped service worker, VAPID subscriptions, notification clicks, and clean unsubscribe behaviour.
Every notification takes an immutable content and audience snapshot, so historical reporting remains understandable as your setup evolves.
Send to one device, one user and all their devices, an exact tag match, a saved segment, or every enabled device. Add included and excluded segments for compound campaigns.
Use templates and variables, localised variants, images, deep links, custom data, sounds, badges, categories, and up to three interactive actions.
Schedule an absolute time or a wall-clock time in each recipient's timezone. Choose queue priority, TTL, collapse behaviour, and platform overrides.
Versioned journey graphs give each execution a stable definition even when you improve the flow later.
Inspect recipients and errors, then report received, confirmed-delivered, opened, clicked, dismissed, custom, and outcome events separately. Reports include unique open and click rates, daily trends, platform and notification funnels, outcome names, and attribution.
Configure destinations, select event types, send a test request, and verify HMAC signatures. Retries and destination safeguards keep integrations dependable.
Create expiring exports, tune event and device retention, and use the privacy workflow for scheduled account deletion.
Separate organisations and apps, manage team access, rotate scoped API keys, inspect audit history, and keep provider credentials encrypted.
Register a device, target a test user, and inspect the resulting events before inviting the rest of your audience.