Audience: push messages

You can define and configure audience options for push messages, including date range options, Analytics segments, and custom segments.

Define audience segments

When an audience segment for push messaging is created, the segment might involve users from one or more apps because report suites or virtual report suites might contain data from one or more apps. For more information about virtual report suites, see Virtual report suites.

In Adobe Mobile Services, marketers might only push to one app per platform. If marketers attempt to push to segments that contain users from multiple apps, a warning is displayed that states that proceeding can result in serious push failures and the potential blocklisting of users. If you experience a push failure, see Resolving push failures in Troubleshooting push messaging.

To use Audience Manager data in your segment definition, see Audience Analytics.


If app users are blocklisted, marketers can never send push messages to those affected users again.

If you select an audience segment that contains users across multiple apps, you might see the following alert:

multiple app name

The app name is based on the pared down version of the appId, which is automatically sent to Adobe Analytics by the Mobile Services SDK in the <app name> <version number> (<bundle id>) format.


The version number is optional.

Up to 6 sets of numbers for the version and 5 sets of numbers for the bundle ID are removed.

For example:

  • Bea[rd]cons 1.0 (123) will appear as Bea[rd]cons
  • Bea[rd]cons 1.2 (1.2) will appear as Bea[rd]cons
  • Bea[rd]cons (1111) will appear as Bea[rd]cons .7
  • Bea[rd]cons 1.2.3. ( will appear as Bea[rd]cons (.6)

To continue to send the push message to the listed apps, select the Yes, I want to proceed. check box and click Send.

Best practices

Here are some best practices to remember:

  • To reduce confusion, avoid defining mobile app virtual report suites that contain data from multiple apps.
  • Use a unique app ID as part of an audience segment each time you want to send a push message.
    This ensures that push notifications are sent to an audience segment that belongs to only one app.


Here are some examples to help you understand how to correctly define segments:

Do: The Marketer provides push certificates for the iOS and Android versions of one app, for example, for Adobe Photoshop. The Marketer might send a push notification to a user segment that spans across both platforms.

Do not: Marketers provide push certificates for iOS and Android versions of one app, for example, for Adobe Photoshop. If the marketer creates and pushes to a segment of all active users in the last 30 days, only the users of the Adobe Photoshop iOS and Android app receive the push, and all of the Adobe Illustrator iOS and Android app users will be blocklisted. For more detailed, example see Resolving push message failures in Troubleshooting Push Messaging.

Configure audience segments

  1. Go to the Audience page for a new push message.

    For more information, see Create a push message.

    As you configure the audience options, remember the following important information:

    • The Estimated Opt-In Audience is the number of devices that match the Adobe Analytics segment and the number of opted-in devices.

      You can view an estimate of the number of users in your selected segment(s) that have opted in to receive messages and will receive the push message. The total number of app users displays below the estimate, regardless of opt-in status.

    • The Total is the number of devices that match the Adobe Analytics segment.

    • Push messages are sent to the devices that are part of a defined Adobe Analytics segment and that have opted-in for push messages.

      This means that the SDK has sent a value of True for the Push Message Opt-In evar.

    • Even though the device has a valid device token, unless Adobe Analytics has set the opted-in flag, the message is not pushed to the device.

    • For more information about troubleshooting push messaging, see the following:

  2. Type information in the following fields:

    • During The

      Type the time frame to use for the estimated audience. From the During The drop-down list, select an option:

    • Last lets you select a relative time frame (for example, the last 7 days, last 30 days, or last 60 days) from the time the message is scheduled to push.

      As an example, if you select the last 30 days and schedule the message to push on October 31, the estimated audience would be the number of users who have opted-in to receive push messages the 30 days before October 31.

    • Static Range lets you select a static range by picking the beginning and end dates for the estimated audience range.

      Using the previous example, if you select a date range beginning October 1 and ending October 15 but schedule the message to push on October 31, the estimated audience would be the number of users who have opted-in to receive push messages in the static date range that you specified (October 1 to October 15).

    • Analytics Segments

      Select an existing Adobe Analytics segment from the drop-down list. For more information, see the Segment builder in the Adobe Analytics documentation.

    • Custom Segments

      Select a metric or variable from the drop-down list (for example, Days Since Last Use or Point of Interest) and configure the filter as desired. For example, the following custom segment targets users who have a mobile phone running iOS and are in the California (United States) region.


    In the Create Audience section, if you click And, a dialog box appears that reminds you to ensure that each app that is listed must have a valid certificate. If you clicked Or, the default dialog box appears. For more information about valid certificates and report suites, see Virtual report suites.

On this page