文档Journey OptimizerJourney Optimizer 指南

计划行动营销活动 action-campaign-schedule

最近更新： 2026年10月25日

创建对象：

  • 初学者
  • 用户

在此页面上：​通过设置开始和结束日期、收件人时区投放、执行频率和速率控制来计划您的操作营销活动，以便您的消息在正确的时间到达正确的受众，而不会淹没下游系统。

style
shade-box

使用​ 计划 ​选项卡定义营销活动计划。

NOTE
当营销活动定位批量受众时，营销活动计划和受众评估是分开的时钟。 营销活动使用执行开始时可用的最新完成受众快照；更改营销活动开始时间不会重新计算受众。 请在分段完成后大约两小时让受众准备就绪，以便使用，但请将此视为变量计划估计，而不是保证。 实际时间取决于沙盒、受众大小、摄取量、导出处理和系统负载。 如果受众仍在评估或导出，则营销活动可以使用之前完成的快照。 批量受众评估后触发​ 控制 ​适用于支持的定期读取受众历程，而不适用于操作营销活动；在预期分段和导出完成之后计划营销活动执行并验证实际沙盒计时。

设置营销活动开始日期

默认情况下，手动激活营销活动后，营销活动便会开始，而发送一次消息后，营销活动便会结束。 如果不想在营销活动激活后立即执行营销活动，则可以在​ 营销活动开始 ​部分中指定发送消息的日期和时间。

在 Adobe Journey Optimizer 中计划营销活动时，请确保开始日期/时间与所需的首次投放时间一致。 对于定期营销活动，如果计划的首次时间已过，则营销活动将根据定期规则滚动到下一个可用时间段。

按收件人的本地时间发送 profile-timezone

在计划特定日期和时间的营销活动时，您可以选择根据每个收件人的用户档案时区发送消息。 这可确保所有收件人无论其地理位置如何，都能在同一本地时间收到消息。

例如，如果您计划使用用户档案时区在早上9点发送活动，则纽约州(ET)的收件人将在东部时间早上9点收到该信息，而洛杉矶州(PT)的收件人将在太平洋时间早上9点收到该信息。

AVAILABILITY
使用配置文件时区进行计划仅适用于以下出站渠道：电子邮件、推送、移动消息、WhatsApp和LINE。

要启用用户档案时区计划，请执行以下操作：

  1. 在​ 营销活动开始 ​部分，指定发送消息的日期和时间。

  2. 启用​ 使用配置文件时区 ​选项。

工作方式：

系统使用每个收件人Adobe Experience Platform配置文件中的profile.timeZone字段来确定其本地时区。 如果用户档案没有时区值，则系统将使用创建营销活动时所在的时区作为回退。

在所有时区之间投放消息时，营销活动仍处于​ 实时 ​状态。 处理完所有时区后，营销活动状态将更改为​已完成。

支持的时区标识符：

profile.timeZone格式可以是IANA命名或定义为UTC偏移。 IANA命名是首选格式，因为它会自动针对夏令时规则进行调整。

对于IANA命名，标识符区分大小写，并且必须与官方的IANA命名匹配。 由于夏令时规则和历史更新，偏移可能会随着时间的推移而发生变化。 有关标识符的官方列表，请参阅IANA时区数据库{_blank}。

设置执行频率

对于​电子邮件、移动设备消息​和​ 推送通知 ​操作，您可以定义发送营销活动消息的频率。 为此，请在营销活动创建屏幕中使用​ 操作触发器 ​选项来指定是否应每天、每周或每月执行营销活动。

NOTE
对于​ 电子邮件 ​操作，您可以创建特定的IP预热计划激活活动。 营销活动计划将由与之关联的IP预热计划驱动，这意味着不再在营销活动本身中定义计划。 了解如何创建IP预热营销活动。

设置结束日期

营销活动结束​部分允许您指定何时应停止执行营销活动。 在指定的日期之外，将不会执行营销活动。

设置速率控制

Journey Optimizer允许您为出站操作（电子邮件、移动消息、推送通知）启用速率控制。

此功能对于防止下游系统（如登陆页面或客户服务平台）过载尤为实用。 例如，您可以将速率限制设置为每秒165条消息，以确保平稳投放而不会淹没下游系统。

要设置速率控制，请在​ 投放设置 ​部分中启用​ 节流投放 ​选项，并指定所需的​每秒投放速率。

  • 支持的最低投放率：每秒1个。
  • 支持的最大投放率：启用“限制投放”选项时，每秒投放2000次。

IMPORTANT
设置投放率时，活动受众可以执行的最长时间范围为12小时。 如果投放率设置为不允许在12小时时间范围内发送消息的所有受众的值，则剩余的用户档案将从营销活动中排除。 您可以在营销活动报告中查看这些排除的用户档案的计数。

按波次发送

要在一段时间内批量投放营销活动消息，而不是一次投放所有营销活动消息，您可以使用波动发送。 这有助于平衡负载、支持可投放性，并避免压倒性的下游系统（例如，呼叫中心或登陆页面）。 您可以定义波次数、波次大小（按百分比或绝对数）以及每个波次的计划。

了解如何使用批次发送。

后续步骤 next

活动计划就绪后，您可以查看和激活该活动。 了解详情

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 schedule an Action campaign in the Schedule tab: start and end dates, recipient local time delivery, execution frequency, rate control, and wave sending.

Intents:

  • Set a start date and time with Campaign start
  • Send messages at each recipient’s local time with Use profile timezone
  • Set a daily, weekly, or monthly execution frequency
  • Set an end date with Campaign end
  • Set rate control with Throttle delivery
  • Deliver the message in batches over time using waves

Glossary:

  • Profile timezone: The profile.timeZone field of each recipient’s Adobe Experience Platform profile, used to determine their local timezone. (product-specific)
  • Rate control: Limits the delivery rate for outbound actions to prevent overload on downstream systems. (product-specific)
  • Delivery rate: The rate per second set when Throttle delivery is enabled in Delivery settings. (product-specific)
  • Waves: Batches in which the campaign message is delivered over time; you define the number of waves, their size (by percentage or absolute number), and the schedule for each wave. (product-specific)
  • IP warmup plan activation campaign: A campaign for email actions whose schedule is driven by the IP warmup plan it is associated with. (product-specific)

Guardrails:

  • By default, Action campaigns start once they are activated manually, and end as soon as the message has been sent once.
  • Outside of the dates specified in Campaign start and Campaign end, the campaign is not executed.
  • For recurring campaigns, if the initial scheduled time has already passed, the campaigns roll over to the next available time slot according to their recurrence rules.
  • Use profile timezone is available for these outbound channels only: Email, Push, Mobile message, WhatsApp, and LINE.
  • If a profile does not have a timezone value, the timezone in which the campaign was created is used as the fallback.
  • Time zone identifiers: profile.timeZone can be IANA naming or UTC offsets. IANA naming is the preferred format, as it automatically adjusts for daylight-saving rules. IANA identifiers are case-sensitive and must match the official IANA naming.
  • Execution frequency (daily, weekly, or monthly) is available for Email, Mobile message, and Push notification actions.
  • Delivery rate: minimum 1 per second (hard limit); maximum 2000 per second (hard limit) when the Throttle delivery option is enabled. Rate control is available for outbound actions (Email, Mobile messages, Push notifications).
  • When a delivery rate is set, the maximum timeframe for which the campaign audience can execute is 12 hours (hard limit). If the delivery rate does not allow all the audience to be sent the message in the 12 hour timeframe, the remaining profiles are excluded from the campaign. The count of excluded profiles is visible in the campaign report.

Terminology:

  • Canonical name: Action campaign schedule — variants: campaign schedule
  • Synonyms: “Send at recipient’s local time” = “Use profile timezone” (section title and option name)
  • Do not confuse: “Live” (status while messages are being delivered across all timezones) ≠ “Completed” (status once all timezones have been processed)

FAQ:

  • Q: When does an Action campaign start and end by default? — It starts once it is activated manually, and ends as soon as the message has been sent once.
  • Q: How do I send at the same local time for every recipient? — Specify the date and time in Campaign start, then enable Use profile timezone. This is available for Email, Push, Mobile message, WhatsApp, and LINE only.
  • Q: What happens if a profile has no timezone value? — The timezone in which the campaign was created is used as the fallback.
  • Q: What are the campaign statuses during profile timezone delivery? — The campaign remains in Live status while messages are being delivered across all timezones; when all timezones have been processed, the status changes to Completed.
  • Q: Which delivery rates can I set? — From 1 to 2000 per second when Throttle delivery is enabled.
  • Q: Why were some profiles excluded from my campaign? — When a delivery rate is set, the maximum timeframe is 12 hours; the remaining profiles are excluded from the campaign if the rate does not allow sending to the whole audience in that timeframe. Their count is in the campaign report.

Examples:

  • Profile timezone: a campaign scheduled to send at 9 AM using profile timezone reaches recipients in New York (ET) at 9 AM ET and recipients in Los Angeles (PT) at 9 AM PT.
  • Rate control: set a rate limit of 165 messages per second to ensure steady delivery without overwhelming downstream systems.

Related pages:

  • IP warmup campaigns: Learn how to create IP warmup campaigns (configuration/ip-warmup-campaign.md)
  • IANA identifiers: IANA Time Zone Database (external, https://www.iana.org/time-zones)
  • Waves: Learn how to send using waves (delivery/send-using-waves.md)
  • Next step, activation: Review and activate an Action campaign (campaigns/review-activate-campaign.md)
recommendation-more-help
journey-optimizer-help