ÃÛ¶¹ÊÓƵ

From ÃÛ¶¹ÊÓƵ Campaign home page, click the In-App messaging card.

You can also create an In-App from the Marketing activities tab, by clicking the Create button.

Note that an In-App message can also be created from a campaign or from the ÃÛ¶¹ÊÓƵ Campaign home page or in a workflow.

Select In-App message.

Select an appropriate template based on your audience targeting needs.

By default, you can select one of the following three out-of-the-box templates:

• Target users based on their Campaign CRM profile (inAppProfile)
• Target all users of a Mobile app (inAppBroadcast)
• Target users based on their Mobile profile (inApp)

Enter the In-App message properties and select your mobile app in the Associate a Mobile App to a delivery field.

If you don’t see any applications in the drop-down list, make sure that your mobile applications are in a Configured state. Applications in a Ready to be configured state will not appear in the list. For more information on mobile application configuration, refer to this page.

Select the audience you want to target for you In-App message. Your audience is prefiltered depending on the mobile application associated to this delivery.

Note that this step is not needed with the Broadcast an In-App message (inAppBroadcast) since it targets all users of a mobile application.

In the Triggers tab, drag and drop the event that will trigger your message. By choosing a trigger, you choose an action done by users which will cause the In-App message to be displayed.

Four categories of events are available:

• Mobile Application events: Custom events implemented in your mobile application.

  For more on events creations, refer to this page.

• Life Cycle events: Out-of-the-box life cycle events supported by ÃÛ¶¹ÊÓƵ Mobile SDK.

  For more on life cycle events, refer to this .

• Analytics Events: The following three categories are supported depending on what is instrumented in your mobile app: ÃÛ¶¹ÊÓƵ Analytics, Context data or View state.

  Please note that these events are only available if you have an ÃÛ¶¹ÊÓƵ Analytics license.

• Places: The following three categories leverage real-time location data to deliver contextually relevant mobile experiences: Places context data, Places custom metadata or Places event type.

  For more information on ÃÛ¶¹ÊÓƵ Places, refer to the Places documentation.

If you use an Analytics Events, ÃÛ¶¹ÊÓƵ Analytics and View state events will be automatically populated based on the report suites configured in the Analytics extension in the Data Collection UI whereas Context data events have to be manually added.

Please note that these events are only available if you have an ÃÛ¶¹ÊÓƵ Analytics license.

If you use a Places trigger, Places context data, Places custom metadata or Places event type will be automatically populated based on all the Libraries and their Points of Interest created in ÃÛ¶¹ÊÓƵ Places.

Please note that this trigger will be applied on the device only for the Points of Interest from the Libraries selected in the Places extension in the Data Collection UI. For more information on the Places extension and how to install it, refer to this .

In the Frequency & duration tab, choose the frequency for your trigger, the start and end date, day of the week and time of the day when your In-App message will be active.

Edit the content of your message and define the advanced options. See Customizing an In-App message.

Click Create.

Click the Preview button.

Click the Select a test profile button and select one of your test profiles to start previewing your delivery. For more information on test profiles, refer to this section.

Check your message on different devices such as Android, iPhone phones or even tablets. You can also check if your personalization fields are retrieving the right data.

You can now send your message and measure its impact with delivery reports.

Click Prepare to compute the target and generate the messages.

Once the preparation has finished successfully, the Deployment window presents the following KPIs: Target and To deliver.

You can check the Deployment window by clicking the button for potential exclusions or errors in your delivery.

Click Confirm to start sending your In-App message.

Check the status of your delivery through the message dashboard and logs. For more on this, refer to this section.

Delivered and Sent KPIs counts are based on what is successfully sent out from Campaign to Message delivery service. Please note that these KPIs are not an indication of the count of mobile devices that received or downloaded the message successfully from Message delivery service.

Measure the impact of your In-App messages with delivery reports. For more on reporting, refer to this section.

After sending your In-App messages, you can choose to deactivate your delivery. This can be useful if you want to stop a particular delivery or if you want to run a new delivery with the same trigger for example.

Click Deactivate then Ok to start the deactivation request.

Once the request has been sent, your delivery will be deactivated and no other message will be sent.

Note that your reports for this delivery will still be accessible.