Enable dashboard features and set behavioral defaults
Control which features are available in the dashboard and set project-level behavioral defaults.
Setting behavioral defaults
Control behaviors for your project:
- Go to Settings.
- Under Project Configuration, select Manage for Dashboard Settings.
- Toggle to enable or disable the settings, then configure as required:
Feature Description Steps Background Push Pre-loads In-App Automations and Scenes on users' devices, which increases the speed and reliability of message delivery. It is disabled by default. When disabled, the SDK downloads and refreshes the entire message list upon next app open. For information about the potential impacts of background push, see In-App Automation: Background Push. The linked information also applies to Scenes. n/a Missed Behavior Specifies how messages are handled when audience conditions are not fully met. You can override this setting on a per message basis in the Settings step in the In-App Automation and Scene composers. Select from the options described in the next table. Ban List A Ban List is an externally maintained record of users that should not be included in Airship message audiences. Before sending a message, Airship validates the audience members with the Ban List. Any matching recipients are dropped from the audience before sending the message. See Configuring your Ban List. Missed Behavior options:
Option Description Cancel The message cannot be displayed again on the device, even if the message is edited. Ignore The message will not count toward the display limit set for Repeat this message, and the waiting period will not apply. The trigger event must occur again before the message is eligible for redisplay. Increment The message will count toward the display limit set for Repeat this message, and the waiting period will apply. The trigger event must occur again before the message is eligible for redisplay.
Enabling features
- Go to Settings.
- Under Project Configuration, select Manage for Dashboard Settings.
- Toggle to enable or disable features. Message Purpose has an additional configuration step and requirements.
- App SDK minimums are listed for each feature.
- Enabling or disabling features in the dashboard does not affect API functionality.
Features you can hide/show in the dashboard:
Message Purpose
When enabled, Message Purpose requires designating each message (sent to any channel) as commercial or transactional. You must select a default value of Commercial, Transactional, or Unset.
The purpose selection appears in the Delivery step in the Message, A/B Test, Automation, and Sequence composers and in the Settings step in the Scene and In-App Automation composers. When creating messages using one of these composers, the purpose will be preset or unset according to the selected value. You can override the default per message.
If you have any scheduled or ongoing (Automation, Sequence, In-App Automation, Scene, or recurring) messages at the time of enabling Message Purpose, edit each message and select a purpose. Until you do so, Airship will send the messages as if they were set to Transactional.
Email — The commercial vs transactional designation is required for all email messages. Even when this setting is disabled, you will still set the purpose in Sender Information when creating email messages in the dashboard.
When Message Purpose is enabled and email and at least one other channel are selected for a message, the commercial/transactional designation set in the email Sender Information will apply to all channels.
For non-email messages, the message purpose informs Airship about your usage, which helps us develop better reporting.
Holdout Experiments — Message Purpose is required when using Holdout ExperimentsMeasures the effects of excluding a group of audience members from all messages or messages with specific Campaign Categories. You can compare the performance of the two audience groups in reports for selected goal events.. Message Purpose is automatically enabled when you create your first Holdout Experiment, and you cannot disable it later.
Categories