대상자 강화 속성 사용 enrichment

데이터 보강 속성이란 무엇입니까?

데이터 보강 속성은 상황에 맞는 추가 속성이며 대상에만 국한됩니다. 프로필과 연결되어 있지 않으며 일반적으로 개인화 목적으로 사용됩니다.

데이터 보강 속성은 대상 구성 또는 사용자 지정 업로드 프로세스의 데이터 보강 활동을 통해 대상에 연결됩니다.

Journey Optimizer 내에서 데이터 보강 속성을 사용할 수 있는 곳은 어디입니까?

대상자 구성의 데이터 보강 속성은 다음 영역에서 활용할 수 있습니다. 대상 데이터 보강 특성을 사용하는 방법을 알아보세요

• 조건 활동(여정)
• 사용자 지정 작업 특성(여정)
• 메시지 개인화(여정 및 캠페인)

여정에서 데이터 보강 속성을 활성화하려면 어떻게 해야 합니까?

작성 워크플로를 사용하여 만든 대상의 데이터 보강 속성을 사용하려면 해당 속성이 “ExperiencePlatform” 데이터 Source 내의 필드 그룹에 추가되어 있는지 확인하십시오. 필드 그룹에 데이터 보강 특성을 추가하는 방법에 대한 정보는 이 섹션에서 확인할 수 있습니다.

여정이 시작된 후 데이터 보강 속성 값이 업데이트됩니까?

현재는 없습니다. 대기 노드나 이벤트 여정 후에도 데이터 보강 속성 값은 이벤트가 시작될 때와 동일하게 유지됩니다.

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 explains how to use audience enrichment attributes from composition workflows, custom uploads, and Federated Audience Composition to create journey paths and personalize messages in Journey Optimizer.

Intents:

• Use enrichment attributes from targeted audiences to build journeys and personalize messages
• Create multiple paths in a journey based on rules that leverage the audience’s enrichment attributes
• Personalize messages in journeys or campaigns using enrichment attributes in the personalization editor
• Add enrichment attributes from composition workflows to a Field Group in the ExperiencePlatform Data Source
• Understand where enrichment attributes can be used and when their values are updated

Glossary:

• Enrichment attributes: Additional attributes that are contextual and specific to an audience, not associated with the profile, and typically used for personalization purposes (product-specific)
• Enrich activity: The activity in audience composition (or the custom upload process) that links enrichment attributes to an audience (product-specific)
• Field Group (ExperiencePlatform Data Source): The Field Group within the “ExperiencePlatform” Data Source to which composition-workflow enrichment attributes must be added before use (product-specific)

Guardrails:

• Audiences created through CSV file custom upload before October 1, 2024, are not eligible for personalization; to use their attributes, re-create and re-upload the external CSV audience.
• Consent policies do not support enrichment attributes; consent policy rules should be based only on attributes found in the profile.
• To use enrichment attributes from audiences created using composition workflows, they must be added to a Field Group within the “ExperiencePlatform” Data Source.
• Enrichment attribute values are not updated after a journey starts; even after wait or event nodes, the values remain the same as when the journey started.

Terminology:

• Canonical name: Enrichment attributes — Acronym: n/a — variants: audience enrichment attributes
• Synonyms: “custom upload” = “custom (CSV file) audience”
• Do not confuse: “Enrichment attributes” (contextual, specific to an audience, not associated with the profile) ≠ “profile attributes” (found in the profile; the basis for consent policy rules)

FAQ:

• Q: What are enrichment attributes? — Additional attributes that are contextual and specific to an audience; they are not associated with the profile and are typically used for personalization.
• Q: Where can I use enrichment attributes within Journey Optimizer? — In Condition activities (Journeys), Custom action attributes (Journeys), and Message personalization (Journeys and campaigns).
• Q: How do I enable enrichment attributes from composition workflows in journeys? — Add them to a Field Group within the “ExperiencePlatform” Data Source.
• Q: Are enrichment attribute values updated after a journey starts? — Currently no; even after wait or event nodes, values remain the same as when the journey started.
• Q: Are older CSV custom upload audiences eligible? — Audiences created through CSV custom upload before October 1, 2024, are not eligible for personalization and must be re-created and re-uploaded.