发送时间优化 send-time-optimization

贵组织应至少在30天内使用Journey Optimizer中的“电子邮件”操作，然后再使用电子邮件中的“发送时间优化”来收集一些电子邮件发送、打开和单击事件。

贵组织应至少在30天内使用Journey Optimizer中的“推送”操作，然后再使用“推送”中的“发送时间优化”以允许收集某些推送发送和打开事件。

如果您的组织已使用电子邮件和/或推送操作类型至少30天，则在Adobe启用发送时间优化后，您的组织无需等待更长时间即可使用发送时间优化。 随着您的组织收集长达16周的数据，结果将继续改进。

对于由组织优化的所有消息，发送时间优化可能会将电子邮件点击率和推送打开率提高约2%到10%。

例如，如果发送电子邮件但未优化发送时间的组织的平均点击率为5.0%，则优化发送时间的同一组电子邮件平均可能会产生高达5.5%的点击率(5.0% * (1+10%) = 5.5%)。

由于样本量小，发送时间优化带来的益处可能不会在单个消息发送上观察到。

在以下情况下，组织更有可能从使用发送时间优化中获得更大的好处：

• 现有历程使用的发送时间是固定的，并且未得到良好优化
• 客户行为的可变性（点击量和打开量）对应于客户位置和客户偏好
• 组织对大部分电子邮件和推送消息使用发送时间优化
• 组织选择建议的6-12小时范围内的最长等待时间

出现这种情况可能有多种原因：

• 您的消息被选为“探索”消息发送时间，而不是“优化”消息发送时间。
• 相似用户的行为会影响模型来建议其他发送时间。

在以下情况下，发送时间优化可以在夜间以本地时区向用户发送推送消息：

• 当用户表现出表明他们可能与夜间发送的消息进行交互时
• 当模型选择“勘探”发送时间时

要避免在夜间时段向客户发送推送消息，请安排在早上或下午早些时候发送批量推送消息，并缩短发送时间优化持续时间。 （例如，上午9点发送时间，最长等待时间为8小时。）

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 configure and use Send-Time Optimization in Adobe Journey Optimizer, an AI-powered feature that predicts the best time to send email or push messages to each individual to maximize engagement.

Intents:

• Enable Send-Time Optimization on an email or push action in a journey
• Choose whether to optimize for opens or click-throughs on email messages
• Set the maximum wait window (Send within next) for delayed delivery
• Understand how the AI model predicts optimal send times using behavioral data
• Determine whether Send-Time Optimization is appropriate for a given message type
• Use Send-Time Optimization within a Wait activity to delay before any downstream activity, decoupled from the message send

Glossary:

• Send-Time Optimization (STO): An AI-powered feature that delays message delivery to each profile until the predicted optimal engagement hour within a configured time window (product-specific)
• Journey AI: Adobe’s AI services powering Send-Time Optimization within Journey Optimizer (product-specific)
• Exploration send time: A randomly selected send time (used for 5% of sends) to test different times and improve model accuracy (product-specific)
• Optimized send time: A model-predicted send time selected to maximize click or open rates (used for 95% of sends) (product-specific)
• Send within next: The maximum number of hours (2–100) the system will wait before sending the message to a given profile (product-specific)

Guardrails:

• Send-Time Optimization must be enabled by Adobe for the organization; contact Adobe Customer Care or your Adobe representative to activate it.
• Send-Time Optimization applies to Email and Push notification channels within Journeys, and to the Wait activity; it is not available for Campaigns or custom actions.
• Send-Time Optimization has no visibility into quiet hours rules; a Send-Time Optimization Wait activity can select a time inside a quiet-hours window for a downstream channel action, which may then queue or discard the message depending on the quiet hours rule configuration.
• The organization must have used Email or Push actions in Journey Optimizer for at least 30 days before Send-Time Optimization produces meaningful results.
• Do not use Send-Time Optimization for urgent or time-sensitive operational messages (e.g., order confirmations, password resets, flight gate changes).
• Maximum wait time range is 2–100 hours; recommended range is 6–24 hours for best results.
• Model scores are stored in profile attributes at _experience.intelligentServices.journeyAI.sendTimeOptimization and are not human-readable.
• Models are trained weekly initially, then retrained and rescored monthly after 16 weeks.

Terminology:

• Canonical name: Send-Time Optimization — Acronym: STO — variants: best send time, send time AI, intelligent send time
• Synonyms: “Send-Time Optimization” = “optimal send time” = “AI send time”
• Do not confuse: “Exploration send time” ≠ “Optimized send time” (exploration is random for model testing; optimized is model-predicted for engagement)

FAQ:

• Q: Which channels support Send-Time Optimization? — Email and Push notification channels within Journeys, and the Wait activity; Campaigns and custom actions are not supported.
• Q: Does Send-Time Optimization know about quiet hours? — No. Quiet hours are only evaluated when a profile reaches a message action, so a Send-Time Optimization Wait activity can pick a time inside a quiet-hours window. Depending on the quiet hours rule, the message is then queued until quiet hours end, or discarded and the profile exits the journey. Learn more.
• Q: Should I optimize for opens or clicks on email? — Optimize for Clicks for most emails. Choose Opens when the message is informational and not intended to drive a specific action.
• Q: How long does the organization need to wait before enabling STO? — At least 30 days of Email or Push usage in Journey Optimizer is needed to collect sufficient behavioral data. Results continue to improve for up to 16 weeks.
• Q: Can STO send push notifications at night? — Yes, if a user’s behavior suggests night-time engagement or if an exploration send time is selected. To avoid this, use a morning send time with a short maximum wait window.
• Q: What is the expected benefit of Send-Time Optimization? — Approximately 2–10% improvement in email click rate or push open rate across all optimized messages, though benefits may not be observable on individual small-volume sends.