- Product documentation
- Latest Updates
- Release Notes
- Getting started
- Profiles and audiences
- Communication channels
- Get started with communication channels
- About communication channels
- Delivery best practices
- Email messages
- SMS messages
- Push notifications
- In-App messaging
- Direct mail
- Transactional messaging
- Landing pages
- Designing email content
- Testing and Sending
- Reporting
- Integrating with other solutions
- Get started with Campaign integrations
- Campaign and Experience Manager
- Campaign and Target
- Campaign and Analytics
- Campaign and Audience Manager or People core service
- Campaign and Analytics for Mobile
- Campaign and Triggers
- Campaign and Microsoft Dynamics 365
- Managing processes and data
- Get started with data and processes management
- Workflow general operation
- Executing a workflow
- Calling a workflow with external parameters
- Targeting activities
- Execution activities
- Channel activities
- Data management activities
- Filtering data
- Importing and exporting data
- Use cases
- About workflow use cases
- Deliveries
- Creating deliveries with a complement
- Creating deliveries on profiles’ creation date
- Creating a weekly delivery
- Creating a cross-channel delivery
- Identifying duplicates before a delivery
- Birthday delivery
- Coupling email and direct mail deliveries
- Sending an email with enriched fields
- Personalizing an email with additional data
- Sending a recurring push notification
- Segmentation and targeting
- Data management
- Reconcile a File audience with the database
- Deduplicating the data from an imported file
- Enriching profile data with data contained in a file
- External signal activity and data import
- Updating the database with external data
- Updating data based on an automatic file download
- Data reconciliation using relations
- Data update using reconciliation
- Exporting profiles in an external file
- Updating multiple subscription statuses from a file
- Subscribing profiles from a file to a specific service
- Working with Adobe Experience Platform audiences
- Developing
- Administrating
- Get started with Campaign Standard administration
- Monitoring guidelines
- Configuration guidelines
- Users and security
- Configuring channels
- Configuring mobile channels
- Implementing Push tracking
- Adding images and videos iOS
- Understanding push notifications payload structure
- Implementing local notification tracking
- Adobe Launch Synchronization FAQ
- Experience Platform SDK integration FAQ
- Configuring Launch rules to support Adobe Campaign Standard use cases
- Mobile use cases supported in Adobe Campaign Standard
- How to migrate your mobile application from SDK v4 to Adobe Experience Platform SDK
- Configuring SMS channel
- Application settings
- Working with APIs
- Get started with Campaign Standard APIs
- About Campaign Standard APIs
- Global concepts
- Interacting with custom resources
- Managing profiles
- Managing services and subscriptions
- Interacting with marketing history
- Privacy management
- Managing transactional messages
- Managing workflows
- Managing organizational units
- Managing geographical units
- Troubleshooting
About In-App messaging
In-App messaging is a messaging channel that allows you to display a message when the user is active within the mobile application. This message type is complimentary to push notifications which are delivered to the notification center of users’ phone. For more information on the push notification channel, refer to this section.
This channel requires mobile applications to be integrated with Adobe Experience Platform SDK. These apps have to be activated in Adobe Experience Platform Launch before being available in Adobe Campaign for In-App deliveries.
To start sending In-App messages on mobile applications leveraging Experience Platform SDK, you need to meet following prerequisites:
-
In Adobe Campaign, make sure you can access the In-App channel. If you cannot access these channels, contact your account team.
-
To leverage mobile use cases in Adobe Campaign Standard with an Experience Cloud SDK application, a mobile app has to be created in Adobe Experience Platform Launch and be configured in Adobe Campaign Standard. For the step-by-step guide, refer to this page.
-
Once configured, you can now prepare your In-App message. For more on this, refer to this page.
-
You can then decide to send an In-App message or a Customizing a local notification message type.
-
Your delivery is now ready to be sent. To learn more, refer to this page.
Related content:
In-App FAQ
What would be some useful resources recommendations to learn more about In-App channel in Adobe Campaign Standard?
Check out the resources below:
What is the purpose of Campaign extensions APIs setLinkageField and resetLinkageField?
Since In-App messages are pulled by the SDK from Campaign, we want to provide a secure mechanism to ensure that In-App Messages containing PII data do not fall into malicious hands. As such, we have following mechanism in place to ensure the secure delivery of messages to the device:
- Customers mark mobile profile fields (appSubscriberRcp table) fields as Personal and Sensitive if they want to ensure that this particular information gets delivered securely.
- Fields marked as such can only be used in Profile template (not in appSubscriber template or Broadcast template) which has additional security mechanism built in.
- Messages built using Profile template can only get served when the user has logged in the App.
- In order to facilitate this secure handshake, mobile app developers should pass additional authentification details using the setLinkageField API. Please note that the linkage field are the ones that are identified as the link between Mobile Profile and CRM Profile while extending appSubscriberRcp table.
- They should flush the In-App messages stored on the device and resetLinkagefields when the user logs out of the App using resetLinkageField. This ensures that if a different user logs into the App, they do not see the messages meant for previous user.
- Refer to Mobile SDK APIs to implement this security mechanism client side.
What do I have to do to enable In-App reporting in Campaign?
You need to configure In-App tracking postback. Instructions can be found here.
To implement local notification tracking, refer to this page.
Which reports are available for In-App channel?
An out-of-the-box report is available in Adobe Campaign for In-App channel. Refer to this documentation.
See this page to understand how each In-App metrics are calculated.
Do you support multi-lingual content variants for In-App similar to Push?
There are no multi-lingual templates available for In-App Messaging now.
However, if the objective is to send an In-App message in a language other than English, the content can be directly pasted in the available text boxes.
Can Campaign personalization fields be added to Custom HTML?
No, this is not yet supported.
I have configured an alert message but it does not display on the device.
For alert messages, at least one dismiss button (primary or secondary should have action dismiss) is required. Otherwise, it is possible to save the message but it will not be received.
If Local notifications iOS custom sound does not play; will the default sound play instead?
For custom sound on iOS, you need to provide a file name with extension when creating a local notification (for example, sound.caf). If this extension is not provided, then the default sound is used.
Are deeplinks supported in In-App messages?
Yes, deeplinks are supported in In-App messages. Deeplinks should include:
- language that states that delivery tracking needs to be disabled in order for the deeplinks to work.
- Appsflyer with Branch as partners that can do the deeplink tracking. For more information on Branch and Adobe Campaign Standard integration, refer to this page.
Can an In-App message be triggered when the user launches the app from a Push notification?
Yes, these messages are also referred as daisy chain messages. Follow the process below:
-
Create an In-App Message.
-
Define a custom event and select it as an event trigger for this IAM e.g. “Trigger from fall preview Push”.
-
When authoring your Push message, define a custom variable whose value can be set as an event used to trigger IAM e.g. Key = “inappkey” and value = “Trigger from fall preview Push”.
-
In the mobile app code, implement event trigger as follows:
