在此页面上：了解推送通知数据流、涉及的关键服务和组件，以及如何使用Adobe Journey Optimizer端到端地传送通知。
此页面可帮助您设置和了解Journey Optimizer中推送通知涉及的关键服务和工作流。
了解如何在此页面上创建推送通知。
在Adobe Journey Optimizer中配置推送渠道的步骤在此页面中有详细说明。
下图显示了与关联的数据流相关的系统和服务，重点说明了如何从端到端服务的角度交付推送通知。
-
使用Apple的APN和Google FCM推送消息服务注册品牌移动应用程序（Android或iOS）
-
消息服务生成推送令牌，该令牌是Adobe Journey Optimizer将用于通过推送通知定位特定设备的标识符。
-
以前生成的推送令牌将传递到Adobe Experience Platform并与Real-time Customer Profile同步；此操作通过OOTB与易于集成的客户端SDK完成
note NOTE 不同平台之间的令牌处理方式有所不同。 在 Android (FCM) 上，当用户清除应用程序缓存或重新安装应用程序时，令牌会自动标记为无效，从而生成新的令牌和ECID。 在 iOS (APN) 上，令牌在这些情况下不会始终被标记为无效。 如果配置文件包含多个具有有效令牌的ECID，则会将推送通知发送到所有关联的设备。 -
推送消息是在Adobe Journey Optimizer中创作的，推送消息是根据渠道配置（即消息预设）创建的
-
推送消息可能包含在历程的编排画布中
-
在历程发布后，根据历程条件的客户配置文件将获得接收推送通知的资格，推送消息有效负载将在此步骤中个性化
-
将个性化推送负载转发到内部推送消息投放服务
-
然后，此内部服务将验证与消息关联的应用程序的凭据，并
-
将消息发送到Apple和Google消息服务以进行最终投放
-
在实时和历程报表中，会记录来自消息传送服务的反馈、错误和成功，以便生成报表
-
推送通知将发送到最终用户设备
-
最终用户推送通知交互通过SDK集成从最终用户客户端作为体验事件发送
关键服务在推送通知中的角色 roles-of-key-services
-
推送通知服务提供程序是核心组件Web服务，可将通知从远程服务器传送到移动应用程序。
Adobe Journey Optimizer同时支持Android和iOS平台，因此可与以下平台集成：
- Firebase Cloud Messaging (FCM) — 将通知发送到Android移动应用程序
- Apple推送通知服务(APN) — 将通知发送到iOS移动应用程序
-
Adobe Experience Platform Mobile SDK，它通过Android和iOS兼容的SDK为您的移动设备提供客户端集成API。 SDK提供了一个Adobe Journey Optimizer扩展，用于公开特定于推送消息的各种API并启用数据流，如注册推送令牌或向Adobe Experience Platform发送推送跟踪事件或任何其他自定义体验事件。 SDK还提供多种其他扩展，这些扩展支持其他Adobe CX Enterprise以及第三方合作伙伴功能。
SDK集成还需要设置Adobe Experience Platform 数据收集服务，例如：
- 创建数据流以配置个人资料和体验事件数据集，数据流将针对这些数据集进入Adobe Experience Platform
- 创建客户端移动属性和添加扩展。 SDK与这些扩展紧密集成，以提供无缝的数据收集体验。
- 注册移动应用程序捆绑包标识符和应用程序凭据
-
Adobe Experience Platform实时客户资料通过组合来自多个渠道（包括Web、移动设备、CRM和第三方）的数据，维护每个客户的整体视图。 用户档案允许您将客户数据整合到一个统一视图中，并提供每个客户交互的带时间戳的可操作帐户。 给定应用程序用户的推送令牌将作为记录数据存储在用户的配置文件中，而用户与推送通知的交互将作为时间序列事件数据受到跟踪。 了解有关Adobe Experience Platform实时客户个人资料的更多信息。
-
Adobe Journey Optimizer ：一旦您的移动应用程序与上述组件集成就绪并且您的客户配置文件位于Adobe Experience Platform中，您就可以在Adobe Journey Optimizer中创作并编排推送通知以与您的用户进行互动。
推送技术设置和从业者工作流 push-technical-setup
下图显示了配置构成推送数据流骨架的组件时涉及的端到端各个步骤。 已根据执行配置的角色和正在配置的组件对措施项进行了分类。
相关主题
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 explains the end-to-end push notification data flow in Journey Optimizer and the roles of the key services and components involved in delivering push notifications.
Intents:
- Understand the end-to-end push notification data flow from app registration to delivery and interaction tracking
- Identify the key services and components involved in push notifications
- Understand how push tokens are generated, synchronized with the Real-time Customer Profile, and used for targeting
- Understand how push messages are authored, personalized, and delivered through Apple and Google messaging services
Glossary:
- Push token: An identifier generated by the messaging services that Journey Optimizer uses to target a specific device with a push notification (product-specific)
- Push notification service providers: The core component web services (FCM for Android, APNs for iOS) that deliver notifications from remote servers to mobile apps (product-specific)
- Adobe Experience Platform Mobile SDK: The client-side integration SDK that provides an Adobe Journey Optimizer extension for registering push tokens, sending push tracking events, and other experience events (product-specific)
- Real-time Customer Profile: The Adobe Experience Platform profile that stores the push token as record data and tracks push interactions as time-series events data (product-specific)
- Channel configuration: The message preset that push messages are created against in Journey Optimizer (product-specific)
Guardrails:
- Token handling differs between platforms: on Android (FCM), tokens are automatically marked invalid when users clear app cache or reinstall the app, generating a new token and ECID; on iOS (APNs), tokens do not consistently get marked invalid in these scenarios.
- If a profile contains multiple ECIDs with valid tokens, push notifications are sent to all associated devices.
- Journey Optimizer supports both Android and iOS platforms, integrating with FCM (Android) and APNs (iOS).
- SDK integration also requires setup of Adobe Experience Platform Data Collection services, including creating a datastream, a client-side mobile property with extensions, and registering the mobile app bundle identifier and app credentials.
Terminology:
- Canonical name: Push notification data flow — Acronym: n/a — variants: push data flow, push notification components
- Synonyms: “channel configuration” = “message preset”
- Do not confuse: “APNs” (Apple Push Notification Service, iOS) ≠ “FCM” (Firebase Cloud Messaging, Android)
- Do not confuse: “push token” (device identifier stored as record data on the profile) ≠ “push interactions” (tracked as time-series events data)
FAQ:
- Q: How is a device targeted for a push notification? — Messaging services generate a push token, which is passed to Adobe Experience Platform and synchronized with the Real-time Customer Profile, and Journey Optimizer uses it to target the specific device.
- Q: Which providers does Journey Optimizer integrate with? — Firebase Cloud Messaging (FCM) for Android and Apple Push Notification Service (APNs) for iOS.
- Q: Why might a user receive a push on multiple devices? — If a profile contains multiple ECIDs with valid tokens, push notifications are sent to all associated devices.
- Q: Where is the push token stored? — Against the user’s profile as record data, while push interactions are tracked as time-series events data.
- Q: Where are delivery successes and errors reported? — Feedback from messaging services is logged for reporting in Journey Live and Customer Journey Analytics reports.