Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Adobe Campaign Classic: transactional messaging

Send The Wallet Crew transactional emails via Adobe Campaign Classic Transactional Messaging using the script email provider.

Use this option when the organization runs Adobe Campaign Classic and already uses Transactional Messaging for production sends.

Which page? This page covers The Wallet Crew sending its transactional emails through Adobe Campaign Classic. To update passes from an Adobe Campaign Classic workflow, see Adobe Campaign in Marketing automation.

Start with Adobe Marketing Cloud and the prerequisite EmailSender extensibility.

The sample on this page calls the Adobe Campaign transactional messaging REST API: a POST to https://mc.adobe.io/<ORGANIZATION>/campaign/<transactionalAPI>/<eventID> with the recipient in email and the event data in ctx. Adobe documents this API for Campaign Standard and for Campaign v8, where Adobe restricts it to users migrated from Campaign Standard. Check that it is available on the instance.

Setup required in Adobe

Create and publish a Transactional Message Event.

Then decide whether Adobe Campaign will use the rendered HTML from The Wallet Crew or build the final email using Adobe Campaign templates and variables.

A secure server-side authentication method supported by the Adobe Campaign deployment is also required. This is often based on Adobe I/O or IMS.

Implementation notes (event call)

The script usually renders the email (when The Wallet Crew controls the HTML), then calls the transactional event endpoint with the recipient and context.

Store these values as tenant secrets before testing:

  • adobe-clientId

  • adobe-clientSecret

  • adobe-campaign-transactionalUrl (full Transactional Message Event URL)

  • adobe-scope (optional: the scopes of the credential, as listed in the Adobe Developer Console)

The sample builds an unsigned pass URL: see Pass links in emails.

What to validate

Trigger a real transactional email, then validate these points:

  • The Transactional Message Event is published and callable.

  • The payload schema matches the event definition.

  • Adobe Campaign accepts the request and processes the message.

FAQ

Is a Transactional Message Event required?

Yes. The script must call a published Transactional Messaging Event endpoint. That event defines the expected payload schema and which variables are available in the Adobe Campaign template.

Which authentication method should be used?

It depends on the Adobe Campaign deployment and how the Adobe organization manages server-to-server access. This page shows an IMS-based approach because it is common, but the final authentication method should be aligned with the Adobe admin team and the official Adobe documentation for that environment.

What is the most common reason for request rejection?

Schema mismatch. The event definition is strict. When payload fields do not match the expected structure of the event, Campaign rejects or ignores fields, and templates render empty values.

Last updated