Co-worker for Decisioning experience-decisioning-coworker-skills

在此页面上:​了解可用于Adobe Journey Optimizer中Decisioning的CX Enterprise Coworker技能 — 了解为何向用户档案或区段显示或未显示优惠,以及创建、解释、模拟和优化资格规则和排名公式 — 提供详细的指导、示例提示和最佳实践。

Adobe Journey Optimizer中的决策功能可帮助您解释优惠决策,并通过自然语言提示创建、测试和优化资格规则和排名公式。 使用Decisioning Explainer了解为何将选件显示给用户档案或区段,或者未显示给用户档案或区段。 使用规则和排名创建和模拟资格规则和排名公式,然后将其应用于您的决策策略。

了解详情:

Decisioning解释器 decisioning-explainer

AVAILABILITY
Decisioning Explainer适用于有权访问Co-worker和Decisioning的所有客户。

Decisioning Explainer使用自然语言回答了为什么特定选件可以或不显示给特定用户档案,或者,更广泛地说,为什么用户档案的某个区段看不到选件。 它会遍历所请求配置文件(或区段)和时间范围的完整决策栈栈:哪些选件符合条件、每个选件包含或排除哪些资格规则、频率或疲劳上限是否禁止该选件、最终排名分数、产生这些分数的策略或AI模型,以及评估配置文件依据的候选池(项目集合)。

这解决了营销人员面临的一个常见挑战:解释为什么一个优惠排名高于另一个优惠,或者解释为什么特定优惠决策会按其方式发生。 Decisioning Explainer是只读的 — 它解释了决策,但不修改规则、排名公式或选择策略。

主要用例

用例
描述
技能
示例提示
为何显示或未显示特定选件
通过复查特定时间范围的资格规则、上限、排名和候选人池来跟踪配置文件或区段的决策。
Decisioning解释器
“为什么配置文件12345在5月15日看到选件X?”

“配置文件X不符合此选件的资格吗?”

“哪个资格规则排除了此客户?”

“向我显示哪些选件配置文件X在6月3日符合资格。”
为何选件的可见性会随着时间的推移而改变
通过审核选定期间的暴露频率、疲劳或上限约束、资格和抑制,调查优惠可见性的更改。
Decisioning解释器
“为什么在过去7天内,选件Y不再向旧客户显示?”

“此客户查看过此选件多少次?”

“此选件在配置文件X中是否有上限?”

“由于上限约束,当前在配置文件X中禁止显示哪些选件?”
优惠的排名或选择方式
解释为什么一个选件排名高于另一个选件,方法是显示排名分数、策略或AI模型,以及用于用户档案的其他决策因素。
Decisioning解释器
“向我展示如何正确地选择优惠Z而不是此配置文件的其他合格优惠。”

“此决定中每个优惠的排名分数是多少?”

“为什么此配置文件的优惠A排名高于优惠B?”

“最影响排名结果的因素是什么?”
区段级别解释
跨区段聚合决策逻辑,以确定用户档案看不到选件的主要原因以及区段正在接收哪些选件。
Decisioning解释器
“对于此受众中的客户,他们被排除的最常见原因是什么?”

“此区段实际接收了哪些优惠?”

“为什么我的忠诚度区段没有看到此优惠?”

提示最佳实践

  • 已知时引用ID:提供配置文件ID、选件名称或区段名称以获取精确跟踪而不是常规答案。
  • 包含时间范围:在询问优惠的可见性发生更改的原因时,请指定日期或日期范围,以便同事可以正确设定跟踪的范围。
  • 直接询问排名细目:如果您需要评分详细信息,请明确询问排名得分或影响结果的因素。
  • 使用区段级别的问题来了解趋势:在调查为什么一组配置文件未看到选件时,请询问有关区段的信息,而不是询问单个配置文件以获取主要原因。

规则和排名 rules-ranking

AVAILABILITY
规则和排名适用于有权访问同事和决策的所有客户。

Rules & Ranking为营销人员提供了AI支持的帮助,以便创建、理解和测试决策逻辑,而无需编写或手动验证PQL语法。 它涵盖四个核心功能:自然语言规则创建、纯英语规则和排名公式解释、针对最多3个测试用户档案的模拟以及PQL优化。 它限于资格规则和排名公式,不创建或编辑选择策略或决策策略。

主要用例

用例
描述
技能
示例提示
自然语言规则创建
将纯语言资格要求转换为新规则的PQL语法或对现有规则的编辑。
规则和排名
“能否创建针对满足XYZ条件的用户的资格规则?”

“创建针对第2级或以上级别忠诚度会员的资格规则。”

“编写一个PQL规则,以排除过去7天内购买过产品的客户。”

“修改此规则,以便在禁止列表中也排除客户。”
纯英语规则和公式说明
解释资格规则或排名公式包含、排除和计算的内容,而无需用户读取PQL语法。
规则和排名
“能否用自然语言向我解释此规则?”

“此排名公式实际上做什么?”

“此资格规则以谁为目标,谁将其排除?”

“在一句话中总结此规则。”

“为什么此客户的选件A排名高于选件B?”

“此规则对于广泛的认知度促销活动限制太严格吗?”

“此规则中的哪个条件筛选掉最多的配置文件?”
模拟
针对最多三个用户档案(包括AI生成的边缘案例)测试资格规则或排名公式,以及返回通过/未通过结果或具有数值分数的排名优惠。
规则和排名
“使用测试配置文件模拟此规则。”

“此规则是否适用于loyalty_tier = gold的配置文件?”

“哪些配置文件通过此资格规则: [配置文件A、配置文件B、配置文件C]?”

“为什么此配置文件未通过资格检查?”

“为此资格规则生成测试配置文件。”

“生成对此条件进行压力测试的边缘案例配置文件。”

“在这些优惠和配置文件中模拟此排名公式。”

“给定此公式此优惠将排名最高?”

“比较此资格规则与黄金的表现。银牌客户与基础级客户。”
PQL优化
使用更简明的语法重写现有规则或公式以满足Journey Optimizer的PQL大小限制而不更改其逻辑或结果。
规则和排名
“为我优化此PQL规则。”

“此规则已达到PQL大小限制 — 能否缩短它?”

提示最佳实践

  • 显式提供目标条件:创建或修改规则时,请指明所需的确切受众、属性或排除条件。
  • 直接引用规则或公式:在要求解释、模拟或优化时,请确保您指的规则或公式是打开或明确识别的。
  • 要求边缘案例:模拟时,要求同事生成边缘案例配置文件以测试条件,而不仅仅是典型条件。
  • 在发布前进行审核:在发布之前检查生成或优化的规则的逻辑和模拟结果。
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 documents two 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; and Rules & Ranking, which creates, explains, simulates, and optimizes eligibility rules and ranking formulas in natural language, without requiring PQL syntax.

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.

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.
  • Rules & Ranking (product-specific): CX Coworker skill that creates, explains, simulates, and optimizes Decisioning eligibility rules and ranking formulas 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 Rules & Ranking can create, explain, simulate, or optimize the rule itself.
  • Ranking formula: the logic used to score and order eligible offers; Rules & Ranking can create, explain, simulate, or optimize a ranking formula, the same way it does for eligibility rules.
  • 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; Rules & Ranking generates, explains, and optimizes PQL without the marketer needing to write or validate it manually.

Guardrails

  • Decisioning Explainer and Rules & Ranking 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.
  • Rules & Ranking simulation supports up to 3 test profiles at a time, manually entered or AI-generated.
  • Rules & Ranking is scoped to eligibility rules and ranking formulas; it does not create or edit selection strategies or decision policies.

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; Rules & Ranking 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 Rules & Ranking 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 Rules & Ranking 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 Rules & Ranking simulate against at once? Up to 3, manually entered or AI-generated, including edge cases.
  • Does Rules & Ranking 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.
recommendation-more-help
journey-optimizer-help