Set optional features

You can enable optional features in the Settings step of the Scenes composer. Each feature’s purpose and settings are detailed here. Scenes are an AXP feature.

Specify start and end dates

Set start and end dates and times during which your Scene can be displayed.

Click the date field and either use the date picker, or enter a date in YYYY-MM-DD format, then select the time and time zone.

Repeat this Scene

Configure the maximum number of times a Scene may be displayed and the minimum waiting period before it is eligible for redisplay.

Enter the maximum number of times the Scene may be displayed, then enter the minimum number of minutes, hours, or days that must elapse before a Scene becomes eligible for redisplay.


TriggersAn event that causes an in-app automation message, scene, or survey to appear to your audience. are not monitored while a Scene is ineligible for display. The trigger event must occur again after the minimum time elapses before the Scene will redisplay.

For example, if you set the maximum number of displays to 3 and the minimum time between displays to 1 week, the Scene will display a maximum of 3 times and at most once per week.


Use this option if you want your Scene to be eligible to be repeated (redisplayed) to your users. Redisplaying your Scene is useful because users can dismiss or ignore your Scenes.

Choose message priority

Assign a priority to ensure that your audience sees the most important Scenes first.


Priority is shared across Scenes and In-App Automation, which is why we are referring to priority here as “message priority” rather than Scene priority.

For example, you may have two Scenes configured to display on the next app open: an urgent account security warning, and a promotional marketing Scene. If you have assigned a high priority to the security warning and a lower priority to the marketing Scene, the higher priority Scene will appear first.

Use the slider to set rough priorities, or look at the number value to make fine distinctions.


Setting a priority is useful because multiple Scenes can become eligible for display at one time.


Setting a priority does not guarantee one Scene will display before another, because all other other conditions must be met for a Scene to become eligible for display. Priority is available as a tiebreaker when you have multiple Scenes ready for display.

Ignore Message Limits

Enable this option to override the project-level Message LimitsLimits that cap the number of messages you can send within a specified time frame, preventing you from over-messaging your users. They are set at the project level. , ensuring that your audience will receive your Scene even if they’ve reached the message limit (message limits include Scenes and In-App Automations). You may want to override message limits for important Scenes like breaking news, account alerts, or location proximity-based Scenes.


This will exist only be presented if one or more multiple-channel message limit exists.

Campaign Categories

Campaign categories are labels that group messages of a similar type or messaging strategy for aggregate reporting. Campaigns help you track the efficacy of both your individual messages and a messaging campaign as a whole.

Enter a campaign category name, then click Add. Click the X next to any category to remove it. Category names have a 64-character maximum. Enter up to ten.

When adding a category defined in message limits, the category will display the message limit rules with an option to override the limit for this send. Click the check box next to “Ignore limit for this message” to override the limit for this category.


Campaign categories are listed in the Message Detail section of Message Reports.

Override default missed behavior action

Override the project-level setting, specifying how the Scene is handled when audience conditions are not fully met. Select one of:

  • Cancel: The Scene cannot be displayed again on the device, even if the Scene is edited.

  • Ignore: The Scene will not count toward the display limit set in Repeat this Scene, and the waiting period will not apply. The trigger event must occur again before the Scene is eligible for redisplay.

  • Increment: The Scene will count toward the display limit set in Repeat this Scene, and the waiting period will apply. The trigger event must occur again before the Scene is eligible for redisplay.

Custom Keys

Custom keys are additional key-value pairs in your push notification payload for use by custom code in your app. You can use custom keys to pass additional campaign identifiers for analytics, pass user information to the device, control the look and feel of the app, provide image links, etc.