排程API觸發的行銷活動 api-schedule

在此頁面上:​在[排程]索引標籤中設定開始和結束日期以及速率控制,讓您的API觸發的行銷活動在正確的時間傳送,而不會造成下游系統負擔。

使用​ 排程 ​索引標籤來定義行銷活動排程。

設定開始和結束日期

根據預設,API觸發的行銷活動會在觸發後開始,並在訊息傳送後立即結束。 如果您不想在行銷活動觸發後立即執行,可以使用​ 行銷活動開始 ​選項指定傳送訊息的日期和時間。

行銷活動end​選項可讓您指定行銷活動何時應停止執行。 在指定日期以外,將不會執行行銷活動。

NOTE
在 Adobe Journey Optimizer 中排程行銷活動時,請確定您的開始日期/時間與所要的首次傳遞一致。

設定速率控制

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 API triggered campaign with start and end dates in the Schedule tab, and how to set rate control with the Throttle delivery option.

Intents:

  • Understand when an API triggered campaign starts and ends by default
  • Set a start date and time with Campaign start
  • Set an end date and time with Campaign end
  • Set a delivery rate per second with Throttle delivery
  • Understand which profiles are excluded when the delivery rate is too low

Glossary:

  • Campaign start: Option to specify a date and time at which the message is sent
  • Campaign end: Option to specify when a campaign stops being executed
  • Rate control: Feature that limits the delivery rate of outbound actions, to prevent overload on downstream systems such as landing pages or customer care platforms
  • Throttle delivery: Option in the Delivery settings section that enables rate control
  • Delivery rate: The number of messages per second specified when Throttle delivery is enabled

Guardrails:

  • By default, API triggered campaigns start once they are triggered, and end as soon as the message has been sent once.
  • Outside of the specified dates, the campaign is not executed.
  • Minimum delivery rate supported: 1 per second (hard limit).
  • Maximum delivery rate supported: 2000 per second when the Throttle delivery option is enabled (hard limit).
  • 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 these excluded profiles is visible in the campaign report.

Applicability:

  • Rate control: outbound actions (Email, Mobile messages, Push notifications)

Terminology:

  • Canonical name: API triggered campaign schedule
  • Do not confuse: Campaign start (when the message is sent) ≠ Campaign end (when the campaign stops being executed)

FAQ:

  • Q: When does an API triggered campaign start by default? — Once it is triggered. It ends as soon as the message has been sent once.
  • Q: How do I send the message at a specific time? — Use the Campaign start option to specify a date and time.
  • Q: How do I limit the delivery rate? — Enable Throttle delivery in the Delivery settings section and specify the Delivery rate per second.
  • Q: What is the supported range for the delivery rate? — From 1 per second to 2000 per second.
  • Q: What happens to profiles that cannot be reached in 12 hours? — They are excluded from the campaign, and their count appears in the campaign report.

Examples:

  • A rate limit of 165 messages per second ensures steady delivery without overwhelming downstream systems.

Related pages:

  • Next step, review and activation: Learn more (campaigns/review-activate-api-triggered-campaign.md)

Personas:

  • developer: Can enable Throttle delivery in Delivery settings and set a Delivery rate per second for Email, Mobile messages, and Push notifications. Can apply rate control to prevent overload on downstream systems such as landing pages or customer care platforms. The page states that the delivery rate supports 1 to 2000 messages per second, with a 12 hour maximum execution timeframe for the campaign audience. Where: “Set rate control”.

Onboarding:

  • Level: Experienced
  • First minimal step: Enable the Throttle delivery option in the Delivery settings section and specify the desired Delivery rate per second.
  • Success check: You can see the count of these excluded profiles in the campaign report.
  • Next: When your campaign configuration and content are ready: Review & activate the API triggered campaign (campaigns/review-activate-api-triggered-campaign.md)
recommendation-more-help
journey-optimizer-help