LogoLogo
  • Home
  • Integration & SDKs
    • Web / Browser Push
      • Wordpress Integration Steps
      • Wix Integration Steps
      • Safari
        • Safari on Desktop
        • Safari on Mobile (iOS / iPadOS)
      • SDK
        • SDK Methods
        • SDK Events
        • Customizing Prompt CSS
        • AMP Support
        • E-Commerce / Abandoned Cart
    • Native App Push
      • Apple / iOS
        • P8 Key or P12 Cert Setup
        • SDK: Swift / Obj-C
          • Activity Tracking
          • Deep Linking
          • Live Activities
          • App Messages
          • Identity Synchronization
          • SDK Methods
          • SDK Delegates
        • SDK: React Native
        • SDK: Flutter
        • Advanced
          • Self-Managed Integration
        • iOS SDK Changelog
      • Android
        • Firebase App Setup
        • SDK: Kotlin / Java
          • Deep Linking
          • Activity Tracking
          • App Messages
          • Identity Synchronization
          • SDK Methods
          • SDK Callbacks
          • Live Activities
        • SDK: React Native
        • SDK: Flutter
        • Advanced
          • Self-Managed Integration
        • Android SDK Changelog
      • React Native
        • Android: Firebase App Setup
        • iOS: P8 Key or P12 Cert Setup
        • SDK: React Native
          • Deep Linking
          • Activity Tracking
          • Subscriber Matching
          • Live Activities
          • App Messages
          • SDK Methods
      • Flutter
        • Android: Firebase App Setup
        • iOS: P8 Key or P12 Cert Setup
        • SDK: Flutter
          • Deep Linking
          • Activity Tracking
          • Subscriber Matching
          • Live Activities
          • App Messages
          • SDK Methods
  • API
    • API Access Management
    • API Reference
  • Platform
    • Dashboard
    • Notifications
      • A/B Testing
      • Custom Buttons
      • Notification Previews
      • Inline Segmentation
      • Notification Templates
      • Macros
      • Native App Push Notifications
    • App Messages
    • Segments
      • Custom Geo Segmentation
    • Campaigns
    • Insights
    • User Management
    • Organizations
      • Multi-Factor Authentication
      • Single Sign On
        • Google Workspace
        • Microsoft Azure AD
        • Okta Workforce
      • Multi-Domain Notifications
      • Multi-Domain Segments
      • API Access
    • Multi-Channel Notifications
  • Info Center
    • Launch Guide & Best Practices
      • Landing Domain Whitelist
    • Web / Browser Push
      • Common Questions
      • Browser Support
      • Retrieve Push User ID
      • Not Getting Prompted
      • Not Receiving Notifications
      • How to Unsubscribe
    • Native App Push
      • Retrieve Push User ID
    • Workflow Planning
Powered by GitBook
On this page
  • Sending a Native App Notification
  • Native App Segments
  • Multi-Domain with Native Channels
  1. Platform

Multi-Channel Notifications

PreviousAPI AccessNextLaunch Guide & Best Practices

Last updated 1 year ago

Before attempting to send a Native App Notification, you must implement the appropriate technology. you can find documentation to do so. Please let your Account Manager know you’re implementing Native App so they can enable the channels in the Pushly Platform.

Sending a Native App Notification

To send a Native App Notification, the process is very similar sending a web Notification. In the ‘Create Notification’ page, you’ll see the Delivery Channels listed.

When selecting your Audience, you can hover over the Audience Size in the top right of the platform and it will show you how many users you’re targeting for each channel.

When targeting Native App users via Segments, you’ll need to ensure you create Segments specifically for Native channels. All existing Segments will be defaulted to Web Channel only. See the Segments section below to learn more on Segmentation with Native App.

For the Landing URL, if you are sending to all three Delivery Channels, then you have the option to use a different URL for the Native App sends

The Title, Body, and Image will all be the same across all Delivery Channels. The character limits for each device will vary. Like web Notifications, we suggest front loading your Title as much as possible. Body copy allows for more characters than Title.

Native App Segments

All existing Segments will automatically have the Web Delivery Channel enabled. To edit an existing Segment to allow for Native iOS and Native Android, the Segment will need to be rebuilt. If you enable/disable a Delivery Channel that has filters saved, you’ll receive an alert about the Segment getting reset and will require you to build out your filters again.

To create a Segment specifically for Native iOS and/or Native Android, enable those toggles and go from there. The filters build out will be the same process as Web.

Multi-Domain with Native Channels

Multi-domain App Notifications function the same as the primary dashboard. If you have questions, please reach out to your Account Manager.

Linked here