Push Notification Segmentation Setup for iOS, Android, and Triggers

Sending the same notification to your entire user base isn't segmentation—it's spam. CTR plummets (some clients lost up to 70% opens per month), unsubscribes rise, and iOS starts throttling delivery via Apple Push Notification throttling for apps with low engagement rates. We solve this technically, not just marketing—designing tag schemas, integrating SDKs, and setting up triggers. We guarantee a 25% increase in open rate and a halving of complaint rates.

Why segmentation matters for deliverability

Apple and Google monitor user behavior with push notifications. If too many users unsubscribe or don't open notifications, delivery gets delayed. For iOS, rate limiting occurs at the APNs level. Segmentation is the only way to maintain high deliverability. Without it, you risk 30% of notifications never reaching users.

How segmentation works at the SDK level

Any push platform (OneSignal, Firebase, Braze, Airship) builds segments from two sources: user attributes (tags, properties) and behavioral data (events, sessions, purchases).

On the client side, the task is simple—send data correctly:

// Android — after each significant action
OneSignal.User.addTag("subscription_tier", "premium")
OneSignal.User.addTag("last_active_days", "0")
OneSignal.User.addTag("preferred_category", "electronics")

// When location changes (with user permission)
OneSignal.User.addTag("region", "UA-30")

// iOS — tags and events
OneSignal.User.addTag("onboarding_completed", "true")
OneSignal.User.addTag("cart_items_count", "\(cart.items.count)")

Tags are strings. All comparison is server-side. Important: don't send a tag on every app launch—that's needless traffic. Send only when the value changes.

Behavioral segments and triggers

The most common case is trigger-based sending by event: user abandoned cart, didn't open app for 7 days, completed onboarding but didn't take first action.

This requires server-side logic. The mobile client only logs events:

// Firebase Analytics — events become available in Audience Builder
FirebaseAnalytics.getInstance(context).logEvent("checkout_started") {
    param("cart_value", 1250.0)
    param("items_count", 3L)
}

In Firebase Audiences, you can build a segment: "users who triggered checkout_started but not purchase_complete in last 24 hours"—then send a notification via FCM or Firebase In-App Messaging.

Geosegmentation

Geo segmentation for push is not "located in Kyiv right now", but "user's region from profile" or geofences.

OneSignal supports automatic location detection with setLocationShared(true). But Apple and Google are tightening background location. More reliable: pass region from user profile as a tag.

For real geofences (notification on zone entry)—CoreLocation on iOS with CLLocationManager.startMonitoring(for:) or Geofencing API on Android via GeofencingClient. This works with local notifications or silent push to update data.

Segments by device and platform

{
  "filters": [
    { "field": "device_type", "relation": "=", "value": "iOS" },
    { "operator": "AND" },
    { "field": "app_version", "relation": ">=", "value": "3.0" }
  ]
}

Useful when releasing a feature only available in a new version—don't send a deep link to a screen that doesn't exist in the old app.

Common segmentation mistakes

Tags are named inconsistently: some developers use "true"/"false", others "1"/"0", yet others simply add or remove a tag. As a result, the segment "users with tag notifications_enabled = true" misses those who simply have the tag without a value.

Better to fix tag schema in a separate enum:

object UserTags {
    const val SUBSCRIPTION = "subscription_tier"
    const val REGION = "region_iso"
    const val LAST_ORDER_DAYS = "last_order_days_ago"

    fun updateLastOrderDays(daysSince: Int) {
        OneSignal.User.addTag(LAST_ORDER_DAYS, daysSince.toString())
    }
}

Platform comparison for segmentation

Our experience and timelines

We have worked on mobile projects for many years and implemented segmentation for 20+ apps with audiences from 10,000 to 500,000 users. We use certified approaches to Apple and Google APIs.

Designing tag schema and behavioral events, implementing SDK integration on iOS + Android (or Flutter), setting up automated segments on the platform side—5–8 business days. Complex trigger chains with server-side logic (e.g., Braze Canvas or custom cron workers)—from 2 weeks.

Get a consultation on segmentation setup

If you have a project with push notifications, contact us. We'll assess your current architecture, propose an optimal segmentation schema, and give a precise cost. Experience and quality guarantees included. Request a consultation to learn how to boost open rate and reduce infrastructure load.

Push Notifications in Mobile App: APNs, FCM, Segmentation, Rich Push

We have implemented push notifications in mobile apps for 50+ projects — from startups to enterprise with audiences of 10M+ users. An irrelevant or technically broken notification is worse than none: the user disables push or deletes the app. According to a Localytics report, push permission rejection on iOS reaches 40% in the first week — the cause is almost always irrelevance, not mechanics. Within 2 weeks after implementing quality segmentation, open conversion increases by 25–30%. Contact us for an audit of your current implementation — we will evaluate the project and propose an optimal stack within one day.

How the Infrastructure Works: APNs and FCM

APNs is the only delivery channel on iOS. Everything else (OneSignal, Braze, Airship) is a wrapper on top of it. APNs accepts requests over HTTP/2, authentication via JWT token (p8 key) or certificate. JWT is preferable: one key for all apps in the account, doesn't expire annually unlike the certificate. For more details, see the official documentation.

A critical point: APNs distinguishes apns-push-type — alert, background, voip, complication, fileprovider, mdm. An incorrect type on iOS 13+ causes background notifications not to wake the app. We've seen projects where content-available: 1 was sent without apns-push-type: background — the app didn't receive silent push on some devices, and the team spent a month looking for an 'app bug'.

FCM on Android works through Google Play Services. For devices without GMS (Huawei, part of the Chinese market), Huawei Push Kit or a direct WebSocket is needed — a separate task. FCM supports data messages (handled in onMessageReceived) and notification messages (the system displays automatically if the app is in the background). Mixing them requires caution: if the notification block has a click_action but the deep link is not registered in the app, tapping the notification simply opens the main screen without navigation.

Why Segmentation Is the Foundation of Effective Push Notifications?

Sending to everyone indiscriminately quickly exhausts user loyalty. Personalized messages are clicked 3 times more often than bulk ones, and proper segmentation reduces churn by 25% (on one project it brought significant additional revenue per quarter). The cost of setting up segmentation in OneSignal or a custom backend depends on the complexity of filters.

Proper segmentation is built on several levels.

Topics are for broad categories: 'new promotions', 'order status updates'. User subscribes via FirebaseMessaging.getInstance().subscribeToTopic("orders"). Simple, but no flexible filtering.

Attribute-based segments — via OneSignal, Braze, or custom backend. We store in the user profile: language, device type, last activity, LTV segment. Notification goes only to those with last_active < 7_days and plan = premium. OneSignal allows building such filters in the interface without code.

Personalized — by specific device_token. It's important to store tokens correctly: the token updates on app reinstall, restoration from backup on a new phone, or resetting settings. On iOS, use UNUserNotificationCenter + didRegisterForRemoteNotificationsWithDeviceToken, save to backend on every launch, not just the first. Otherwise, after 3 months 30% of tokens in the database are outdated.

What Is Rich Push and How Does It Boost Conversion?

A standard notification with title and text is clicked less often than a rich push with image and action buttons — by 3 times. But implementing rich push is a separate task on each platform.

On iOS, rich content requires UNNotificationServiceExtension (to modify payload) and UNNotificationContentExtension (custom UI). The extension runs in a separate process with limited time and memory. If the extension crashes or exceeds the timeout, the system shows the original payload without media. A typical mistake is trying to load an image over HTTP (not HTTPS): ATS blocks the request, the extension silently fails, and the user sees a notification without an image.

On Android with API 26+, notifications are tied to NotificationChannel. If the channel is created with IMPORTANCE_LOW, sound and vibration are unavailable. Different notification types (transactional, marketing) should be in different channels so the user can disable marketing without losing order notifications. BigPictureStyle, MessagingStyle, InboxStyle are templates for expanded notifications. MessagingStyle with Person and avatars is the best choice for chats.

How to Track Delivery and Conversion of Push Notifications?

Sending a notification is half the work. It's important to know: was it delivered, opened, and did it lead to a target action.

FCM returns a MessageId on send, but does not guarantee a delivery callback — by design. For open tracking, custom logic is needed: on notification tap in onMessageReceived or via getInitialNotification() / onNotificationOpenedApp (OneSignal SDK), send an event to analytics with notification_id.

OneSignal provides built-in delivery and CTR analytics. For more detailed analysis — integrate with Amplitude or Mixpanel via webhook on open events. The budget for such a dashboard varies depending on event volume.

How We Implement Push Notifications: Typical Process

1. Audit current implementation — check token storage, update handling, notification types.
2. Design architecture — choose transport (FCM + APNs), segmentation layer (OneSignal/Braze/custom), personalization method.
3. Implementation — write registration code, inbound handling, rich push, deep linking.
4. Testing — send test campaigns, verify delivery on different devices, simulators, regions.
5. Monitoring and analytics — set up dashboard, open and conversion events.
6. Documentation and training — hand over operational materials to the team.

Typical stack: FCM + APNs at transport level, OneSignal or Firebase Notifications Composer for segmentation, custom backend for personalized event-based notifications. For large apps with >1M users, OneSignal has pricing limits — then we use Braze or a custom implementation on AWS SNS.

Timelines depend on complexity: basic FCM+APNs integration with transactional notifications — 1–2 weeks. A full system with segmentation, rich push, analytics, and A/B testing — 4–8 weeks. Order an audit of your current push infrastructure or get a consultation on implementing push notifications in your mobile app — we will contact you within a day and provide an accurate estimate.