配置API触发的活动操作 api-action

应用上限规则（电子邮件、推送、移动设备）

在​ 业务规则 ​下拉列表中，选择一个规则集以将上限规则应用于营销活动。 利用渠道规则集，可设置按通信类型划分的频率封顶，以防止消息类似的客户超载。 了解如何使用规则集

覆盖电子邮件渠道配置 （电子邮件）

当API触发的营销活动需要与所选渠道配置不同的电子邮件值时，使用此选项，而不创建其他配置。 您可以仅覆盖该操作所需的字段，而配置的其他部分保持不变。 了解如何覆盖电子邮件渠道配置

对于API触发的营销活动，由于在运行时从API有效负载生成上下文，因此在定义电子邮件操作时，上下文属性在个性化编辑器中不可用，因此必须手动输入。 了解有关上下文数据语法的更多信息

note important
IMPORTANT
表达式路径必须与API有效负荷结构完全匹配，因为Journey Optimizer未执行任何检查。 例如，如果有效负载包含context.RM.name和context.RM.emailPrefix，请在表达式中使用相同的点表示法。

跟踪参与情况（电子邮件、移动设备）。

使用​ 操作跟踪 ​部分跟踪收件人对电子邮件或移动投放的反应。 执行营销活动后，即可从营销活动报告获取跟踪结果。 了解关于营销活动报告的更多信息

启用快速传递模式 （推送）。

快速投放模式是一个 Journey Optimizer 附加组件，允许通过营销活动以非常快的速度发送大量推送消息。 如果消息投放延迟对业务有重大影响，并且您想要在手机上发送紧急推送警报（例如，向已安装新闻频道应用程序的用户发送突发新闻），可使用快速投放。 了解如何在此页面🔗上为推送通知启用快速传递模式。

有关使用快速投放模式时的性能的详细信息，请参阅 Adobe Journey Optimizer 产品说明。

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 choose the channel and the channel configuration of an API triggered campaign in the Actions tab, and how to set optimization, multilingual, capping, tracking, and Rapid delivery mode options.

Intents:

• Add an action to an API triggered campaign and choose its communication channel
• Select a channel configuration for the message
• Use the Message Optimization section for content experiments, targeting rules, or both
• Add multilingual content with the Languages section
• Apply capping rules, track engagement, or enable Rapid delivery mode, depending on the channel

Glossary:

• Channel configuration: Defined by a System Administrator; contains the technical parameters for sending the message, such as header parameters, subdomain, mobile apps (product-specific)
• Business rules: Drop-down list in which you select a rule set to apply capping rules to the campaign
• Capping rules: Frequency capping by communication type, applied through a rule set, to prevent overloading customers with similar messages
• Action tracking: Section used to track how recipients react to email or mobile deliveries; results are accessible from the campaign report once the campaign has been executed
• Rapid delivery mode: A Journey Optimizer add-on that allows very fast push message sending in large volumes through campaigns (product-specific)

Guardrails:

• Available channels vary based on your licensing model and add-ons.

Prerequisites and permissions:

• A channel configuration, defined by a System Administrator

Applicability:

• Capping rules (Business rules): Email, Push, Mobile
• Track engagement (Action tracking): Email, Mobile
• Rapid delivery mode: Push
• High Throughput API triggered campaigns: email channel only

Terminology:

• Canonical name: API triggered campaign action
• Do not confuse: “channel” (the communication channel selected with Add action) ≠ “channel configuration” (the technical parameters defined by a System Administrator)

FAQ:

• Q: How do I choose the channel of an API triggered campaign? — In the Actions tab, click Add action and select the communication channel.
• Q: Which channels can I use? — Available channels vary based on your licensing model and add-ons. High Throughput API triggered campaigns currently support the email channel only.
• Q: Who defines the channel configuration? — A System Administrator defines it.
• Q: Which channels support capping rules and engagement tracking? — Capping rules apply to Email, Push, and Mobile. Tracking applies to Email and Mobile.
• Q: Which channel supports Rapid delivery mode? — Push.

Examples:

• Rapid delivery mode is used when delay in message delivery is business-critical, for example an urgent push alert such as breaking news sent to users who have installed a news channel app.

Related pages:

• Supported channels: Channels in journeys & campaigns (channels/gs-channels.md)
• Setting up channel configurations: Learn how to set up channel configurations (configuration/channel-surfaces.md)
• Content experiments and targeting rules: Optimization in campaigns (content-management/gs-message-optimization.md)
• Multilingual content: Get started with multilingual content (content-management/multilingual-gs.md)
• Rule sets for capping: Learn how to work with rule sets (conflict-prioritization/rule-sets.md)
• Campaign reports: Learn more about campaign reports (reports/campaign-global-report-cja.md)
• Enabling Rapid delivery mode for push notifications: on this page (push/create-push.md#rapid-delivery)
• Next step, designing the content: Learn more (campaigns/api-triggered-campaign-content.md)

Personas:

• developer: Can add an action to an API triggered campaign and select its communication channel in the Actions tab. Can select a channel configuration that contains technical parameters such as header parameters, subdomain, and mobile apps. The page states that High Throughput API triggered campaigns currently support the email channel only. Where: “Configure the API triggered campaign action”.

Onboarding:

• Level: Experienced
• First minimal step: Navigate to the Actions tab, select Add action, and select the communication channel.
• Success check: Tracking results are accessible from the campaign report once the campaign has been executed.
• Previous: A channel configuration must be defined before you can select it for the action: Set up channel configurations (configuration/channel-surfaces.md)
• Next: Once your campaign configuration and content are ready, design its content: Edit the API triggered campaign content (campaigns/api-triggered-campaign-content.md)