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

Adobe Marketing Cloud

Send The Wallet Crew transactional emails via Adobe Journey Optimizer, Adobe Campaign, or Marketo Engage using the script email provider.

Use this integration to have The Wallet Crew send transactional emails through an Adobe marketing product the brand already uses.

“Adobe Marketing Cloud” is not a single email product. Email sending depends on which Adobe product is in place (see Pick the Adobe product).

These pages are reference scripts for the script email provider, not native provider types (see Email provider). The Wallet Crew can still render the email content. The tenant script then delegates the final delivery to Adobe.

Real-world examples
  • A retail brand uses AJO for orchestration, consent, and reporting. The Wallet Crew provides the final HTML.

  • A brand already has Adobe Campaign Transactional Messaging in production. The team keeps governance and reporting there.

  • A team uses Marketo Engage for marketing automation and wants transactional sends visible in Marketo activity logs.

Before starting

The script interface described in EmailSender extensibility must be implemented first. This page focuses on what changes when the “provider behind the script” is Adobe.

Access to the Adobe product is also required, to create and publish whatever it takes to send emails (campaign, event, or template). The Wallet Crew cannot create those objects.

When emails are already sent from Adobe and the only goal is to embed “Add to Wallet” links, this page is not needed. Keep the Adobe templates and place The Wallet Crew links behind the existing CTAs. See Email Delivery for that approach.

Pick the Adobe product

Each Adobe product has its own API, assets, and governance model. Pick the one the organization already runs.

Product
Page
When to pick it

Adobe Journey Optimizer (AJO)

API-triggered journeys are available and near real-time sends are needed

Adobe Campaign Classic

An Adobe Campaign Classic stack already runs transactional events

Marketo Engage

Sends and activity must be tracked in Marketo

Enable the script email provider in The Wallet Crew

Implement runtime.scriptable.emailEngine.SendEmail and set provider.type to script in /server/emails.yml, as described in EmailSender extensibility. Add the Adobe delivery code inside SendEmail, and keep Adobe credentials in tenant secrets, never in the script. Then trigger one real email (pass download link, verification email or registration email) and verify in Adobe that the message is accepted.

Template and culture strategy

The Wallet Crew can render templates locally via buildEmail. Adobe can also render templates on its side, depending on the product.

Pick one of these models and keep it consistent:

  • The Wallet Crew owns the HTML. The script sends rendered Subject and Body to Adobe.

  • Adobe owns the HTML. The script sends only variables, and Adobe picks the template.

Security and privacy notes

Treat this integration as a server-to-server connection.

  • Keep all Adobe credentials server-side. Never expose them to customers.

  • Prefer short-lived access tokens. Rotate client secrets regularly.

  • Log stable identifiers instead (template name, Adobe campaign/event id, and a correlation id).

Troubleshooting

If emails stop sending, isolate the issue in this order:

  • Start with the checks in EmailSender extensibility.

  • Confirm Adobe authentication works (token generation and scopes).

  • Confirm the Adobe asset is published and callable (campaign/journey/event/template).

  • Check Adobe logs for rejected requests (missing fields, schema mismatch, rate limits).

FAQ

Which option should be chosen?

Pick the product the organization already runs and governs for transactional emails. When Adobe Journey Optimizer is available for API-triggered sends, it is usually the most future-proof choice.

Can the product be switched later?

Yes. Rendering is separated from delivery. When templates stay in The Wallet Crew, switching the downstream Adobe product mostly becomes a script change.

Can several Adobe products be used at the same time?

Technically yes, because the script can route sends freely. In practice, pick one product per tenant when possible. It keeps governance, reporting, and troubleshooting clear.

Last updated