Use Adobe Marketing Cloud to set up in-app messages to appear in your apps.

Overview

In-App Messaging allows consumer marketers to trigger rich messaging to app users. In-App Messaging combines custom messaging with triggers to deliver specific messages only when the targeted conditions are met.

Examples:

  • Display a “Rate the Application” message after users have launched the app 5 times.
  • Direct users to a specific website after they read a certain article or a specified number of articles.
  • Send a message about important new content within the application.
  • Display a welcome screen or an interstitial HTML ad the first time the app or a browse page is launched.
  • Display a message that can be dismissed only when the user signs in.

In-App Messaging does not use Apple’s push notifications infrastructure. It is available on iOS and Android devices.

For information about In-App Messaging, see this Marketing Cloud article: Mobile Services In-App Messaging article.

Setting up in-app messaging

You can set up in-app messages to appear in both iOS and Android apps.

In-App Messaging is provided through the Mobile Marketing SDK. This requires an additional purchase through the Digital Marketing Cloud.

  1. Sign in to the Mobile Marketing Dashboard (https://mobilemarketing.adobe.com).

  2. Add or edit an app.

  3. Select the app to configure it, scroll down to SDK Analytics Options, and set a session timeout value greater than 0 seconds. Click Save.

    If you don't have access to SDK Analytics Options, contact your system administrator.

    This option specifies the length of time, in seconds, that must elapse between app launches before the launch is considered a new session. This timeout also applies when your application is sent to the background and reactivated. The time that your app spends in the background is not included in the session length.

  4. Build or rebuild your app.

    Whenever you configure app settings in the Marketing Cloud Dashboard, you must rebuild your app in On-Demand Services in order to pick up the changes.

Creating an in-app message

You can set up in-app messages to appear in both iOS and Android apps.

  1. In the Mobile Marketing Dashboard, select the app in which you want to use in-app messaging.

  2. With the app selected, click Messaging in the left rail, and then click Manage Messages.

  3. Click Create Message, and then click Create In-App.

  4. Under Audience, specify the view, trigger, and trait settings.

    When you select a trigger such as View State, the drop-down list is populated with a list of valid values based on recent analytics events. You can select these values or type your own.

    See the use cases below for a list of examples. For a list of triggers specific to AEM Mobile app, see the list at the end of this article.

    See Audience: In-App Message in Marketing Cloud help.

  5. Under Experience, specify the display, text, and button options.

    See Experience: In-App Message in Marketing Cloud help.  

  6. Under Schedule, specify when the in-app message will be active.

    See Schedule: In-App Message in Marketing Cloud help.  

  7. Click Save & Activate.

Use Cases

Launch request

At launch, display an in-app message that asks users to subscribe for email notifications.

Contextual promotion

When users navigate to a collection or article, an in-app message promotes a featured product or campaign. For example, a mobile app for a clothing store could promote a new product if a user navigates to the men's shoes collection.

Social sharing

If users are sharing articles only on Facebook, encourage them to sign up for Twitter to increase their social reach.

Triggers for AEM Mobile

For more information about these analytics event types, see Analytics Report Guide for AEM Mobile.

dps.app.pubid – Project ID string
dps.app.viewerver – Viewer version number string
dps.app.pubtitle – Publication Title (public facing) string
dps.app.viewertype – Viewer type string
dps.app.visitorid – Visitor ID (tracking identifier from AppMeasurement)
dps.app.userid – User identifier string
dps.app.vendorid – App vendor identifier string
dps.app.pubname – Publication name string
dps.app.network – Network ("online" or "offline")
dps.app.orientation – App orientation ("portrait", "landscape", "both")
dps.ref.gesture – Referrer navigation gesture ("click", "back", "swipe", or "scroll")
dps.ref.type – Referrer type (menu, home, static, dynamic) string
dps.ref.name – Referrer name string
dps.ref.title – Referrer title string
dps.col.title – Collection title string
dps.col.name – Collection name string
dps.col.layoutname – Collection layout name string
dps.col.type – Collection type (free, entitled, restricted) string
dps.nest.title – Title of the collection that was tapped
dps.nest.name – Name of the collection that was tapped
dps.article.title – Article title string
dps.article.name – Article name string
dps.article.author – Article author string
dps.ad.title – Ad title string
dps.ad.name – Ad name string
dps.ad.type – Ad type string ("static" or "eft")
dps.ad.category – Ad category string
dps.ad.advertiser – Ad advertiser string
dps.cont.lang – Content search language string ("content" refers to collection, article, or banner)
dps.cont.productid – Content product ID string
dps.cont.department – Content department string
dps.cont.access – Content access state string
dps.cont.hidden – Article or banner that is hidden from browse page
dps.cont.short – Content short abstract string
dps.cont.keywords – Content keyword string
dps.cont.internalkeywords – Content internal keyword string
dps.cont.order – Content order within collection
dps.cont.importance – Content importance (low, normal, high) string
dps.share.channel – Social sharing channel (facebook, twitter) string
dps.ban.name – Banner name string
dps.ban.title – Banner title string
dps.ban.isvideo – Banner is video (not enabled)
dps.ban.autoplay – Banner set to autoplay (not enabled)
dps.rich.type – Overlay type (not supported)
dps.rich.gesture – Overlay gesture (not supported)
dps.rich.context – Overlay context (not supported)
dps.rich.isad – Overlay ad (not supported)
dps.rich.engagement – Overlay engagement type (not supported)
dps.rich.url – Overlay URL (not supported)
dps.rich.destination – Overlay destination (not supported)
dps.rich.videoname – Overlay video name (not supported)
dps.push.id – Push notification ID string
dps.push.token – Push notification token string
dps.push.type – Push notification type string
dps.push.startup – App startup source string
dps.push.status – Push notification status string
dps.buy.type – Purchase type string
dps.subscriber.type – Subscriber type string
dps.subscriber.id – Subscriber ID string
dps.buy.subterm – Subscription tern
dps.buy.subtype – Subscription type
dps.buy.store – App Store string
dps.rich.videooffset – Overlay video offset (not supported)
dps.rich.videolength – Overlay video length (not supported)
dps.metered.consumed – Number of metered articles consumed (not supported)
dps.metered.dwelltime – Dwell time on metered articles
dps.ban.tapaction – Banner tap action
dps.ban.weblinkurl – Banner web link URL
dps.error – Error string
dps.search.term – User search term
dps.serach.refining – User search term new or refined
dps.search.resultcount – Number of search results
dps.search.position – Position within search results
dps.state – State string

Licencia na používanie tohto diela sa poskytuje v súlade s podmienkami licencie Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Na príspevky v sociálnych sieťach Twitter™ a Facebook sa nevzťahujú podmienky licencií Creative Commons.

Právne upozornenia   |   Zásady ochrany osobných údajov online