On this page: Activate High throughput mode for API-triggered campaigns so you can send very large-scale, real-time transactional messages (email and push) at up to 5000 transactions per second without relying on profiles.
High throughput mode is designed for organizations that need very large-scale, real-time transactional messaging (up to 5000 transactions per second). Unlike regular API-triggered campaigns, High throughput campaigns operate independently of Adobe Profiles and require a different configuration model.
This page explains how High throughput campaigns differ from standard API-triggered campaigns, setup requirements, and when to choose each mode.
Guardrails & limitations guardrails
-
Access - Available across all regions except Switzerland for organizations licensed with the High throughput transactional messaging add-on.
-
Channels: Email and push notifications.
-
Personalization in High throughput campaigns:
- All personalization must be included in the API payload as contextual data. Learn how to personalize content using contextual data
- Profile-based personalization is not supported. If profile variables are used, validation errors will occur.
-
Personalization in High throughput channel configurations - High throughput channel configurations do not support contextual or profile-based personalization.
-
Matching resources - High throughput campaigns, channel configurations, and IP pools can only be used with each other. Standard and High throughput resources cannot be mixed.
-
API endpoint - High throughput campaigns use a different endpoint than standard API-triggered campaigns. For details, see Execute an API triggered campaign.
-
Campaign exclusivity - High throughput campaigns do not use Adobe Profiles. Messages are delivered whether or not a profile exists.
Moreover, a campaign cannot be used for both profile-enabled and non-profile use cases. If you need both, create two separate campaigns, and ensure the calling system decides which one to trigger based on the context.
-
Datasets for feedback and tracking - Feedback and tracking data for High throughput campaigns are stored in dedicated datasets that are not enabled for profiles. As a result, these events are not stitched to profiles, even if a matching profile exists.
The datasets used are:
- AJO Message Feedback Event Dataset - Non Profile — used for both email and push feedback.
- AJO Email Tracking Experience Event Dataset - Non Profile — used for email tracking only. A dedicated non-profile tracking dataset for push is not yet available.
-
Throughput allocation - The throughput provisioned under the High throughput add-on is exclusively reserved for High throughput campaigns. There is no sharing of throughput between standard and High throughput API-triggered campaigns.
-
Unsupported features:
-
Message Export and dynamic subdomains are not supported for High throughput.
-
Personalized PDF attachments - Not supported when High throughput traffic is routed through the secondary region. Learn more about personalized PDF attachments
-
-
Push notifications:
- Web push — High throughput web push campaigns run on shared infrastructure and do not benefit from the dedicated capacity reserved for High throughput mobile push.
- Payload size — The maximum payload size is 5 KB.
- Denylist behavior — When a message hits a denylist, delivery feedback is retained but no profile-update feedback is produced. This means denylist responses do not trigger profile updates or token invalidation in Adobe Experience Platform.
Choosing between standard vs. High throughput campaigns
Use this table to decide which API-triggered campaign type fits your use case:
In other words:
-
Choose Standard API-triggered campaigns if:
- You don’t have High throughput contracted.
- Your throughput needs are <500 TPS.
- You require personalization based on Adobe Profiles.
- You want campaign data stitched to profiles for future targeting.
- You want to use another channel than Email or Push.
-
Choose High throughput campaigns if:
- You need throughput >500 TPS.
- You don’t require profile stitching.
- You can pass all personalization in the API payload.
- You want to use the Email or Push channel.
Configure High throughput API-triggered campaigns configure-high-throughput
Once the prerequisite is met, you can set up High throughput yourself in the product UI for both channels:
- Email: create a dedicated High throughput IP pool, then a High throughput email channel configuration that uses it. Learn more
- Push: create a High throughput push channel configuration. Learn more
Prerequisite prerequisite
After purchasing the High throughput transactional messaging add-on, contact Adobe Customer Care or your Adobe representative so that the required backend activation can be completed.
Set up High throughput API-triggered email campaigns setup-guidelines
To configure High throughput email campaigns, follow the steps below.
Create a dedicated IP pool create-ip-pool
High throughput requires a dedicated IP pool because it is built to maintain high availability and performance across two regions.
When you purchase the High throughput add-on, sending IPs are provisioned in a secondary region, in addition to the IPs allocated to you in your primary region.
- Failover - If the primary region becomes unavailable, all High throughput traffic automatically switches to the secondary region, so your transactional messages keep being delivered.
- IP warm-up - To make sure the secondary region IPs are ready when needed, part of your High throughput traffic is routed through the secondary region on an ongoing basis. This keeps these IPs warm. Sending from IPs with no sending history could cause internet service providers (ISPs) to reject your emails.
Create the IP pool as follows.
-
Create an IP pool. Learn how
-
Select the Enable high-throughput option.
-
Select one or more secondary region IPs for the dedicated IP pool. This ensures high availability for your High throughput traffic.
The dedicated IP pool is now ready for use with High throughput channel configurations.
Create a High throughput email channel configuration configuration-guidelines
-
Create an email channel configuration. Learn how
-
Select the Transactional email type in the Email settings.
-
Enable the Create as a High throughput configuration toggle.
-
In the IP pool details section, select the High throughput IP pool you created. Only High throughput IP pools are listed.
-
Submit the channel configuration.
Your High throughput email channel configuration is now ready for use in a High throughput API-triggered campaign.
Set up High throughput push campaigns setup-push
As with email, you can set up High throughput for push yourself, directly in the interface. To do so, follow the steps below.
-
Create a push channel configuration. Learn how
-
Enable the Create as a High throughput configuration toggle.
-
Select the platform(s) and corresponding App id(s) for your push configuration.
note NOTE When the High throughput toggle is enabled, push App id personalization is not available. -
Submit the channel configuration.
Your High throughput push channel configuration is now ready for use in a High throughput API-triggered campaign.
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 High throughput mode for API triggered campaigns differs from standard API triggered campaigns, its guardrails and setup requirements, and when to choose each mode for very large-scale, real-time transactional messages (email and push) without relying on profiles.
Intents:
- Decide between a standard API triggered campaign and a High throughput campaign
- Know the guardrails and limitations of High throughput campaigns
- Set up High throughput campaigns: a dedicated IP pool and a channel configuration for email, a channel configuration for push
- Know how to personalize a High throughput campaign (contextual data only)
- Know which datasets store feedback and tracking data for High throughput campaigns
Glossary:
- High throughput mode (also written High Throughput): A mode of API triggered campaigns designed for very large-scale, real-time transactional messaging, which operates independently of Adobe Profiles (product-specific)
- Standard API triggered campaign: An API triggered campaign that is not in High throughput mode
- High Throughput transactional messaging add-on: The add-on that organizations must be licensed with to use High throughput campaigns (product-specific)
- Contextual data: Personalization data passed in the API payload
- AJO Message Feedback Event Dataset - Non Profile: Dataset used for both email and push feedback of High throughput campaigns
- AJO Email Tracking Experience Event Dataset - Non Profile: Dataset used for email tracking only of High throughput campaigns
Guardrails:
- Throughput: High throughput campaigns support up to 5000 transactions per second; standard API triggered campaigns support up to 500 transactions per second.
- Channels: Email and push notifications for High throughput campaigns.
- Personalization: all personalization must be included in the API payload as contextual data. Profile-based personalization is not supported, and validation errors occur if profile variables are used.
- Channel configurations that use profile-based personalization cannot be used with High throughput campaigns. Only channel configurations without profile personalization can be used.
- High throughput campaigns use a different API endpoint than standard API triggered campaigns.
- High throughput campaigns do not use Adobe Profiles. Messages are delivered whether or not a profile exists.
- A campaign cannot be used for both profile-enabled and non-profile use cases. If you need both, create two separate campaigns, and make the calling system decide which one to trigger based on the context.
- Feedback and tracking data for High throughput campaigns are stored in dedicated datasets that are not enabled for profiles, so these events are not stitched to profiles, even if a matching profile exists. A dedicated non-profile tracking dataset for push is not yet available.
- The throughput provisioned under the High Throughput add-on is exclusively reserved for High throughput campaigns. There is no sharing of throughput between standard and High throughput API triggered campaigns.
- Personalized PDF attachments are not supported when a High throughput campaign fails over to another region.
- Web push: High Throughput web push campaigns run on shared infrastructure and do not benefit from the dedicated capacity reserved for High Throughput mobile push.
- Push payload size: the maximum payload size is 5 KB (hard limit).
- Denylist behavior for push: when a message hits a denylist, delivery feedback is retained but no profile-update feedback is produced, so denylist responses do not trigger profile updates or token invalidation in Adobe Experience Platform.
- High throughput channel configurations (and, for email, IP pools) can only be used with High throughput API triggered campaigns, and not with standard transactional messaging using API triggered campaigns or journeys.
- The type of a channel configuration or IP pool cannot be changed after creation: a standard resource cannot be converted to High throughput, and vice versa.
- Push App id personalization is not available in High throughput push channel configurations.
- When creating a High throughput API triggered campaign, only High throughput channel configurations are available for selection.
Prerequisites and permissions:
- The organization must be licensed with the High Throughput transactional messaging add-on.
- A one-time backend activation after purchasing the add-on, requested through Adobe Customer Care or your Adobe representative (not needed for each channel configuration).
- Email: a new dedicated High throughput IP pool, and a new email channel configuration with the Create as a High throughput configuration toggle enabled that uses this IP pool.
- Push: a new push channel configuration with the Create as a High throughput configuration toggle enabled, with the platform(s) and App id(s) selected. No IP pool is needed.
Applicability:
- Access: available across all regions except Switzerland.
- Applies to API triggered campaigns, in High throughput mode.
Terminology:
- Canonical name: High throughput mode — variants: High Throughput mode, High throughput campaigns
- Acronym: TPS — transactions per second (used on the page body)
- Do not confuse: “Standard API triggered campaign” (included in the base offering, standard entitlement and message packs, standard infrastructure, uptime 99,9%) ≠ “High throughput campaign” (requires the High Throughput transactional messaging add-on, separate tiered message volumes, enhanced infrastructure, uptime 99,99%); both have a health check API
FAQ:
- Q: When should I choose a standard API triggered campaign? — When you do not have High Throughput contracted, your throughput needs are under 500 TPS, you require personalization based on Adobe Profiles, you want campaign data stitched to profiles for future targeting, or you want to use another channel than Email or Push.
- Q: When should I choose a High throughput campaign? — When you need throughput over 500 TPS, you do not require profile stitching, you can pass all personalization in the API payload, and you want to use the Email or Push channel.
- Q: Can a High throughput campaign use profile attributes for personalization? — No. Profile-based personalization is not supported, and validation errors occur if profile variables are used. Pass all personalization as contextual data in the API payload.
- Q: Can one campaign serve both profile-enabled and non-profile use cases? — No. Create two separate campaigns, and make the calling system decide which one to trigger.
- Q: Is throughput shared between standard and High throughput campaigns? — No. The throughput provisioned under the High Throughput add-on is exclusively reserved for High throughput campaigns.
- Q: How do I set up High throughput campaigns? — Both email and push can be self-configured in the UI. For email, create a dedicated High throughput IP pool, then create a channel configuration with the Create as a High throughput configuration toggle enabled and select that IP pool. For push, create a push channel configuration with the toggle enabled and select the platform(s) and App id(s); no IP pool is needed. App id personalization is not available for High throughput push.
Related pages:
- Personalizing content with contextual data: Learn how to personalize content using contextual data (campaigns/api-triggered-campaign-content.md#contextual)
- Endpoint used by High throughput campaigns: Execute an API triggered campaign (campaigns/trigger-campaigns.md#trigger)
- Channel configurations with profile-based personalization: profile-based personalization (email/surface-personalization.md)
- Personalized PDF attachments: Learn more about personalized PDF attachments (email/pdf-attachments.md#personalized-attachments)
- Create IP pools: Learn how to create IP pools (configuration/ip-pools.md)
- Set up channel configurations: Learn how to set up channel configurations (configuration/channel-surfaces.md)
- Set up push channel configurations: Learn how to create a push channel configuration (push/push-configuration.md#message-preset)
- Push App id personalization: Learn about push App id personalization (push/push-configuration.md#app-id-personalization)
Personas:
- developer: Can pass all personalization for High throughput campaigns as contextual data in the API payload. Can call a different API endpoint than the one used for standard API triggered campaigns. Can use the AJO Message Feedback Event Dataset - Non Profile and the AJO Email Tracking Experience Event Dataset - Non Profile for feedback and tracking. The page states that profile variables cause validation errors, and push payload size is limited to 5 KB. Where: “Guardrails & limitations”.
Onboarding:
- Level: Experienced
- First minimal step: Create a new IP pool.
- Success check: The page states a Health check API is available for the High Throughput Campaign.
- Next: Learn how to personalize content using contextual data: Edit the API triggered campaign content (campaigns/api-triggered-campaign-content.md); Learn how to set up channel configurations: Set up channel configurations (configuration/channel-surfaces.md)