On this page: Learn how to send an email from a journey using the integration with Adobe Campaign v7 and v8, including creating the transactional template, event, and action.
This use case explains all the steps required to send an email using the integration with Adobe Campaign v7 and Adobe Campaign v8.
First, create a transactional email template in Campaign. Then, in Journey Optimizer, create the event, action, and design the journey.
To learn more about the Campaign integration, refer to these pages:
Adobe Campaign
Your Campaign instance must be provisioned for this integration. The Transactional Messaging feature must be configured.
-
Log in to your Campaign control instance.
-
Under Administration > Platform > Enumerations, select the Event type (eventType) enumeration. Create a new event type (“journey-event”, in our example). Use the internal name of the event type when writing the JSON file later.
-
Disconnect and reconnect to the instance for the creation to take effect.
-
Under Message Center > Transactional message templates, create a new email template based on the event type previously created.
-
Design your template. In this example, personalization is applied to the profile’s first name and the order number. The first name is in the Adobe Experience Platform data source, and the order number is a field from the Journey Optimizer event. Ensure you use the correct field names in Campaign.
-
Publish your transactional template.
-
Write the JSON payload corresponding to the template.
{
"channel": "email",
"eventType": "journey-event",
"email": "Email address",
"ctx": {
"firstName": "First name", "purchaseOrderNumber": "Purchase order number"
}
}
- For the channel, you need to type “email”.
- For the eventType, use the internal name of the event type created previously.
- The email address will be a variable, so you can type any label.
- Under ctx, the personalization fields are also variables.
Journey Optimizer
-
Create an event. Include the “purchaseOrderNumber” field.
-
Create an action in Journey Optimizer corresponding to your Campaign template. In the Action type drop-down, select Adobe Campaign Classic.
-
Click the Payload field and paste the JSON created earlier.
-
For the email address and the two personalization fields, change Constant to Variable.
-
Now create a new journey and start with the event previously created.
-
Add the action and map each field to the correct field in Journey Optimizer.
-
Test your journey.
-
You can now publish your journey.
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 provides a step-by-step use case for sending a transactional email from Adobe Journey Optimizer using the integration with Adobe Campaign v7/v8, covering Campaign template creation, event and action configuration, and journey design.
Intents:
- Configure a transactional email template in Adobe Campaign v7/v8 for use with Journey Optimizer
- Create an event in Journey Optimizer that includes custom fields such as a purchase order number
- Create and configure a Campaign Classic action in Journey Optimizer with a JSON payload
- Map journey event fields to Campaign personalization variables in the action configuration
- Build and publish a journey that triggers a Campaign transactional email
Glossary:
- Transactional Messaging: A Campaign feature that sends real-time, triggered emails based on events; must be configured before this integration can be used (product-specific)
- Event type (eventType): An enumeration value defined in Campaign that identifies the type of transactional event; its internal name is referenced in the JSON payload (product-specific)
- Campaign Classic action: A Journey Optimizer action type that connects to Adobe Campaign v7/v8 to send transactional messages (product-specific)
- Payload field: The JSON structure pasted into a Journey Optimizer action that defines the data fields sent to Campaign (product-specific)
Guardrails:
- Campaign v7/v8 build 9125 or higher is required for this integration
- The Transactional Messaging feature must be configured in the Campaign instance before use
- After creating a new event type in Campaign, you must disconnect and reconnect to the instance for it to take effect
- Personalization field values set as “Constant” in the action must be changed to “Variable” to allow dynamic population at runtime
Terminology:
- Canonical name: Adobe Campaign v7/v8 — Acronym: ACC — variants: Campaign Classic, Campaign v7, Campaign v8
- Synonyms: “eventType” = “event type internal name”
- Do not confuse: “Campaign Classic action” ≠ “custom action” (Campaign Classic action is a specific built-in action type for ACC integration)
FAQ:
- Q: What Campaign version is required for this integration? — Campaign v7/v8 build 9125 or higher is required.
- Q: What must be configured in Campaign before starting? — The Transactional Messaging feature must be configured and a transactional email template must be created based on the event type.
- Q: How do I make personalization fields dynamic in the Journey Optimizer action? — In the action payload configuration, change the field configuration from “Constant” to “Variable” for fields that will be populated at runtime.
- Q: Where does the first name personalization data come from in this use case? — The first name comes from the Adobe Experience Platform data source, while the order number comes from the Journey Optimizer event payload.
- Q: How do I connect the Journey Optimizer action to the Campaign template? — Select “Adobe Campaign Classic” as the Action type, then paste the JSON payload that matches the transactional message template structure.