App push notifications that reach users the moment it matters.

Send scheduled and automated push notifications to your iOS and Android app users — personalized with any contact field, segmented by any behaviour, and triggered automatically by your campaigns and automations. A few API calls to add to your app. Zero friction for your marketing team.

iOS (APNs) and Android (FCM) — both supported natively
Personalize with any standard or custom contact field
Send scheduled blasts or automation-triggered sequences
Full audience segmentation — send to exactly the right users

Start 14-day free trial Read the API docs

9:41

Saturday, March 14

📅

DailyStory Demo 5m ago

Your appointment is tomorrow at 10am

Tap to add to your calendar or reschedule.

iOS APNs + Android FCM

Personalization on every notification

Scheduled or automation-triggered

AI content generation built in

Full audience segmentation

Platform support

iOS and Android — both supported natively, out of the box.

DailyStory sends push notifications through Apple’s Push Notification service (APNs) for iOS and Google’s Firebase Cloud Messaging (FCM) for Android. Add a small integration to your mobile app using the DailyStory API, register the device token, and every notification you send from DailyStory is delivered through the native notification infrastructure for each platform — reliably, at scale.

✓ Apple APNs — iOS and iPadOS push delivery
✓ Google FCM — Android push delivery
✓ Device token registration via the DailyStory REST API
✓ Single contact can have multiple registered devices
✓ Token refresh handled automatically on re-registration
✓ Full send, delivery, and open tracking per platform

Platform support at a glance

🍎

Apple iOS

APNs · iPhone & iPad

🤖

Google Android

FCM · All Android devices

// POST after user grants notification permission
fetch(`https://${dataCenter}.dailystory.com`
    + “/api/v1/push/register”, {
  method: “POST”,
  body: JSON.stringify({
    tenantUid: “ghg0ctulvdx7bu10”,
    deviceToken: apnsOrFcmToken,
    platform: “ios”, // or “android”
    contactEmail: userEmail
  })
});

No SDK required Plain REST API Works with Swift, Kotlin, React Native, Flutter

Personalization

Every notification reads like it was written for that specific person.

Generic push notifications get ignored. Personalized ones get tapped. DailyStory lets you use any standard or custom contact field as a personalization token inside your push notification title and body — first name, membership tier, cart items, last purchase, upcoming appointment date, loyalty points balance, or any custom property you’ve stored on the contact record. The token is resolved at send time for each individual recipient.

✓ First name, last name, company, and all standard fields
✓ Custom contact fields — any property you’ve defined
✓ AI writing assistant — generate compelling copy in seconds
✓ Preview personalization with a real contact before sending
✓ Same token syntax used across email, SMS, and push

Personalization tokens → rendered notifications

Notification template

Title

Hey {{FirstName}}, your order just shipped 🚀

Body

Order {{OrderNumber}} arrives by {{DeliveryDate}}.

Token → resolved value

{{FirstName}} → Jamie

{{OrderNumber}} → #DS-84291

{{DeliveryDate}} → Wednesday, March 19

{{LoyaltyPoints}} → 2,450 pts

{{MembershipTier}} → Gold Member

Rendered for Jamie

Automations & segmentation

Send the right notification to the right user — automatically.

Push notifications are most powerful when they’re triggered by something real. DailyStory’s automation engine can send push notifications based on any trigger — a contact entering a segment, a custom event firing, a date approaching, or any step in a multi-channel campaign sequence. Combine that with DailyStory’s audience segmentation to ensure each notification only reaches the users for whom it’s relevant.

✓ Trigger push from any automation step — alongside email and SMS
✓ Send to specific segments — not your entire app user list
✓ Schedule one-time blasts or recurring campaigns
✓ Suppress users already in a specific stage of a journey
✓ Re-engagement sequences for users who haven’t opened the app
✓ Transactional sends via REST API for order, booking, and billing events

Multi-step automation — push as one channel among many

Trigger

📦

Order shipped

Push notification

📲 “Your order shipped!”

~98% delivered

Wait

3 days

delay

Condition

Review submitted?

Push

📲 Review nudge

Yes

✉️ Thank you

Push audience 4,218 devices

Dynamic

WHERE Push enabled is true

AND Last app open within 30 days

AND Order status is shipped

Developer-first

A clean REST API. Works with any mobile framework.

DailyStory’s push notification integration is a small addition to your existing mobile app — not a heavy SDK. Register device tokens via the REST API, associate them with DailyStory contacts, and the platform handles the rest. Works with Swift, SwiftUI, Kotlin, Java, React Native, Flutter, and any framework that can make an HTTP request after obtaining a device token. Transactional pushes — order confirmations, booking reminders, billing alerts — can also be triggered directly via the API from your backend without involving the DailyStory campaign UI at all.

✓ Register device token: one POST request
✓ Associate token with a contact by email or ID
✓ Trigger transactional push from your backend via REST
✓ No proprietary SDK — any HTTP client works
✓ React Native, Flutter, Swift, Kotlin all supported
✓ Full API reference at dev.dailystory.com

Transactional push — triggered from your backend

send-push.js — backend trigger

// Send a transactional push from your server
const response = await fetch(
  `https://us-1.dailystory.com/api/v1/push/send`,
  {
    method: “POST”,
    headers: {
      “Authorization”: `Bearer ${apiKey}`,
      “Content-Type”: “application/json”
    },
    body: JSON.stringify({
      contactEmail: “jamie@example.com”,
      title: “Your booking is confirmed ✓”,
      body: “Spin class · Tuesday 7am · Studio A”,
      data: { bookingId: 9821 }
    })
  }
);

Swift Kotlin React Native Flutter Java Node.js PHP

Channel strategy

Push Notifications vs. Email vs. SMS — When to Use Each Channel.

DailyStory lets you combine push notifications with email and SMS in the same automation. Use push for real-time, in-the-moment alerts where timing matters. Use email for rich content, detailed information, and inbox longevity. Use SMS for urgent, action-required messages. The right channel at the right moment — all from a single platform.

✓ Push, email, and SMS in the same automation sequence
✓ Channel preference respected per contact
✓ Suppress push if email was already opened (reduce noise)
✓ All channels, all reporting — one dashboard

When to use each channel

📲

App Push Notification

Real-time alerts requiring immediate attention — shipping updates, appointment reminders, flash sales, booking confirmations. Requires app installed and notifications permitted.

✉️

Email Marketing

Rich content, detailed information, newsletters, receipts, and messages where inbox longevity matters. Higher engagement on complex content.

💬

SMS Marketing

Urgent, action-required messages — two-factor codes, last-chance offers, event day logistics. No app required. Highest open rate of any channel.

Everything included

Push Notification Features: Personalization, Scheduling & Rich Media.

No push notification add-on. No per-notification fees. App push is available on all paid DailyStory plans alongside email, SMS, automations, and segmentation.

🍎

Apple APNs delivery

Native iOS push delivery through Apple’s Push Notification service — reliable, fast, and directly integrated.

🤖

Google FCM delivery

Android push delivery through Firebase Cloud Messaging — covering all Android devices and form factors.

🏷️

Personalization tokens

Any standard or custom contact field as a token in push title or body — resolved individually at send time.

🤖

AI content generation

Built-in AI writing assistant generates compelling push notification copy — title, body, and emoji — in seconds.

📅

Scheduled campaigns

Schedule push notification blasts to specific segments at a precise date and time — including timezone-aware delivery.

⚡

Automation-triggered sends

Push notifications as a step in any DailyStory automation — triggered by events, conditions, waits, or campaign triggers.

🎯

Audience segmentation

Target push sends to any DailyStory segment — push-enabled contacts, device type, behaviour, purchase history, and more.

🔌

REST API integration

📊

Delivery and open tracking

Per-send reporting — delivered, opened, failed — with breakdown by platform (iOS vs Android) and campaign attribution.

🔁

Multi-channel sequences

Combine push with email and SMS in the same automation — send push first, then follow up by email if unopened.

📱

Multi-device per contact

A single contact can have multiple registered device tokens — iPad, iPhone, and Android tablet all receiving the same send.

🛡️

Opt-out management

Push permission status tracked per contact. Revoked permissions handled gracefully — no sends to opted-out devices.

Common questions

App Push Notifications FAQs

DailyStory supports both Apple iOS (via APNs — Apple Push Notification service) and Google Android (via FCM — Firebase Cloud Messaging). Both platforms are supported natively at no additional cost. The integration requires a small addition to your mobile app to register device tokens — the process is documented in the developer documentation.

No. DailyStory’s push notification integration uses plain REST API calls — no proprietary SDK is required. You obtain the device token using the standard iOS or Android notification APIs (or your cross-platform framework’s equivalent), then POST it to the DailyStory API to register the device against a contact. Any HTTP client works — Swift URLSession, Kotlin OkHttp, React Native’s fetch, Flutter’s http package, and so on.

Yes. Transactional push notifications — order confirmations, booking reminders, payment receipts, security alerts — can be sent directly from your server backend using the DailyStory REST API with an authorization key. These bypass the campaign UI entirely and are designed for real-time, event-driven notifications that need to fire immediately when something happens in your system.

Yes. DailyStory’s full audience segmentation engine applies to push campaigns. You can target by push-enabled status, device platform, last app open date, purchase history, membership tier, geography, or any other field — standard or custom — on the contact record. Only contacts who are both in the target segment and have a registered device token will receive the notification.

Yes. Push notifications are a first-class channel inside DailyStory’s automation builder. You can add a “Send push notification” step anywhere in an automation — after a trigger, following a wait step, inside a yes/no branch, or as a follow-up to an email or SMS step. This lets you build truly multi-channel journeys: push first, then SMS if unopened, then email as a final step, for example.

When a user revokes push notification permission on their device, APNs and FCM return an error on the next send attempt. DailyStory detects this automatically and marks the device token as inactive on the contact record. That contact will no longer receive push notifications until a valid token is re-registered. This is handled gracefully without affecting your overall deliverability metrics.

Yes. App push notifications are included on all paid DailyStory plans — there is no separate add-on, no per-notification fee, and no additional cost for iOS vs Android. See full pricing for plan details. You can start with a 14-day free trial to test the integration before committing.