在此頁面上：瞭解推播通知資料流程、相關的重要服務和元件，以及如何透過Adobe Journey Optimizer端對端傳送通知。
此頁面可協助您設定並瞭解Journey Optimizer中推播通知的相關重要服務與工作流程。
瞭解如何在此頁面上建立推播通知。
在Adobe Journey Optimizer中設定推播頻道的步驟已詳載於此頁面。
下圖顯示與相關資料流程相關的系統和服務，重點說明如何從端對端服務角度傳送推播通知。
-
透過Apple的APN和Google FCM推送訊息服務註冊品牌行動應用程式（Android或iOS）
-
訊息服務會產生推播權杖，這是Adobe Journey Optimizer將用來以推播通知鎖定特定裝置的識別碼。
-
先前產生的推播權杖會傳遞至Adobe Experience Platform並與即時客戶個人檔案同步；這是透過易於整合的使用者端SDK在OOTB中完成
note NOTE 不同平台的Token處理方式不同。 在 Android (FCM) 上，當使用者清除應用程式快取或重新安裝應用程式，產生新的權杖和ECID時，權杖會自動標示為無效。 在 iOS (APN) 上，Token在這些情況下不會一致地被標籤為無效。 如果設定檔包含多個具有有效權杖的ECID，則會將推播通知傳送至所有關聯的裝置。 -
推送訊息是在Adobe Journey Optimizer中製作，推送訊息是根據頻道設定（即訊息預設集）建立
-
推播訊息可包含在歷程中的協調畫布上
-
在歷程發佈後，根據歷程條件的客戶設定檔符合接收推播通知的資格，在此步驟中推播訊息負載會個人化
-
個人化推播裝載會轉送至內部推播訊息傳遞服務
-
此內部服務接著會驗證與訊息相關聯之應用程式的認證，並且
-
傳送訊息至Apple與Google訊息服務，以進行最終傳送
-
訊息服務的意見反應會被記錄，錯誤和成功則會記錄在Journey Live和Customer Journey Analytics報告中
-
推播通知會傳送至一般使用者裝置
-
一般使用者推播通知互動會透過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.