建置區段定義 build-segments

串流區段

當新資料流入系統時，對象的設定檔清單會即時保持最新。

串流細分是持續進行的資料選擇流程，其會根據使用者活動來更新客群。 在建置區段定義並儲存產生的客群後，區段定義會在 Journey Optimizer 中套用至傳入的資料。 這表示當個人設定檔資料變更時，將會在對象中新增或移除該個人，以確保您的目標對象永遠相關。 在Adobe Experience Platform檔案中進一步瞭解。

note important
IMPORTANT
評估方法與事件資料功能是獨立的概念。 區段可設定為串流，同時以批次方式處理特定事件型別。 自​2024年11月1日起，Journey Optimizer不支援追蹤和意見回饋資料集中的傳送和開啟事件，以在任何客戶沙箱或組織中執行真正的串流分段。 這些事件仍可用於批次區段，但如果包含在串流區段中，則會以批次方式評估這些事件，且無法透過串流資格提供確定性的當天排除。 當區段定義符合Adobe Experience Platform的串流區段資格標準時，點按和其他追蹤事件可用於串流區段。 追蹤集合本身不會停止。 傳送事件產生的相關排除、跳出和延遲事件也會受到影響。 對於隱藏使用案例，請使用原生頻率上限或其他可用的商業規則。 若要回應先前在相同歷程中傳送的支援訊息，請使用回應事件，而不是將邏輯重建為對象。

批次分段

每24小時評估對象的設定檔清單。

批次細分透過區段定義一次處理所有設定檔資料，建立對象的快照，可儲存和匯出以供使用。 與串流細分不同，批次細分不會持續即時更新對象清單。 在批次程式後傳入的新資料，在下一個批次程式前不會反映在對象中。 嘗試強制立即更新不會覆寫每日週期。 如需立即的增量更新，請考慮使用串流或隨選細分選項。

如需詳細資訊，請參閱Adobe Experience Platform劃分服務檔案

邊緣分段

Edge區段能在Adobe Experience Platform中即時評估邊緣的區段，啟用相同頁面和下一頁個人化使用案例。 目前只有選取的查詢型別可使用邊緣分段進行評估。 如需詳細資訊，請參閱Adobe Experience Platform劃分服務檔案

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 build a segment definition from attributes and events to create an audience, choose its streaming, batch, or edge evaluation method, and evaluate audiences on demand for targeting in Journey Optimizer.

Intents:

• Create an audience with the Build rule method from the Audiences menu
• Use attributes and events (and components from existing audiences) as building blocks of a segment definition
• Choose the streaming, batch, or edge evaluation method for the audience
• Run on-demand (flexible) evaluation of selected audiences before targeting them
• Understand backfilling timing after an audience is first defined

Glossary:

• Segment definition: A new audience definition created with Adobe Experience Platform Segmentation Service using the Build rule method (product-specific)
• Build rule: The audience creation method selected from Create audience that opens the segment definition screen (product-specific)
• Attributes: One of the two basic building blocks of segment definitions, for example the city where profiles live or the birth year (product-specific)
• Events: One of the two basic building blocks of segment definitions, for example a purchase made within the last 7 days (product-specific)
• Streaming segmentation: Evaluation method where the audience profile list is kept up to date in real time as new data flows in (product-specific)
• Batch segmentation: Evaluation method where the audience profile list is evaluated every 24 hours as a snapshot (product-specific)
• Edge segmentation: Evaluation method that evaluates segments instantaneously on the edge for same-page and next-page personalization (product-specific)
• Flexible audience evaluation: The Audience Portal ability to run a segmentation job on demand for selected audiences (product-specific)

Guardrails:

• The frequencyMap attribute is not supported for use in segment definitions and cannot be used as part of audience segmentation criteria; for frequency-based targeting, consider frequency capping rules under business rules.
• As of November 1st, 2024, streaming segmentation no longer supports the use of send and open events from Journey Optimizer tracking and feedback datasets; this applies to all customer sandboxes and organizations.
• Send and open events can still be used in batch segments, but if included in a streaming segment they are evaluated in a batch manner; clicks and other tracking events remain available for streaming segmentation.
• Edge segmentation can currently evaluate only select query types.
• Batch segmentation is evaluated every 24 hours; attempts to force an immediate update do not override the daily cycle.
• After an audience is first defined, backfilling the audience from prior data can take up to 24 hours.
• Flexible audience evaluation lets you evaluate up to 20 audiences at a time, and ineligible audiences are automatically excluded.

Terminology:

• Canonical name: Segment definition — Acronym: n/a — variants: segment
• Do not confuse: “Streaming segmentation” (real-time updates) ≠ “Batch segmentation” (evaluated every 24 hours) ≠ “Edge segmentation” (instantaneous on the edge)

FAQ:

• Q: How do I start creating a segment definition? — From the Audiences menu, click Create audience and select Build rule.
• Q: Can I use the frequencyMap attribute in a segment definition? — No; it is not supported and cannot be used as segmentation criteria. Consider frequency capping rules under business rules instead.
• Q: Can I still use send and open events in streaming segmentation? — No; as of November 1st, 2024, streaming segmentation no longer supports send and open events from Journey Optimizer tracking and feedback datasets, though they remain usable in batch segments.
• Q: How long does backfilling take? — Backfilling the audience from prior data can take up to 24 hours after the audience is first defined.
• Q: How many audiences can I evaluate on demand at once? — You can evaluate up to 20 audiences at a time with flexible audience evaluation, and ineligible audiences are automatically excluded.

Personas:

• marketer: Can create a segment definition by selecting Create audience and then Build rule from the Audiences menu. Can drag attributes and events into the workspace, then choose a streaming, batch, or edge evaluation method for the audience. Can run flexible audience evaluation on up to 20 audiences at a time before targeting them in journeys or campaigns. The page states that backfilling the audience from prior data can take up to 24 hours after the audience is first defined. Where: “Create a segment definition”.

Onboarding:

• Level: Beginner
• First minimal step: From the Audiences menu, select Create audience, then select Build rule.
• Success check: The audience displays in the list of Adobe Experience Platform audiences after it is saved.
• Next: After creating and saving the audience, before using it in journeys: About Adobe Experience Platform audiences (audience/about-audiences.md); When responding to a message sent earlier in the same journey instead of rebuilding the logic as an audience: Reactions events (building-journeys/reaction-events.md)