文件Journey OptimizerJourney Optimizer 指南

使用案例：加快傳遞速度 use-case-ramp-up-your-deliveries

最後更新： 2026年9月4日
  • 適用對象：
  • Journey Orchestration

建立對象：

  • 中繼
  • 使用者
  • 開發人員

在此頁面上：​瞭解如何使用「最佳化」活動與設定檔上限，建立逐步加快電子郵件傳送的歷程，協助您熱身新的IP位址並建立您的寄件者信譽。

style
shade-box

如果您最近移至其他電子郵件服務提供者、IP位址或電子郵件網域或子網域，您必須建立您作為寄件者的信譽。 否則，您的傳遞可能會遭到封鎖或移至收件者信箱的垃圾郵件資料夾。 在傳遞能力最佳實務指南中瞭解如何利用IP暖身提高您的電子郵件信譽。

若要熱身IP，您可以逐步增加傳遞數量。 深入瞭解在Journey Optimizer中最佳化傳遞能力。

此使用案例的目的是建立歷程，以加快電子郵件傳遞速度。 若要設定此歷程，請遵循下列步驟：

  1. 建立歷程。 閱讀全文。

  2. 將​ 最佳化 ​活動新增至歷程。 閱讀全文。

  3. 在​ 條件 ​活動設定中，設定傳遞的收件者數目上限：

    1. 在​ 最佳化 ​活動設定中，選取​ 條件 ​方法，並將​ 型別 ​欄位設定為​設定檔上限。 閱讀全文。

    2. 將​ 限制 ​欄位設定為此傳遞的收件者數目上限。

    控制傳遞磁碟區的設定檔上限條件設定

    您可以逐漸提高此限制，最多可達您的訂閱者總數。

  4. 在​ 條件 ​活動之後，將​ 電子郵件 ​動作活動新增至名義路徑。

    斜向傳遞歷程中的電子郵件訊息設定

    當歷程執行時，會傳送訊息給輸入的設定檔，最多為您指定的設定檔數量上限。 當達到此限制時，輸入的設定檔會採用替代路徑。

  5. 使用您選擇的活動完成歷程。

IP啟動後，您就可以移除此條件。

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 use case describes how to build an Adobe Journey Optimizer journey that gradually ramps up email delivery volume using a Profile cap condition to protect sender reputation during IP warming.

Intents:

  • Build a journey to gradually increase email delivery volume for IP warming
  • Configure a Profile cap condition to limit the number of recipients per delivery run
  • Protect sender reputation when switching to a new email service provider, IP address, or domain
  • Remove the volume cap condition once the IP is fully warmed up

Glossary:

  • IP warming: The process of gradually increasing email send volume from a new IP address or domain to build sender reputation with mailbox providers (product-specific)
  • Profile cap: A condition type in the Optimize activity that limits the maximum number of profiles that receive a message in a given journey run (product-specific)
  • Optimize activity: A journey canvas activity used to apply conditions, targeting rules, or experimentation to control how profiles flow through a journey (product-specific)

Guardrails:

  • A Profile cap condition must be set in the Optimize activity’s Conditions method to control delivery volume.
  • Profiles that exceed the cap take the alternate path defined in the journey.
  • The profile cap limit should be increased gradually over time up to the total number of subscribers.

Terminology:

  • Canonical name: Ramp-up deliveries — Acronym: none — variants: IP warming, IP warmup, delivery ramp-up
  • Synonyms: “IP warming” = “IP warmup” = “sender reputation building”
  • Do not confuse: “Profile cap” ≠ “audience size limit” (Profile cap is a per-run delivery limit; audience size is the total number of qualified profiles)

FAQ:

  • Q: Why do I need to ramp up deliveries when switching to a new IP or domain? — A new IP or domain has no sending history, so mailbox providers may block or spam-folder messages until a positive reputation is established through gradual, increasing volume.
  • Q: How does the Profile cap condition control delivery volume? — It sets a maximum number of profiles that can receive the message in a single journey run; profiles beyond that limit take an alternate path instead.
  • Q: When can I remove the Profile cap condition? — Once the IP is fully warmed up and your sender reputation is established, you can remove the condition from the journey.
  • Q: Can I increase the cap gradually over time? — Yes; you can update the Limit field in the Profile cap condition to progressively increase the number of recipients per run up to your full subscriber count.
recommendation-more-help
journey-optimizer-help