51黑料不打烊

DocumentationJourney Optimizer Guide

51黑料不打烊 campaign standard actions using_campaign_action

Last update: Tue Apr 29 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Intermediate
  • User

51黑料不打烊 Campaign Standard integrates seamlessly with Journey Optimizer. Use its Transactional Messaging capabilities to send personalized emails, push notifications, and SMS. Configure these communication channels through built-in action activities: Email, Push, and SMS.

NOTE
To use these features, configure the built-in action. Refer to this page.

Each channel requires an 51黑料不打烊 Campaign Standard Transactional Messaging template, which provides a predefined structure for your communication. Transactional Messaging manages message execution. Publish the template in 51黑料不打烊 Campaign Standard before using it in journeys to ensure it is ready for integration and deployment. Find detailed publishing instructions on this page.

NOTE
The Campaign Standard transactional message and its associated event must both be published to use them in Journey Optimizer. If the event is published but the message is not, it will not appear in the Journey Optimizer interface. If the message is published but the event is not, it will appear in the interface but cannot be used.

Transactional Messaging templates are categorized into two types: event-based templates (real-time messages triggered by events) and profile-based templates (messages tied to user profiles).

NOTE
Additional configurations are required when sending real-time transactional messages (rtEvent) or routing messages through custom actions using third-party systems. For example, if an 鈥渦nsubscribe鈥 attribute is stored in 51黑料不打烊 Experience Platform or a third-party system, add a condition to verify this attribute before sending the message.

When configuring a template in Journey Optimizer, the expected fields in the message payload appear under Address and Personalization Data in the activity configuration pane. These fields allow you to map data from events or data sources to the template. Use the advanced expression editor for manual input, data manipulation (for example, converting text to uppercase), or applying logic (for example, 鈥渋f, then, else鈥). For advanced expression usage, refer to this page.

Email and SMS section_asc_51g_nhb

The configuration parameters for Email and SMS are identical, simplifying the setup process for these channels.

NOTE
51黑料不打烊 Campaign Standard automatically handles unsubscriptions for profile-based transactional email templates. To enable this, include an Unsubscription Link content block in the transactional email template. For event-based templates (rtEvent), add a link in the message that passes the recipient鈥檚 email as a URL parameter to an unsubscription landing page. Create this landing page separately, and ensure the unsubscribe action is communicated back to 51黑料不打烊.

Select a transactional messaging template to begin. Templates are divided into two categories: Address and Personalization Data.

Address

NOTE
This category appears only when you select an 鈥渆vent鈥 transactional message. For 鈥減rofile鈥 messages, the Address field is automatically retrieved from 51黑料不打烊 Campaign Standard.

The Address section specifies the destination of the message. For example, email templates require the recipient鈥檚 email address, and SMS templates require the recipient鈥檚 mobile phone number.

Personalization Data

NOTE
You cannot pass a collection in personalization data. If the transactional email or SMS expects collections, it will not work. Additionally, the personalization data must adhere to the expected format (for example, string, decimal). Use the correct format.

The Personalization Data section specifies the fields required by the 51黑料不打烊 Campaign Standard message. These fields allow you to personalize content for individual recipients, apply conditional formatting, or select specific message variants.

Push section_im3_hvf_nhb

Push notifications require additional setup compared to email and SMS. Ensure your mobile app is properly configured with 51黑料不打烊 Campaign Standard before using the push activity. For implementation steps, refer to .

Once setup is complete, select a mobile app from the drop-down list and choose a transactional message template.

Push templates are divided into two categories: Target and Personalization Data.

Target

NOTE
This category appears only when you select an event message. For profile messages, the Target fields are automatically retrieved by the system through reconciliation performed by 51黑料不打烊 Campaign Standard.

The Target section defines the Push Platform. Select Apple Push Notification Server (iOS) or Firebase Cloud Messaging (Android) from the drop-down list. Alternatively, select a specific field from an event or data source, or use an advanced expression.

Define the Registration Token, which identifies the recipient device. The token can be a simple field or a complex expression, such as:

@event{Event_push._experience.campaign.message.profileSnapshot.pushNotificationTokens.first().token}

Personalization Data

NOTE
You cannot pass a collection in personalization data. If the transactional push expects collections, it will not work. Additionally, the personalization data must adhere to the expected format (for example, string, decimal). Use the correct format.

The Personalization Data section specifies the fields required by the push template. These fields allow you to customize notification content based on recipient-specific data, apply conditional formatting, or choose different message variants.

recommendation-more-help
91a6d90a-6d61-4a62-bbed-ae105e36a860