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.