护栏和限制 guardrails

在此页面上:​查看适用于编排的营销活动中数据存储、摄取、数据建模、活动和渠道的护栏和限制。

下面显示了使用编排的营销活动时的护栏和限制。

数据流限制

数据设计和存储

  • 最大表数 — 关系数据存储最多支持200个表(架构)。

  • 架构大小 — 对于编排的营销活动,任何单个架构的总大小不得超过100 GB。

  • 每日更新卷 — 为保持性能和稳定性,对架构的每日更新应限制为少于其总记录计数的20%。

  • 关系数据模型 — 关系数据是支持摄取、数据建模和分段用例的主要模型。

  • 标识字段 — 用于定位的架构必须至少包含一个类型为String且映射到定义的标识命名空间的标识字段。

  • 每个架构的属性 — 每个架构的平均属性数不应超过50列以保持可管理性和性能。

  • 配置文件启用 — 无法为Adobe Experience Platform配置文件启用关系架构。 Adobe Experience Platform配置文件仅支持标准XDM架构。 可以为编排的营销活动或操作营销活动启用关系架构。 了解详情

数据引入 data-ingestion

  • 配置文件和关系摄取 — 需要配置文件+关系数据摄取。

  • 更改数据捕获源 — 所有引入都必须通过更改数据捕获源进行:

    • 基于文件的源 - _change_request_type字段必填。 支持的值为u (更新插入)或d (删除)。 这些值必须为小写的 u 和 d,而不是大写的 U 和 D。

    • 基于云的源 — 必须启用表日志记录。

  • 仅完整记录 — 不允许部分记录更新;每行都必须作为完整记录提供。

  • 批次摄取频率 - Campaign Orchestration的批次摄取限制为每15分钟一次。

  • 摄取延迟 — 关系存储中的摄取延迟通常为15分钟到2小时,具体取决于:

    • 数据量

    • 系统并发

    • 操作类型(例如,插入操作比更新操作快)

  • 数据流到数据集关系 — 数据流到数据集关系是1-1。 在给定时间,只有一个源可以馈送一个数据集。 要切换源,请删除现有数据流,然后使用新源创建新数据流。

数据建模

  • 版本描述符 — 所有架构(包括事实表)都必须包含版本描述符,以确保正确的版本控制和可跟踪性。

  • 主键 — 每个表都必须具有定义的主键,以支持数据完整性和下游操作。

  • 永久表名称 — 在数据集创建期间分配的table_name是永久的,用于分段和个性化功能。

  • 字段组 — 当前数据建模框架不支持字段组。

  • 复合主键 — 目前不支持具有文件上载流的复合主键。

受众

  • 仅限标量属性 — 受众定义中仅支持标量属性;不允许映射和数组。

  • 用于分段的关系数据 — 分段活动主要依赖关系数据。 虽然可以包含配置文件数据,但使用大型配置文件数据集可能会影响性能。

  • 配置文件属性限制 — 对可在批处理受众和流式受众中使用的配置文件属性数实施限制,以保持系统效率。

  • 枚举 — 完全支持枚举。

  • 未缓存读取受众 — 未缓存读取受众;每个活动执行都从基础数据触发完整的受众评估。

  • 受众优化 — 在使用大型或复杂的受众定义时,强烈建议进行优化,以确保性能。

  • 已保存受众

    • 保存的受众是静态的 — 保存的受众活动是静态的;它们反映的是活动执行时可用的数据。
  • 未附加到保存的受众 — 不支持附加到保存的受众活动。 任何修改均需要完全覆盖受众。

活动限制 activities-limitations

  • 渠道活动限制 — 编排的营销活动最多支持10个渠道活动(电子邮件、手机消息、推送或直邮)。 只有渠道活动才会计入此限制。 定位、数据管理和流量控制活动不计算(例如,构建受众、加载文件、等待、拆分、扩充、协调、分支、结束或测试)。

    如果保存或发布时超出限制,则操作失败。 要保持在限制之内,请减少渠道活动的数量,或在多个编排的活动中拆分消息投放。

  • 画布活动限制 — 已编排的活动画布上的活动数限制为500。 此限制适用于画布上的所有活动类型。 它与发布时实施的渠道活动限制不同。 为了提高可维护性和性能,请将工作流限制在实践中的100个以内。

渠道限制

编排的营销活动仅支持移动设备消息、推送、电子邮件、LINE、自定义渠道和直邮渠道。

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 lists the guardrails and limitations for Orchestrated campaigns across data storage, ingestion, data modeling, audiences, activities, and channels.

Intents:

  • Determine how much relational data a schema can hold and how fast it can grow before performance is affected.
  • Identify how data must be ingested into the relational store, including required fields and timing.
  • Understand data modeling requirements such as version descriptors and primary keys.
  • Learn which audience attribute types and audience behaviors are supported.
  • Determine how many channel activities and total activities an Orchestrated campaign canvas can contain.
  • Identify which channels are supported in Orchestrated campaigns.

Glossary:

  • Relational datastore: the storage layer for Orchestrated campaigns that supports a maximum of 200 tables (schemas) (product-specific)
  • Change Data Capture sources: the required ingestion method for Orchestrated campaigns, which can be file-based (using the _change_request_type field) or cloud-based (using table logging) (product-specific)
  • Table name: the table_name assigned during dataset creation, used throughout segmentation and personalization features (product-specific)
  • Read Audiences: audience activities that trigger a full audience evaluation from the underlying data at each campaign execution, rather than using cached results (product-specific)
  • Saved audience: an audience activity that is static and reflects the data available at the time of campaign execution (product-specific)

Guardrails:

  • Maximum tables: the relational datastore supports a maximum of 200 tables (schemas) (hard limit).
  • Schema size: the total size of any individual schema must not exceed 100 GB (hard limit).
  • Daily update volume: daily updates to a schema should be limited to less than 20% of its total record count to maintain performance and stability (recommended).
  • Relational data is the primary model supported for ingestion, data modeling, and segmentation use cases.
  • Schemas used for targeting must contain at least one identity field of type String, mapped to a defined identity namespace.
  • Attributes per schema: the average number of attributes per schema should not exceed 50 columns to maintain manageability and performance (recommended).
  • Relational schemas cannot be enabled for Adobe Experience Platform Profiles (hard limit); only Standard XDM schemas are supported for Adobe Experience Platform Profiles. Relational schemas can be enabled for Orchestrated campaigns or Action campaigns.
  • Profile + relational data ingestion is required.
  • All ingestion must occur via Change Data Capture sources.
  • File-based sources require the _change_request_type field, with supported values u (upsert) or d (delete), lowercase only.
  • Cloud-based sources require table logging to be enabled.
  • Partial record updates are not allowed; each row must be provided as a complete record.
  • Batch ingestion frequency for Campaign Orchestration is limited to once every 15 minutes (hard limit).
  • Ingestion latency in the relational store typically ranges from 15 minutes to 2 hours, depending on data volume, system concurrency, and type of operation (for example, inserts are faster than updates).
  • The dataflow to dataset relationship is 1–1: only one source can feed one dataset at a given time. To switch the source, delete the existing dataflow and create a new dataflow with the new source.
  • All schemas, including fact tables, must include a version descriptor.
  • Each table must have a defined primary key.
  • The table_name assigned during dataset creation is permanent.
  • Field groups are not supported in the current data modeling framework.
  • Support for composite primary keys with file-upload flows is not available at this time.
  • Only scalar attributes are supported in audience definitions; maps and arrays are not allowed.
  • Segmentation activities primarily rely on relational data; profile data can be included, but using large profile datasets may impact performance.
  • Limits are enforced on the number of profile attributes that can be used in both batch and streaming audiences, but the page does not state the figures.
  • Enumerations are fully supported.
  • Read Audiences are not cached; each campaign execution triggers a full audience evaluation from the underlying data.
  • Audience optimization is strongly recommended when working with large or complex audience definitions (recommended).
  • Saved audience activities are static; they reflect the data available at the time of campaign execution.
  • Appending to a Saved Audience activity is not supported; any modifications require a full overwrite of the audience.
  • An Orchestrated campaign supports a maximum of 10 channel activities (Email, Mobile message, Push, or Direct mail) (hard limit, enforced when saving or publishing). Only channel activities count toward this limit; Targeting, Data Management, and flow control activities (for example, Build audience, Load file, Wait, Split, Enrichment, Reconciliation, Fork, End, or Test) do not count. Exceeding the limit causes the save or publish operation to fail.
  • The number of activities on an Orchestrated campaign canvas is limited to 500 (hard limit), covering all activity types. This limit is separate from the channel activities limit enforced at publication.
  • Keep workflows under 100 activities in practice for maintainability and performance (recommended).
  • Only Mobile message, Push, Email, and Direct mail channels are supported in Orchestrated campaigns.

Terminology:

  • Canonical name: channel activities — variant: channel activities limit
  • Do not confuse: channel activities limit (maximum 10 Email, Mobile message, Push, or Direct mail activities, enforced when saving or publishing) ≠ canvas activities limit (maximum 500 activities of any type on the canvas)
  • Do not confuse: “Read Audiences” (not cached, evaluated fully at each campaign execution) ≠ “Saved audiences” (static, reflecting data at the time of campaign execution)

FAQ:

  • Q: How many tables does the relational datastore support? — A maximum of 200 tables (schemas).
  • Q: How many channel activities can an Orchestrated campaign have? — A maximum of 10 channel activities (Email, Mobile message, Push, or Direct mail); exceeding this limit causes the save or publish operation to fail.
  • Q: How many activities total can be on the canvas? — Up to 500 activities of any type; this is separate from the channel activities limit.
  • Q: Which channels are supported in Orchestrated campaigns? — Mobile message, Push, Email, and Direct mail.
  • Q: Can relational schemas be enabled for Adobe Experience Platform Profiles? — No; only Standard XDM schemas are supported for Adobe Experience Platform Profiles.
  • Q: Can I append data to a Saved Audience activity? — No; any modifications require a full overwrite of the audience.

Personas:

  • admin: Can reduce the number of channel activities or split message delivery across multiple Orchestrated campaigns to stay within the 10 channel activities limit. The page states that exceeding this limit causes the save or publish operation to fail. Where: “Activities limitations”.

Onboarding:

  • Level: Intermediate
  • First minimal step: Include a version descriptor in every schema, including fact tables.
recommendation-more-help
journey-optimizer-help