인앱 채널 시작하기 gs-in-app

AI Knowledge Reference

This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.

For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.

• TL;DR: This page introduces the In-app messaging channel in Adobe Journey Optimizer, explaining what In-app messages are, when they work best, and when to consider another channel.

Intents:

• Understand what In-app messages are and how they engage app users
• Learn the purposes of In-app messages, such as promoting features, presenting offers, and onboarding
• Identify use cases where In-app messages work best
• Recognize situations where another channel is more appropriate
• Navigate to configuring, creating, designing, and reporting on In-app messages

Glossary:

• In-app message: A notification sent to users within your app, guiding them to specific points of interest such as new features, special offers, or onboarding (product-specific)
• Banner blindness: The effect where users start ignoring messages that appear too often, a risk of overusing In-app messages (product-specific)
• Active session: The condition In-app messages depend on; the user must be actively using the app for the message to be displayed (product-specific)

Guardrails:

• In-app messages depend on an active session, so they are not suited to every scenario.
• Consider another channel when the user is not actively using the app, since the message will never be displayed.
• Consider another channel for critical or time-sensitive issues that require reaching users outside the app, such as an outage or security alert.
• Consider another channel for regulatory or legal communications that require a read confirmation, which in-app messages cannot provide.
• Consider another channel for account reactivation or win-back campaigns for inactive users who are unlikely to open the app, and for high-volume transactional updates, such as an order confirmation, that are better suited to email or mobile message.
• Consider another channel when overuse could lead to banner blindness, or when users may be offline or without app connectivity when the message is meant to be delivered.

Terminology:

• Canonical name: In-app message — Acronym: n/a — variants: In-app notification, In-app messaging channel
• Synonyms: “In-app message” = “In-app notification”
• Do not confuse: “In-app messages” (delivered within the app during an active session) ≠ “push notifications” (In-app messages have no dependency on push tokens or external delivery services, and are independent of opt-in status for other channels)

FAQ:

• Q: What is an In-app message? — A notification sent to users within your app, guiding them to specific points of interest such as new features, offers, or onboarding.
• Q: When do In-app messages work best? — When you want to guide or influence users while they are already engaged with your app, taking advantage of that moment of active attention.
• Q: Can In-app messages reach users who opted out of push? — Yes; they work entirely within the app, independent of opt-in status for other channels.
• Q: When should I use another channel instead? — When the user is not in the app, for critical/time-sensitive alerts needing to reach users outside the app, for regulatory messages needing read confirmation, for account reactivation, or for high-volume transactional updates.
• Q: What is the risk of overusing In-app messages? — Banner blindness, where users start ignoring messages that appear too often.

Personas:

• marketer: Can create In-app notifications in Journey Optimizer and configure the message layout, display, text, and button options. Can trigger messages based on in-app behavior or location, such as highlighting a feature after a user visits a related screen. Can tailor layout, text, and buttons to specific audiences for personalized onboarding flows. Where: “Use cases”.

Onboarding:

• Level: Beginner
• First minimal step: Configure the In-app channel with proper mobile app configurations.
• Success check: You can access In-app reports for the channel.
• Next: Set up in-app channel prerequisites and configuration: In-app channel prerequisites and configuration (in-app/inapp-configuration.md); Create an In-app notification: Create an In-app notification in Journey Optimizer (in-app/create-in-app.md)