Adobe Campaign Standard 통합 using_adobe_campaign_standard

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 integrate Journey Optimizer with Adobe Campaign Standard through a built-in action so journeys can send emails, push notifications, and SMS through its transactional messaging capabilities.

Intents:

• Configure the built-in AdobeCampaignStandard action for a sandbox
• Paste and test the Adobe Campaign Standard instance URL
• Make the Email, Push, and SMS actions available when designing a journey
• Use a Reactions event to react to tracking data from a Campaign Standard message
• Understand the capping and activity constraints of the integration

Glossary:

• AdobeCampaignStandard action: The built-in action selected from the action list to connect Journey Optimizer to Adobe Campaign Standard (product-specific)
• Transactional Messaging: The Adobe Campaign Standard capability used to send emails, push notifications, and SMS from Journey Optimizer (product-specific)
• Test the instance URL: The button that verifies the host, that the URL starts with https, and that the organization matches the Journey Optimizer organization (product-specific)
• Reactions event: An event that reacts to tracking data related to a Campaign Standard message sent within the same journey (product-specific)

Guardrails:

• A capping rule of 4,000 calls per 5 minutes is automatically defined for Adobe Campaign Standard actions.
• The Adobe Campaign Standard integration is set up through a dedicated built-in action and must be configured for each sandbox.
• You cannot use a Campaign Standard action with an Audience qualification or Read audience activity.
• A journey cannot use both built-in channel actions and Campaign Standard actions.
• The transactional message and its associated event must both be published: if only the event is published the message is not visible, and if only the message is published it is visible but not usable.

Terminology:

• Canonical name: Adobe Campaign Standard integration — Acronym: ACS — variants: Campaign Standard action, AdobeCampaignStandard action, built-in action
• Do not confuse: “built-in channel actions” (native Journey Optimizer channel actions) ≠ “Campaign Standard actions” (Adobe Campaign Standard integration actions), which cannot both be used in the same journey
• Do not confuse: “Email, Push, SMS actions” (available after configuring the integration) ≠ “Reactions event” (reacts to tracking data of a sent Campaign Standard message)

FAQ:

• Q: What is the capping limit for Adobe Campaign Standard actions? — A capping rule of 4,000 calls per 5 minutes is automatically defined.
• Q: Why is a Campaign Standard message not visible or not usable in Journey Optimizer? — If the event is published but the message is not, it is not visible; if the message is published but the event is not, it is visible but not usable.
• Q: Does the integration need to be configured once for the whole organization? — No, it is set up through a dedicated built-in action that must be configured for each sandbox.
• Q: Which tracking reactions are available per channel? — Push can react to clicked, sent, or failed; SMS to sent or failed; email to clicked, sent, opened, or failed.
• Q: Why can a journey not use both built-in channel actions and Campaign Standard actions? — A journey cannot combine built-in channel actions and Campaign Standard actions.