在此頁面上:探索Adobe Journey Optimizer中可用於決策的CX Enterprise Coworker技能 — 瞭解優惠為何顯示給設定檔或區段、建立、解釋、模擬、最佳化及管理適用性規則、排名公式和頻率上限運算式,以及在聊天中建立決策專案 — 提供詳細指引、範例提示和最佳實務。
Adobe Journey Optimizer中的決策功能可協助您說明優惠決定、建立決定專案,以及透過自然語言提示建立、測試和最佳化適用性規則、排名公式和頻率限定運算式。 使用Decisioning Explainer來瞭解為何對設定檔或區段顯示或未顯示選件。 使用決策規則工作流程來建立和模擬適用性規則、排名公式和頻率限定運算式,然後再將其套用至您的決策策略。 使用決定優惠專案工作流程,透過描述您需要的內容來建立決定專案。
了解更多:
- Journey Optimizer的同事技能 — Journey Optimizer中跨歷程、忠誠度、內容管理及決策的同事技能概觀。
- 同事檔案 — 同事的行銷活動、聊天和專案功能概觀。
- 同事聊天UI指南 — 如何存取和瀏覽同事聊天。
決策說明器 decisioning-explainer
決策說明器會以自然語言回答為何特定優惠會或不會向指定設定檔顯示,或更廣義地說,為何設定檔區段沒有看到優惠。 它會逐步執行請求設定檔(或區段)和時間範圍的完整決策棧疊:哪些優惠方案合格、每個優惠方案包含或排除哪些適用性規則、頻率或疲勞上限是否抑制優惠方案、最終排名分數、產生這些分數的策略或AI模型,以及評估設定檔的候選集區(專案集合)。
這可解決行銷人員面臨的一個常見挑戰:說明為何一個優惠排名高於另一個優惠,或為何特定優惠決定會如常發生。 決策說明程式是唯讀的 — 它可說明決策,但不會修改規則、排名公式或選擇策略。
主要使用案例
提示最佳實務
- 已知時參考ID:提供設定檔ID、選件名稱或區段名稱,以取得精確追蹤而非一般答案。
- 包含時間範圍:詢問優惠方案的可見度為何變更時,請指定日期或日期範圍,讓同事可以正確設定追蹤的範圍。
- 直接要求排名劃分:如果您想要評分詳細資料,請明確要求排名分數或影響結果的因素。
- 針對趨勢使用區段層級的問題:在調查一組設定檔未看到選件的原因時,請詢問有關區段的問題,而非單一設定檔,以取得主要原因。
決策規則工作流程 rules-ranking
決策規則工作流程為行銷人員提供AI支援的協助,以便建立、瞭解、測試和管理決策邏輯,而不需要編寫或手動驗證PQL語法。 內容涵蓋自然語言規則建立、尋找及檢閱現有規則和公式、純英文說明、修正及驗證運算式、最多3個測試設定檔的模擬、PQL最佳化及刪除。 其範圍包括適用性規則、排名公式和優惠方案專案頻率限定運算式 — 不會建立或編輯選擇策略或決定原則。
主要使用案例
提示最佳實務
- 明確提供目標條件:建立或修改規則時,請指出您想要的確切對象、屬性或排除條件。
- 直接參考規則或公式:要求說明、模擬或最佳化時,請確定您想要的規則或公式已開啟或已明確識別。
- 要求邊緣案例:模擬時,請要求同事產生邊緣案例設定檔,以測試條件,而不僅僅是一般條件。
- 發佈前先檢閱:在發佈之前先檢查產生或最佳化的規則邏輯和模擬結果。
- 在刪除前先明確說明:請為要刪除的規則或公式命名,並檢查其先使用的位置。
決定優惠專案工作流程 decisioning-offer-item-workflow
決定優惠專案工作流程可讓您描述在聊天中需要同事的內容,更快建立決定專案。 同事會與您一起建立專案,因此您不必手動填寫決策專案建立表單的每個欄位。
當您描述專案時,同事可以協助您定義專案的標籤或標籤、資格(根據對象或現有規則)、排程、頻率限定、內容片段和自訂屬性。 如需頻率限定,您可以使用已命名的網頁或電子郵件版位,或自訂PQL條件。 您也可以使用該技能來更新、核准、取消核准、封存或永久刪除決定專案,以及從CSV檔案或清單中一次建立或更新多個專案。 若要深入瞭解這些設定,請參閱建立您的第一個決定專案。
決定優惠專案工作流程不會編寫適用性規則或管理目錄、集合或選擇策略。 若要建立或編輯適用性規則和排名公式,請使用決策規則工作流程。
主要使用案例
提示最佳實務
- 先描述專案:在第一個訊息中包含專案名稱與優惠目的,讓同事可以建立後續追蹤問題較少的專案。
- 說明您需要的限制:提及您想要的對象、日期或頻率限制,而不是將其留待稍後再說。
- 在將專案展示給設定檔之前,請先檢閱:在您核准之前,請檢查專案Co-worker建立的屬性和限制。 深入瞭解核准決定專案。
- 刪除前先明確顯示:無法復原永久刪除。 為要刪除的專案命名,並考慮改為封存該專案。
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 documents three CX Coworker skills for Decisioning in Adobe Journey Optimizer: Decisioning Explainer, which explains in natural language why a specific offer was or wasn’t shown to a profile or segment; Decisioning Rule Workflow, which creates, explains, simulates, and optimizes eligibility rules and ranking formulas in natural language, without requiring PQL syntax; and Decisioning Offer Item Workflow, which creates and manages decision items from a description given in chat.
Intents
- Understand why a specific offer was or wasn’t shown to a profile.
- Understand why an offer’s visibility to a customer or segment changed over time.
- Understand how an offer was ranked or selected over other eligible offers.
- Get an aggregated explanation of why a segment of profiles isn’t seeing an offer.
- Create a new eligibility rule, or edit an existing one, from a plain-language description.
- Get a plain-English explanation of what an existing eligibility rule or ranking formula does.
- Simulate an eligibility rule or ranking formula against test profiles.
- Rewrite a rule or formula to fit within PQL size limits without changing its logic.
- Find or list existing rules and ranking formulas.
- Fix, validate, or delete a rule or formula.
- Create an offer-item frequency capping expression from a plain-language description.
- Create a decision item by describing it to Coworker in chat.
Glossary
- Decisioning Explainer (product-specific): CX Coworker skill that explains, in natural language, why an offer was or wasn’t shown to a profile or segment, by tracing eligibility, capping, ranking, and candidate pool evaluation.
- Decisioning Rule Workflow (product-specific): CX Coworker skill that creates, finds, explains, fixes, validates, simulates, optimizes, and deletes Decisioning eligibility rules, ranking formulas, and offer-item frequency capping expressions using natural language, without requiring the marketer to write or read PQL syntax directly.
- Eligibility rule: a condition that includes or excludes an offer as a candidate for a given profile; Decisioning Explainer identifies which rule included or excluded each candidate offer, and Decisioning Rule Workflow can create, explain, simulate, or optimize the rule itself.
- Ranking formula: the logic used to score and order eligible offers; Decisioning Rule Workflow can create, explain, simulate, or optimize a ranking formula, the same way it does for eligibility rules.
- Decisioning Offer Item Workflow (product-specific): CX Coworker skill that creates decision items (offers) from a natural-language description given in chat, so you don’t have to fill in each field of the item creation form manually. It can also update, approve, unapprove, archive, or permanently delete decision items.
- Decision item: an offer or other piece of content that Decisioning can select and present to a profile; Decisioning Offer Item Workflow builds the item with you in chat.
- Capping: frequency or fatigue suppression logic that can prevent an otherwise-eligible offer from being shown; Decisioning Explainer can identify when capping suppressed an offer.
- Candidate pool (item collection): the set of offers a profile is evaluated against during a decisioning event; Decisioning Explainer reports which candidate pool was used.
- PQL (Profile Query Language): the expression syntax underlying Decisioning eligibility rules and ranking formulas; Decisioning Rule Workflow generates, explains, and optimizes PQL without the marketer needing to write or validate it manually.
Guardrails
- Decisioning Explainer and Decisioning Rule Workflow are both available for all customers who have access to Coworker and Decisioning.
- Decisioning Explainer is read-only: it explains decisions but does not modify rules, ranking formulas, or selection strategies.
- Decisioning Rule Workflow simulation supports up to 3 test profiles at a time, manually entered or AI-generated.
- Decisioning Rule Workflow is scoped to eligibility rules, ranking formulas, and offer-item frequency capping expressions; it does not create or edit selection strategies or decision policies.
- Decisioning Offer Item Workflow is scoped to decision items; it does not author eligibility rules or manage catalogs, collections, or selection strategies.
Terminology
- Do not confuse: “eligibility” (whether an offer qualifies as a candidate) is distinct from “ranking” (how qualifying candidates are ordered) and “capping” (frequency/fatigue suppression applied after eligibility and ranking) — Decisioning Explainer reports on all three separately.
- Do not confuse: Decisioning Explainer explains why a decision already made turned out the way it did for a real profile or segment; Decisioning Rule Workflow explains, creates, simulates, or optimizes the rule or formula configuration itself, independent of any specific real-world decisioning event.
FAQ
- Can Decisioning Explainer explain a decision for a single profile? Yes, ask why a specific profile did or didn’t see a specific offer, on a specific date.
- Can Decisioning Explainer explain decisions across a segment? Yes, it can aggregate the explanation across a segment to surface the dominant reason a group of profiles isn’t seeing an offer.
- Does Decisioning Explainer show ranking scores? Yes, it can return the final ranking score for each offer and which strategy or AI model produced it.
- Can Decisioning Explainer change a rule or ranking formula? No, it is read-only and does not modify decisioning configuration.
- Can Decisioning Rule Workflow create a brand-new eligibility rule from scratch? Yes, describe the target audience or condition in plain language and it generates the PQL rule.
- Can Decisioning Rule Workflow explain a rule someone else built? Yes, it can explain any existing eligibility rule or ranking formula in plain English, including what it includes, excludes, and each condition’s meaning.
- How many test profiles can Decisioning Rule Workflow simulate against at once? Up to 3, manually entered or AI-generated, including edge cases.
- Does Decisioning Rule Workflow change a rule’s logic when optimizing it? No, PQL optimization only makes the syntax more concise to fit size limits; it preserves the original logic and outcome.
- Can I create a decision item from a description in Coworker? Yes, describe the item you need to Coworker and Decisioning Offer Item Workflow builds it with you in chat.
Personas:
- marketer: Can create an eligibility rule or ranking formula from a plain-language description, without writing PQL syntax. Can simulate the rule or formula against up to three test profiles, including AI-generated edge cases, to see pass-fail results or ranking scores. The page states that Decisioning Rule Workflow does not create or edit selection strategies or decision policies. Where: “Decisioning Rule Workflow”.
Onboarding:
- Level: Beginner
- First minimal step: Describe the target audience or condition in plain language to create a new eligibility rule.
- Success check: Coworker generates the PQL rule from the plain-language description.
- Previous: Learn about Coworker skills across Journey Optimizer before using the Decisioning-specific skills: Work with AI (start/ai-features.md)