채널 활동 channel

이메일 헤더 개인화(이메일).

note important
IMPORTANT
이 기능은 일부 조직에서만 사용할 수 있습니다(제한된 가용성). 액세스 권한을 받으려면 Adobe 담당자에게 문의하십시오.
Journey Optimizer을 사용하면 Campaign Orchestration의 관계형 스토어의 데이터를 포함하여 발신자 정보를 개인화할 수 있으므로 계정 관리자의 이름으로 이메일 전송과 같은 사용 사례를 사용할 수 있습니다. 이 데이터는 조직 또는 법적 규정에 의해 정의된 사용 제한이 적용될 수 있으므로 Journey Optimizer 내의 데이터 작업이 법적 및 규정 준수 의무를 준수하는지 확인하십시오.
Adobe Journey Optimizer은 프로필 수준에서 Adobe Experience Platform(AEP)를 통해 동의를 처리합니다. Journey Optimizer Campaign Orchestration 관계형 비프로필 데이터를 사용하여 개인화할 때 조직은 세분화 및 개인화를 사용하여 동의 정책을 만들고 적용해야 합니다.

채널 구성을 선택한 후 해당 구성에 정의된 값을 바꾸려면 전자 메일 게재 설정 무시​를 사용하도록 설정하십시오. 이 채널 활동에 대해 다음 설정을 사용자 지정할 수 있습니다.

• 전자 메일 헤더 매개 변수: 이름에서, 전자 메일 접두사에서, 이름에 회신 및 전자 메일에 회신

• 실행 주소: Source(프로필 또는 Target Dimension) 및 배달 주소

비워 둔 모든 필드의 경우 Journey Optimizer은(는) 선택한 채널 구성의 값을 사용합니다.

참여 추적(전자 메일 및 모바일).

작업 추적 섹션을 사용하여 받는 사람이 전자 메일 또는 모바일 게재에 어떻게 반응하는지를 추적하세요. 캠페인이 실행되면 캠페인 보고서에서 추적 결과에 액세스할 수 있습니다. 캠페인 보고서에 대해 자세히 알아보기

빠른 전송 모드를 사용(푸시)합니다.

빠른 전송 모드는 캠페인을 통해 대량으로 매우 빠른 푸시 메시지를 전송할 수 있는 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 add, configure, and send channel activities (Email, Mobile message, Push, Direct mail, Line, and Custom channel) within an Orchestrated campaign, including targeting, channel configuration, content creation, testing, sending confirmation, and rate control.

Intents:

• Add a channel activity (Email, Mobile message, Push, Direct mail, Line, or Custom channel) to an Orchestrated campaign canvas.
• Choose a Marketing or Transactional category for a channel activity and configure its target dimension.
• Select a channel configuration and apply rule set capping rules, content experiments, and multilingual content to a channel activity.
• Create and personalize the message content for a channel activity.
• Simulate and test channel activity content before publishing.
• Test a channel activity with Run test and send a proof to a test profile before publishing.
• Confirm or disable confirmation for message sending, and set rate control for outbound channel activities.

Glossary:

• Channel activity (product-specific): an activity added to an Orchestrated campaign canvas that sends a message through a specific channel.
• Category (Marketing or Transactional) (product-specific): field on a channel activity used to choose Marketing or Transactional handling for the message.
• Target dimension (product-specific): the dimension selected in the Target section of a channel activity to determine the delivery target.
• One message per profile / One message per secondary dimension (product-specific): options that determine how many messages are sent when a secondary dimension (related rows linked to a profile) applies.
• Channel configuration (product-specific): defined by a System Administrator; contains technical sending parameters (header parameters, subdomain, mobile apps, etc.) for a channel activity.
• Rule set (product-specific): applied to a channel activity to set capping rules such as frequency capping and quiet hours.
• Simulate content (product-specific): tests content variations using sample input data or AI auto-generation.
• Simulate content (AEP profiles) (product-specific): previews and tests content using test profiles.
• Send without confirmation: a Properties setting that disables the default pause, which by default requires explicit approval before message delivery for non-recurring Orchestrated campaigns.
• Throttle delivery (product-specific): a Schedule tab option that enables rate control (a delivery rate per second) for Email, Mobile message, and Push channel activities.
• Rapid delivery mode (product-specific): a Journey Optimizer add-on that enables very fast, large-volume push message sending through campaigns, used when delay in message delivery is business-critical (for example, an urgent breaking-news push alert).

Guardrails:

• Supported channels in Orchestrated campaigns: only Mobile message, Push, Email, and Direct mail channels are supported (hard limit). Note: the page’s contextual help also describes a Line activity and a Custom channel activity for Orchestrated campaigns, so this guardrail and that description are in conflict in the source page.
• Channel activities limit: an Orchestrated campaign supports a maximum of 10 channel activities (Email, Mobile message, Push, or Direct mail) (hard limit). Only channel activities count toward this limit; targeting and flow control activities do not.
• Exceeding the channel activities limit when saving or publishing causes the operation to fail.
• Transactional messages bypass business rules and do not require opt-in.
• Simulating content with test profiles requires that execution has reached the channel activity in test: in test mode the workflow pauses at the channel activity, so a channel activity located after another channel activity is never reached, and Simulate Content cannot be used for those downstream channel activities.
• Simulating content with test profiles requires a test profile that belongs to the audience targeted by that channel activity; otherwise selecting it does not render a preview of the content.
• Sending a proof to a test profile requires that the profile has the testProfile attribute set to true, has an identity in the namespace configured as the target dimension of the channel activity, and is present in the input transition of the message activity.
• Proof sending is available before and after publication; before publishing, as with Simulate content (AEP profiles), the campaign must first be started in test mode and the workflow must reach the channel activity to get access to the test profiles.
• By default, for non-recurring Orchestrated campaigns, message delivery is paused until the send is explicitly confirmed.
• Wave sending (splitting delivery into scheduled batches before confirming) applies only to outbound channel activities (Email, Mobile, Push, or Direct mail).
• Rate control (Throttle delivery) minimum supported delivery rate, per channel activity: 1 per second (hard limit).
• Rate control (Throttle delivery) maximum supported delivery rate, per channel activity, when Throttle delivery is enabled: 2000 per second (hard limit).
• When setting a delivery rate, the maximum timeframe for which a campaign audience can execute is 12 hours (hard limit). If the delivery rate does not allow the full audience to be sent within that timeframe, the remaining profiles are excluded from the campaign and counted in the campaign report.

Prerequisites and permissions:

• Before adding a channel activity, define the target audience using a Build audience or a Read audience activity.
• Email header personalization (Email) is available only for a set of organizations (Limited Availability); access requires contacting an Adobe representative.
• Rapid delivery mode (Push) is a Journey Optimizer add-on.

Terminology:

• Canonical name: channel activity — variants: Email activity, Mobile message activity, Push activity, Direct mail activity, Line activity, Custom channel activity.
• Canonical name: Adobe Experience Platform — Acronym: AEP.
• Synonyms: none.
• Do not confuse: “Simulate content” (tests content variations with sample input data or AI auto-generation) ≠ “Simulate content (AEP profiles)” (previews and tests content with test profiles).
• Do not confuse: “One message per profile” (one message regardless of how many secondary dimension rows qualify) ≠ “One message per secondary dimension” (one message per qualifying secondary dimension row, so a profile can receive multiple messages).
• Do not confuse: “Marketing” category (opt-in required, business rules applied) ≠ “Transactional” category (opt-in not required, business rules bypassed).

FAQ:

• Q: Which channels are supported in Orchestrated campaigns? — The Guardrails and limitations section states that only Mobile message, Push, Email, and Direct mail are supported; the page’s contextual help also documents Line and Custom channel activities for Orchestrated campaigns.
• Q: How many channel activities can an Orchestrated campaign contain? — A maximum of 10 channel activities (Email, Mobile message, Push, or Direct mail); targeting and flow control activities do not count toward this limit.
• Q: What is the difference between Marketing and Transactional categories? — Marketing requires opt-in and applies business rules; Transactional does not require opt-in and bypasses business rules.
• Q: What is the difference between Simulate content and Simulate content (AEP profiles)? — Simulate content tests content variations with sample input data or AI auto-generation; Simulate content (AEP profiles) previews and tests content with test profiles.
• Q: Why can I not simulate content for some channel activities using test profiles? — In test mode, the workflow pauses at the channel activity, so a channel activity located after another channel activity is never reached, and the selected test profile must belong to the audience targeted by that channel activity.
• Q: Why does nothing happen after I click Run test on a channel activity? — The button remains available even if the message content contains an error; check the Alerts / Warning icon in the canvas toolbar for a content-related error, fix it, and run the test again.
• Q: Why can a test profile not receive a proof? — The profile must have the testProfile attribute set to true, have an identity in the namespace configured as the target dimension of the channel activity, and be present in the input transition of the message activity.
• Q: What happens if message delivery cannot complete within the rate control timeframe? — The maximum timeframe for a campaign audience to execute is 12 hours; if the delivery rate does not allow the full audience to be sent within that timeframe, the remaining profiles are excluded from the campaign and counted in the campaign report.

Examples:

• Welcome series: sending a welcome series through email, Mobile messages, push, and direct mail.
• Post-purchase follow-up: delivering a follow-up email after a purchase.
• Birthday greeting: sending personalized birthday greetings via Mobile messages.
• Cart abandonment: triggering a message through a custom channel when a customer abandons their shopping cart.
• Rate control: setting a delivery rate of 165 messages per second to ensure steady delivery without overwhelming downstream systems (an illustrative value within the 1–2000 per second supported range).

Best practices:

• Use Transactional only for operational or time-sensitive communications; misclassifying a promotional message as Transactional bypasses consent and business rules, which may violate regulatory requirements.

Related pages:

• To define the target audience before adding a channel activity: Build audience (orchestrated/activities/build-audience.md)
• To define the target audience before adding a channel activity: Read audience (orchestrated/activities/read-audience.md)
• For more information on targeting dimensions and how to configure them: Configure a Targeting dimension (orchestrated/target-dimension.md)
• For who defines a channel configuration: System Administrator (start/path/administrator.md)
• To learn how to set up channel configurations: Learn how to set up channel configurations (configuration/channel-surfaces.md)
• To apply capping rules using channel rule sets: Learn how to work with rule sets (conflict-prioritization/rule-sets.md)
• To create a content experiment for a channel activity: Create a content experiment (content-management/content-experiment.md)
• To add multilingual content to a channel activity: Get started with multilingual content (content-management/multilingual-gs.md)
• To view action tracking results for Email and Mobile deliveries: Learn more about campaign reports (reports/campaign-global-report-cja.md)
• To enable Rapid delivery mode for Push notifications: on this page (push/create-push.md)
• To add personalization in Orchestrated campaigns: Learn how to add personalization in Orchestrated campaigns (orchestrated/add-personalization.md)
• To create conditional content in the Email Designer: Learn how to create conditional content in the Email Designer (personalization/dynamic-content.md)
• To simulate content variations with sample input data or AI auto-generation: Learn how to simulate content variations (test-approve/simulate-sample-input.md)
• To preview and test content with test profiles: Preview and test your content (content-management/preview-test.md)
• To run a campaign in test before simulating content: Test your campaign before publishing (orchestrated/start-monitor-campaigns.md)
• To select a test profile matching the channel activity’s target audience: Select test profiles (content-management/test-profiles.md)
• To split delivery into scheduled batches before confirming sending: Learn how to send using waves (delivery/send-using-waves.md)
• To complete activities orchestration and publish the campaign: Learn how to start and monitor Orchestrated campaigns (orchestrated/start-monitor-campaigns.md)

Personas:

• marketer: Can add a channel activity to an Orchestrated campaign canvas, choosing Email, Mobile message, Push, Direct mail, or Line. Can set the Category field to Marketing or Transactional, then select a Target dimension for the delivery in the Target section. The page states that transactional messages do not require opt-in and bypass business rules. Where: “Add a channel activity and define its properties”.

Onboarding:

• Level: Intermediate
• First minimal step: Add a channel activity into the canvas.
• Success check: The list of channel configurations is filtered according to the target set for the delivery, and only compatible configurations appear.
• Previous: Define the target audience before adding a channel activity: Use the Build audience activity (orchestrated/activities/build-audience.md); Define the target audience before adding a channel activity: Use the Read audience activity (orchestrated/activities/read-audience.md)
• Next: Complete the activities orchestration in the canvas and publish the campaign: Start and monitor Orchestrated campaigns with Adobe Journey Optimizer (orchestrated/start-monitor-campaigns.md)