在此页面上：开始使用 Adobe Journey Optimizer 中的推送通知，以便通过历程和营销活动联系您的移动应用程序用户和 Web 访客。
推送通知可帮助您随时联系移动应用用户和 Web 访问者，尤其是当他们未主动使用应用或浏览网站时。 推送通知可帮助您实现各种用例，例如提供有关服务的更新、要求用户执行操作、向用户发送新交易的提醒等。 终端用户需要先选择启用，设备平台才会允许其接收或查看通知。 用户可在应用程序安装完成后首次启动时、后续会话或工作流程中（视情况而定）选择启用。
Journey Optimizer 支持推送通知，并帮助您以行业领先的吞吐率发送高度相关的通知。 推送通知可能包含个性化和基于历程的上下文，以便利用您的品牌在 Adobe CX Enterprise 中拥有的数据洞察。
可以通过以下方式创建推送通知：
-
在 历程 中：在历程中添加推送活动并定义基本设置后，请使用 操作：推送 右侧窗格，创建推送通知内容。 了解如何创建历程
-
在 营销活动 中：创建营销活动后，选择推送通知作为您的操作并定义基本设置。 了解如何创建操作营销活动 | API 触发的营销活动 | 编排的营销活动
使用专用选项卡定义 iOS、Android 和 Web 平台的推送通知设置。
用例
当您需要直接快速联系用户的设备时，推送通知的工作效果最佳，无需用户进入您的应用程序或检查其收件箱。
何时不使用
推送通知不适合每条消息。 在以下情况下考虑其他渠道：
- 您的受众推送选择启用率较低，或者对通知表现出抵制态度，因为消息可能根本无法触达他们
- 消息需要长格式内容，电子邮件可处理得更好，并允许更详细的格式设置
- 该内容是敏感内容或隐私内容，不应在锁屏界面中显示，因为在该界面中，设备附近的任何人都可以看到
- 您的大多数用户都从桌面而不是移动应用程序访问您的服务，因为推送通知在此类应用程序中的覆盖范围有限或无法触达
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 push notifications in Journey Optimizer for reaching mobile app users and web visitors through journeys and campaigns, and covers when to use or not use the channel.
Intents:
- Understand what push notifications enable in Journey Optimizer
- Decide whether to create a push in a journey or a campaign
- Define push settings for iOS, Android, and Web platforms
- Evaluate use cases where push is the right channel and where it is not
- Understand how push opt-in and opt-out are handled
Glossary:
- Push notification: A message that reaches mobile app users and web visitors at any time, including when they are not actively using the app or website (product-specific)
- Opt-in: The consent device platforms require before end-users can receive or view notifications, obtainable as early as first app launch post-install (product-specific)
Guardrails:
- Before creating a push notification for the first time, the Push channel must be configured.
- Device platforms require opt-in before end-users may receive or view notifications.
- Push notifications do not require opt-out management on your side: recipients unsubscribe through their devices, and their notification settings via the mobile OS or web browser.
Terminology:
- Canonical name: Push notification — Acronym: n/a — variants: push, notification
- Synonyms: “mobile app users and web visitors” = target recipients of push
- Do not confuse: creating a push “In a Journey” ≠ creating a push “In a Campaign”
FAQ:
- Q: Where can push notifications be created? — In a Journey (via a Push activity) or in a Campaign (by selecting Push notification as the action).
- Q: Which platforms are supported? — iOS, Android, and Web, configured via dedicated tabs.
- Q: Do I need to manage push opt-out? — No, recipients can unsubscribe through their devices or via mobile OS / browser notification settings.
- Q: When should I not use push? — When opt-in rates are low, the message needs long-form content, the content is sensitive and shouldn’t appear on a lock screen, or most users are on desktop.
- Q: How do I check a profile’s push consent status? — In the AEP profile viewer, via Check push opt-out status.