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.
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.
Pick the Adobe product
Each Adobe product has its own API, assets, and governance model. Pick the one the organization already runs.
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
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
SubjectandBodyto 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
Last updated

