> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/connectors/email-provider/adobe-marketing-cloud.md).

# 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](#pick-the-adobe-product)).

These pages are **reference scripts** for the script email provider, not native provider types (see [Email provider](https://docs.thewalletcrew.io/connectors/email-provider.md#where-the-configuration-lives)). The Wallet Crew can still render the email content. The tenant script then delegates the final delivery to Adobe.

<details>

<summary><strong>Real-world examples</strong></summary>

* 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.

</details>

## Before starting

The script interface described in [EmailSender extensibility](https://docs.thewalletcrew.io/connectors/custom-connector/emailsender-extensibility.md) 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.

{% hint style="info" %}
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](https://docs.thewalletcrew.io/guides-enrolment/enrolment/via-email.md) for that approach.
{% endhint %}

## 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) | [Adobe Journey Optimizer](https://docs.thewalletcrew.io/connectors/email-provider/adobe-marketing-cloud/adobe-journey-optimizer.md)                                        | API-triggered journeys are available and near real-time sends are needed |
| Adobe Campaign Classic        | [Adobe Campaign Classic: transactional messaging](https://docs.thewalletcrew.io/connectors/email-provider/adobe-marketing-cloud/adobe-campaign-transactional-messaging.md) | An Adobe Campaign Classic stack already runs transactional events        |
| Marketo Engage                | [Marketo Engage (Transactional Email API)](https://docs.thewalletcrew.io/connectors/email-provider/adobe-marketing-cloud/marketo-engage-transactional-email-api.md)        | Sends and activity must be tracked in Marketo                            |

{% hint style="warning" %}
Pick one rendering strategy. Avoid duplicating templating in both The Wallet Crew and Adobe. Do not mix both models across journeys: it creates hard-to-debug differences between emails.
{% endhint %}

## 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](https://docs.thewalletcrew.io/connectors/custom-connector/emailsender-extensibility.md). 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](https://docs.thewalletcrew.io/connectors/custom-connector/emailsender-extensibility.md#troubleshooting).
* 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

<details>

<summary><strong>Which option should be chosen?</strong></summary>

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.

</details>

<details>

<summary><strong>Can the product be switched later?</strong></summary>

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

</details>

<details>

<summary><strong>Can several Adobe products be used at the same time?</strong></summary>

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.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thewalletcrew.io/connectors/email-provider/adobe-marketing-cloud.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
