Message A/B tests

See also Scene A/B tests and Sequence A/B tests .

About A/B tests for messages

Create variants of message content by duplicating the initial variant or from scratch. Each variant returns analytic data to help you determine the most effective way to engage your audience. Audience allocation is automatically evenly distributed between variants and a control group, but you can change the percentages.

A/B tests for messages support these channels and message types:

• App — Push notifications, in-app messages, and Message Center
• Web
• Email
• SMS
• Open channel

Set up the test in two steps:

1. Create two or more message variants — Just like in the Message composer, for each variant, select channels, configure content for each channel, and set up delivery.

2. Allocate an audience — You can designate all users as eligible for the test or target specific users. Of that group, set the percentage that will participate in the test, distributed among variants and a control group. Audience members are randomly selected.

   The control group is the portion of your audience that won’t receive any messages but will be included in the performance report for comparison. If you do not want to use a control group, you can set its percentage to 0% when setting the test audience. The remaining audience, if you’ve allocated less than 100% between variants and control, won’t receive any messages and won’t be included in the report.

   Setting a lower audience percentage lets you test with a smaller group so you can effectively manage feedback and interpret results. By default, the overall audience percentage is divided evenly between variants and a control group, but you can set your own values.

After creating variants and setting the audience, you can start the test and review its results.

When running A/B tests and a Holdout ExperimentMeasures 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. simultaneously, Airship prevents holdout group users from being included in the A/B tests. This eliminates potentially skewed data in cases where there are overlapping experimentation audiences. It also ensures that the most critical experiments maintain integrity.

To prepare for your tests, see About A/B testing.

Create a message A/B test

First, select the Create dropdown menu (), then A/B Test. Or you can start from your list of all A/B tests by going to Experiments, then Message A/B Tests, and then selecting Create A/B Test.

Next, select the test name and change it to something descriptive, then select the check mark to save it.

To finish setting up your test, you must add message variants and determine the audience. You can configure them in any order.

Add message variants

You can add up to 26 variants to an A/B test:

1. Select Add variant. After completing a step, select the next step in the header to move on.

2. For Channels:

   First, select a Channel CoordinationA group of strategies for targeting users where they are most likely to receive your message. strategy:

   • Fan Out targets a Named User on all the channels they are opted in to, maximizing the chances they receive your message.
   • Last Active targets a Named User on the opted-in channel they used most recently.
   • Priority Channel targets a Named User on the first channel they are opted in to, in the priority order you set.

   Then, enable the channel types to include in your audience. For Mobile Apps, also select from the available platforms. For Priority Channel, also drag the channel types into priority order.

    Note

   For projects using the channel-level segmentation system, instead of Channel Coordination, enable the channels you want to send the message to.

   Use Channel conditions to filter which channels are included in the audience. A channel must meet the conditions to remain in the audience.

   For example, if your audience includes users with app, email, and SMS channels, and you set a channel condition requiring membership in an email Subscription List:

   • Only email channels that meet that condition would remain in the audience.
   • All app and SMS channels would be excluded.

   To set channel conditions, use the same process as when building a SegmentA reusable audience group you create by selecting unique or shared user data.. You can use the following data in your conditions:

   • AutogroupA default tag group. When devices are registered in Airship, they are automatically assigned a tag within the autogroup tag group; the tag is a numeric value of 1 to 100. Some uses for autogroup tags are creating a control group, and to randomly Segment your audience. Autogroup must be enabled for your account — contact Support or your account manager.
   • Channel IDAn Airship-specific unique identifier used to address a channel instance, e.g., a smartphone, web browser, email address.
   • Device PropertiesMetadata representing the default attributes and property tags of a device, such as language and time zone settings, OS and browser versions, and notification opt-in status. Device properties are used for audience segmentation. The data used for the tags and attributes is collected automatically from the Airship SDKs, and are updated daily.
   • EventsEvents represent activities in the Airship system, as well as user behavior in your app or website. You can also send external activities (e.g., POS transactions) into the Airship system as events. Events power Airship data products and can be used in audience segments, as Automation triggers, and for partner integrations.
   • Lifecycle ListAutomatically generated audience lists that capture app open, uninstall, notification, and dormancy information within the past 24 hours, one week, or 30 days.
   • Predicted to Churn statusAnalyzes your audience for users that exhibit behaviors indicating they are likely to become inactive, and tags the users as High, Medium, or Low Risk.
   • Subscription ListAn audience list of users who are opted in to messaging about a specific topic. Users can manage their opt-in status per list using a Preference Center.
   • TagMetadata that you can associate with channels or Named Users for audience segmentation. Generally, they are descriptive terms indicating user preferences or other categorizations, e.g., wine_enthusiast or weather_alerts_los_angeles. Tags are case-sensitive. in the device Tag GroupAn array of tags that you can associate with both channels and Named Users. — See Primary device tags.
   • Uploaded (Static) ListA reusable audience list that you create. Uploaded lists are static and updatable. In the API, they are referred to as Static Lists.

   Selected Lifecycle, Subscription, and Uploaded Lists must contain Channel IDs or Named Users as the identifier, not a mix of the two.

    Note

   Setting channel conditions is not supported for projects using the channel-level segmentation system.

   Under Localization, enable the option if you want to provide different content to app and web users depending on their language and country.

3. For Content, configure the message content per enabled channel. See the Content documentation per message type, Content options, and Localization.

4. For Delivery, configure the message delivery timing and options. See Message delivery.

5. In the Review step, review the device preview and message summary:

   • Use the arrows to page through the various previews. The channel and display type dynamically update in the dropdown menu above. You can also select a preview directly from the menu.
   • If you want to make changes, select the associated step in the header, make your changes, then return to Review.

   • Send a test message to verify its appearance and behavior on each configured channel. The message is sent to your selected recipients immediately, and it appears as a test in Messages OverviewA view of all your project’s messages, with options for editing their settings, content, status, and more..

     1. Select Send Test.
     2. (If your message includes localized content) Under Localization, select a language-country pair to apply to the test message.
     3. Under Test audience, enter at least one Named UserA customer-provided identifier used for mapping multiple devices and channels to a specific individual. or Test GroupA preview group is audience group used for previewing personalized content in the dashboard. Wherever a personalization preview is available, you can select a preview group, and its group members’ attributes will appear for any Handlebars references to attributes. You can enable any preview group as a test group so you can send test messages to its group members. These messages appear as tests in Messages Overview. and select from the results. If your message includes email, you can also search for email addresses. If no matches appear for an address, you can select Create channel for <address>, and the channel will be registered for your project and opted in to transactional messaging.
     4. (If your message contains HandlebarsHandlebars is Airship’s templating language for personalization. Handlebars expressions use double curly braces wrapped around a content template, ranging from a simple variable, e.g., {{first_name}}, to complex evaluations of personalization data.) Under Personalization, select and configure a personalization data source:

        Data source	Description	Steps
        Test message recipient	The message will be personalized using information associated with each test audience member.	n/a
        Preview Data tool	The message will be personalized using the data currently entered in the Preview Data tool. The same values will apply to all test message recipients. You can also manually edit the JSON.	(Optional) Edit the JSON data.

     5. Select Send.

   When your review is complete, select Save Variant.

To add another variant from scratch, select Add variant. To duplicate an existing variant, select the more menu icon () at the end of a row and select Copy to variant.

Set the test audience

After creating an A/B test, select Audience and then set up your test audience:

1. Choose and configure users:

   Option	Description	Steps
   All Users	This option makes the test available to a percentage of your total audience.	n/a
   Target Specific Users	This option makes the test available to a percentage of users who meet specified conditions.	Select and configure one or more conditions. Use the same process as when building a SegmentA reusable audience group you create by selecting unique or shared user data..

2. Under Audience allocation, limit the selected audience to your specified percentage.
3. (Optional) To override the default variant distribution, enable Allow uneven allocations. Then, under Variant allocation, edit the percentage for each variant and the control group.
    Note

   If you later add more variants, also update your variant allocation settings.

4. Select Save.

Start an A/B test

Once you’ve created your message variants and set the audience for your test, select Start A/B test and confirm. Each variant will send according to its delivery settings.

View test results

After starting an A/B test, discover which variant performed best. Use the test- and message-level reports to determine the quality of each variant and strategies for increasing engagement. See also Implementing A/B tests, outcomes, and compliance in About A/B testing.

To access test results, go to Experiments, then Message A/B Tests, select the more menu icon () for a test in the list, then View results. You can also select the name of a test from the list and then go to Results.

• A Performance section for each channel contains statistical data for each variant per channel and the control group, if any. Select a variant name to open its message report.
• Message Detail contains the same information and preview options shown in the Review step when creating each variant and in a variant’s message report.

To export test data, select Download CSV, then Performance Data. If your test included Custom EventsEvents that indicate that a user performed a predefined action, such as adding an item to a shopping cart, viewing a screen, or clicking an Unsubscribe button. Custom Events can trigger automation, including Sequences and Scenes. You can code them into your app or website, or send them to Airship from an external source using the Custom Event API. Custom Events contain properties that you can use to personalize messages., you will also have the option to download Variant Event Data, which is a report of event conversions and associated values, broken out by variant and control group, if any.

RTDS events

Messages used as variants in an A/B test include experiment information in Real-Time Data StreamingA service that delivers user-level events in real time to your backend or third-party systems using the Data Streaming API. events.

The Send event includes an experiments object with the test details, including experiment_id, type, and variant_id. The experiment_id also appears in the body object.

The Control event includes an experiment_id at the top level and also in the body object.

Managing A/B tests

Go to Experiments, then Message A/B Tests to view and manage your Message A/B Tests. Each test is listed by name with its status and the date it was last modified. Your last modified test is listed first. You can search for tests by name.

Options from the tests list:

Editing message variants and audience

You can edit variants and audience settings for any test that has not yet been started. After opening a test from the message A/B Tests list, select the more menu icon () for a variant and select an option:

To modify the test audience, select Audience and adjust targeting or allocation settings. See Set the test audience for configuration details.