在此页面上：了解如何通过依赖Adobe Campaign Standard事务性消息传递模板，在历程中使用内置的Campaign Standard电子邮件、推送和短信操作活动。
如果您有Adobe Campaign Standard，则以下内置操作活动可用： 电子邮件、推送和短信。
对于每个渠道，您选择一个Adobe Campaign标准事务型消息传递模板。 对于内置的电子邮件、短信和推送渠道，我们依赖事务型消息传递来执行消息发送。 这意味着如果您要在历程中使用特定消息模板，则必须在Adobe Campaign Standard中发布该模板。 请参阅此页面以了解如何使用此功能。
历程
您可以使用事件（也称为实时）或用户档案事务型消息模板。
当您选择模板时，消息有效负载中需要的所有字段都会显示在活动配置窗格的 地址 和 Personalization数据 下。 您需要将每个字段映射到要使用的字段（从事件或从数据源）。 您还可以使用高级表达式编辑器手动传递值，对检索到的信息执行数据操作（例如，将字符串转换为大写），或使用函数，如“if， then， else”。 请参阅此页。
电子邮件和短信 section_asc_51g_nhb
对于 电子邮件 和短信，参数相同。
在事务性电子邮件模板中包括 退订链接 内容块。
如果您使用基于事件的模板(rtEvent)，请在消息中纳入一个链接，该链接会将收件人的电子邮件作为URL参数传递，并将他们定向到退订登陆页面。
创建登陆页面，并确保将收件人的取消订阅决策传输到Adobe。
首先，您需要选择事务型消息传递模板。
有两种类别可用：地址和Personalization数据。
您可以使用界面轻松定义在何处检索 地址 或Personalization数据。 您可以浏览事件和可用数据源的字段。 您还可以将高级表达式编辑器用于更高级的用例，例如使用需要传递参数或执行操作的数据源。 请参阅此页。
地址
这些是系统需要知道将消息发送到何处的字段。 对于电子邮件模板，这是电子邮件地址。 如果是短信，就是手机号码。
用于Campaign Standard集成的
Personalization数据
这些是Adobe Campaign标准消息所需的字段。 这些字段可用于个性化消息、应用条件格式或选择特定的消息变体。
Journey Optimizer和Campaign Standard之间的
推送 section_im3_hvf_nhb
在使用推送活动之前，需要配置您的移动设备应用程序以及Campaign Standard以发送推送通知。 使用此文章为移动设备执行必要的实施步骤。
首先，您需要从下拉列表中选择移动设备应用程序和事务型消息。
用于Campaign Standard参数映射的
有两个类别可用：Target和Personalization数据。
Target
在此部分中，您需要定义推送平台。 下拉列表允许您选择Apple Push Notification Server (iOS)或Firebase Cloud Messaging (Android)。 或者，您可以从事件或数据源中选择特定字段，或定义高级表达式。
您还需要定义注册令牌。 表达式取决于如何在事件有效负载或其他Journey Optimizer信息中定义令牌。 如果在集合中定义了令牌，则它可以是简单字段，也可以是更复杂的表达式：
@event{Event_push._experience.campaign.message.profileSnapshot.pushNotificationTokens.first().token}
Personalization数据
这些是Adobe 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 to use the Adobe Campaign Standard actions (Email, SMS, and Push) in Journey Optimizer journeys to send emails, push notifications and SMS via Campaign Transactional Messaging templates.
Intents:
- Configure the Campaign Standard Email, SMS, or Push actions in a journey
- Select and map a Campaign Standard transactional messaging template to journey fields
- Map Address and Personalization Data fields from journey events or datasources to the message payload
- Handle unsubscription for event-based and profile-based transactional email templates
- Configure push notification target platform and registration token for the Campaign Standard Push action
Glossary:
- Transactional Messaging: Adobe Campaign Standard feature on which the Campaign Standard Email, SMS, and Push actions rely to execute message sending (product-specific)
- rtEvent: Abbreviation used for real-time transactional messages, also called event transactional messaging templates (product-specific)
- Profile transactional template: A Campaign Standard transactional messaging template of the profile type; for profile messages the Address (or Target for push) fields are retrieved automatically by the system, and for email the unsubscription mechanism is handled by Adobe Campaign Standard (product-specific)
- Registration Token: A field defined in the Target category of the Campaign Standard Push action; the expression depends on how the token is defined in the event payload or in other Journey Optimizer information (product-specific)
Guardrails:
- The Adobe Campaign Standard integration must be configured before use; refer to the action configuration page.
- Both the Campaign Standard transactional message and its associated event must be published for the template to be usable in Journey Optimizer.
- Collections cannot be passed in Personalization Data fields.
- For real-time transactional messages (rtEvent), a specific setup is required for fatigue, block list, or unsubscription management; for example, add a condition before the message sending to check an unsubscribe attribute stored in Adobe Experience Platform or in a third-party system.
- For profile-based push messages, the Target fields are retrieved automatically; the Target category is only visible for event messages.
- Mobile app must be configured with Campaign Standard before the Campaign Standard Push action can be used.
- Personalization Data fields have an expected format (for example string or decimal), which must be respected.
Terminology:
- Canonical name: Adobe Campaign Standard — Acronym: ACS — variants: Campaign Standard
- Synonyms: “event” transactional messaging template = “real-time” template; “real-time transactional messages” = “rtEvent”
- Do not confuse: “profile transactional template” (unsubscription mechanism handled automatically by Adobe Campaign Standard for email) ≠ “event-based template (rtEvent)” (incorporate a link in the message that directs recipients to an unsubscription landing page)
FAQ:
- Q: Which actions are available through the Adobe Campaign Standard integration? — The Campaign Standard Email, SMS, and Push actions are available when you have Adobe Campaign Standard.
- Q: Does the transactional message need to be published in Campaign Standard before using it in Journey Optimizer? — Yes, both the transactional message and its associated event must be published. If the event is published but the message is not, the message is not visible in the Journey Optimizer interface; if the message is published but its event is not, it is visible but not usable.
- Q: How is unsubscription handled for profile-based email templates? — Unsubscription is automatically handled by Adobe Campaign Standard when using a profile transactional template; include an Unsubscription link content block in the template.
- Q: Can I pass a collection as personalization data? — No, collections cannot be passed in Personalization Data; if the transactional message expects collections, it will not work.
- Q: Where do I map the recipient address for an event-based email? — The Address category in the activity configuration pane is only visible for event transactional messages; for profile messages the address is retrieved automatically.