# Treasure Engage V0 Export Integration

Engage Studio is Treasure AI's native email delivery service. With this export connector, you can trigger transactional email delivery in real time as part of a customer journey activation workflow.

The connector sends email transactions through the Engage Studio Delivery API, supporting personalized content via merge tags and dynamic templates.

## Prerequisites

- Basic knowledge of Treasure AI
- An email sender configured in Engage Studio. See [Email Sender Configuration](/products/marketing-cloud/engage-studio/channels/email/email-sender-configuration) for details.
- An email template created in Engage Studio. See [Engage Content Creation](/products/marketing-cloud/engage-studio/channels/email/engage-content-creation) for details.
- A Treasure AI Master API Key


## Use Cases

The primary use case for this integration is to incorporate it into a real-time activation workflow for triggered email delivery. Here is an overview of how to configure that workflow:

1. In Engage Studio, create an email sender and configure your email domain.
2. In Engage Studio, create an email template with optional merge tags for personalization.
3. In the Treasure AI Console, create an authentication for this integration.
4. In a Real-time Journey, select this authentication for a new triggered activation.


## Requirements and Limitations

- The connector supports a global rate limit of 1,000 requests per second.
- The connector retries failed requests that return HTTP 500 status codes, up to 3 additional attempts.
- Requests that return HTTP 401 (Unauthorized) are not retried.
- Email sender and template must be pre-configured in Engage Studio before use.


## Static IP Address of Treasure Data Integration

If your security policy requires IP whitelisting, you must add Treasure Data's IP addresses to your allowlist to ensure a successful connection.

Please find the complete list of static IP addresses, organized by region, at the following [document](/apis/endpoints/ip-addresses-integrations-result-workers)

## Export via Treasure AI Console

### Create Authentication

![Treasure Engage V0 Export connector tile in the Integrations Hub Catalog](/assets/engage-export-streaming-logo.50f869abf8de02abc4c99397fb76c7c85f12d2837fdd79594ae0a412198eb0c0.b958b269.webp)

1. Open **Treasure AI Console**.
2. Navigate to **Integrations Hub** > **Catalog**.
3. Search for **Treasure Engage V0** in the Catalog.
4. Hover over the connector tile and select **Create Authentication**.
5. Ensure the **Credentials** tab is selected, then enter your credentials.


### Authentication Fields

![Treasure Engage V0 Export new authentication configuration screen](/assets/engage-export-streaming-new-authentication.cba2209a5dbd76836d66593d5ffe72d84bb38d6b6e3f7a76d30b33fba07af5fc.b958b269.png)

| Parameter | Required | Description |
|  --- | --- | --- |
| Treasure AI Master API Key | Yes | Your Treasure AI Master API Key used to authorize email delivery requests to the Engage Studio Delivery API. |


1. Select **Continue**.
2. Enter a name for your connection.
3. Select **Done**.


### Real-time Triggered Activation

After creating the authentication, the Treasure Engage V0 Export connector is available for real-time customer journey activations.

To create or update a triggered activation:

1. Open your Real-time Journey in Journey Orchestration.
2. Select the triggered activation node.
3. Enter a **Triggered activation name** and optional description.
4. From the **Authentication** drop-down menu, select the Treasure Engage V0 authentication you created.
5. Configure the integration parameters described below.
6. Select **Create** or **Update**.


See [Creating a Real-time Triggered Activation](/products/customer-data-platform/journey-orchestration/realtime/creating-a-real-time-triggered-activation) for additional information.

### Integration Parameters

![Treasure Engage V0 Export Activation Config](/assets/engage-export-streaming-activation-config.201324d0c3e6894b3ddddde70a06dc78a53b6a9abe082f582ca7a12d80921950.b958b269.png)

| Parameter | Required | Description |
|  --- | --- | --- |
| Sender Email | Yes | The ID of the email sender configured in Engage Studio. This determines the "From" address for the email. |
| Email Template | No | The ID of the email template (message) created in Engage Studio. When specified, the connector uses this template for the email body. |
| Campaign ID | No | An optional campaign identifier for tracking and reporting purposes. |
| To Address | Yes | The recipient's email address. |
| To Display Name | Yes | The display name shown to the recipient. |
| Values | Yes | A key-value map of merge tag values for email personalization. These values are substituted into the email template's merge tags (for example, `{{ profile.first_name }}`). |


## Retry and Logging Logic

- The connector retries requests when it receives HTTP 500 status codes.
- If the request succeeds before reaching the maximum retry count (3 retries), the activation log records a success.
- If the request still fails after all retries, the connector logs an error in the activation table.
- Requests that receive HTTP 401 (Unauthorized) are not retried. Verify that the Treasure AI Master API Key is correct if you see 401 errors.
- Activation results and errors are available in the client's activation table for monitoring and troubleshooting.