添加个性化 build-personalization-expressions

在邮件中，可以在邮件的不同位置添加个性化，如​ 主题行 ​字段。

还可以在内容的其他部分中添加它。 例如，对于推送通知，可在​标题、正文、自定义声音、徽章​和​ 自定义数据 ​字段中添加个性化设置。

在电子邮件Designer中编辑电子邮件内容时，您可以使用上下文工具栏中的图标在大多数文本元素中添加个性化设置。

Journey Optimizer还允许您个性化邮件中的​URL。 个性化 URL 可将收件人引导至网站的特定页面，或引导至个性化的微型网站，具体取决于轮廓属性。 了解详情

{width="50%"}

• 找不到“XYZ”路径

尝试引用架构中未定义的字段时。

在这种情况下，firstName1​未定义为配置文件架构中的特性：

{{profile.person.name.firstName1}}

• 变量“XYZ”的类型不匹配。 应为数组。 找到字符串。

当尝试对字符串而不是数组进行迭代时。

在这种情况下，product​不是数组：

{{each profile.person.name.firstName as |product|}}
 {{product.productName}}
{{/each}}

• 无效的Handlebars语法。 找到'[XYZ}}'

当使用了无效的Handlebars语法时。

Handlebars表达式用​ {{expression}} ​括起来

   {{[profile.person.name.firstName}}

• 区段定义无效

No segment definition found for 988afe9f0-d4ae-42c8-a0be-8d90e66e151

与电子邮件或推送消息中的优惠集成相关的错误具有以下模式：

Offer.<offerType>.[PlacementID].[ActivityID].<offer-attribute>

验证是在验证个性化编辑器中的个性化内容期间执行的。

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 how to use the Journey Optimizer personalization editor to select, build, customize, and validate personalization expressions from sources including profile attributes, audiences, offer decisions, and contextual attributes.

Intents:

• Understand where personalization can be added in Journey Optimizer (messages, Email Designer, URLs, email configuration, offers)
• Select the appropriate personalization source for an expression
• Add attributes and build expressions in the editor workspace
• Use editor tools: Find/Replace, Auto complete, Validate, Pills, Save as fragment
• Use navigation pane features: Helper functions, Favorites, Conditions, Fragments
• Validate expressions and resolve common errors

Glossary:

• Personalization editor: The central UI tool in Journey Optimizer for building, customizing, and validating personalization expressions; available wherever personalization can be defined. (product-specific)
• Personalization sources: The data categories available for building expressions — Profile attributes, Target attributes, Audiences, Offer decisions, and Contextual attributes.
• Contextual attributes: Journey- or campaign-specific data (events, properties, custom action responses) available for personalization only when a channel action is used in a journey or campaign. (product-specific)
• Pills: A personalization editor display mode that renders long attribute paths as compact, clickable tokens for improved readability. Available only for profile attributes, contextual attributes, and dynamic media. (product-specific)
• Auto complete: An editor feature that automatically suggests and completes code as you type; available only for HTML and Text formats, supporting Profile and Context attributes only. (product-specific)
• Expression fragment: A reusable personalization expression component that can be referenced across campaigns and journeys. (product-specific)
• Fallback text: A default string displayed when a string-type profile attribute is empty for a given profile; configured per attribute via “Insert with fallback text”.

Guardrails:

• Auto complete is available only for HTML and Text formats; it supports Profile and Context attributes only.
• Pills display mode is available only for profile attributes, contextual attributes, and dynamic media.
• URL personalization is available for External link, Unsubscription link, and Opt-Out link types only.
• By default, the attributes pane shows only populated attributes; toggle off “Show only populated attributes” to display all schema attributes.
• Offers model usage must contain only profile attributes; non-profile attributes in a decision cause a validation error.

Terminology:

• Canonical name: personalization editor
• Do not confuse: Personalization editor (used to build content expressions in messages, emails, push notifications, and offers — supports both Handlebars and PQL syntax) ≠ Advanced expression editor (used in the journey for conditions on data sources and event information, custom wait activities, and action parameters mapping — provides built-in functions and operators that differ from those in the personalization editor)
• Do not confuse: Profile attributes (XDM schema-based, available in all contexts) ≠ Contextual attributes (journey/campaign-specific, only available in that context) ≠ Target attributes (Orchestrated campaigns only)
• Do not confuse: Auto complete for HTML/Text (suggests personalization attribute completions) ≠ native HTML code auto-completion (the editor default when the toggle is disabled)

FAQ:

• Q: Where can personalization be added in Journey Optimizer? — In any field with the add personalization icon — including the email subject line, push notification fields (Title, Body, Custom sound, Badges, Custom data), Email Designer text elements, URLs (External link, Unsubscription link, Opt-Out), email configuration subdomains/headers/URL tracking parameters, and offer text-type representations.
• Q: What are the available personalization sources? — Profile attributes, Target attributes (Orchestrated campaigns only), Audiences, Offer decisions, and Contextual attributes (journey/campaign events and custom action responses).
• Q: How is an expression validated? — Validation runs automatically when you click Add to close the editor. You can also trigger it manually with the Validate button. Common errors include: path not found (field not in schema), type mismatch (iterating a string as array), invalid Handlebars syntax, and invalid segment definition.
• Q: What does the Pills option do? — It renders long attribute paths as compact, clickable tokens for better readability in the editor. Available only for profile attributes, contextual attributes, and dynamic media.
• Q: Why do I see only some attributes in the attributes pane? — By default, the pane shows only populated attributes. Select the settings icon above the search field and toggle off “Show only populated attributes” to display all schema attributes.