# Mailjet Destination

## Destination Info

* Accepts [Identify](/docs/segment/connections/spec/identify) calls.
* Refer to it as **Mailjet** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)

This destination is maintained by Mailjet. For any issues with the destination, you may [contact the Mailjet Support team](mailto:support@mailjet.com).

## Getting Started

Navigate to the "App Connections" page\* (Account -> App Connections) and click on the "Segment" destination block to find your Segment Authentication key. \* If you do not see the App Connections page for any reason, contact us at [plugins@mailjet.com](mailto:plugins@mailjet.com). Select a Contact list from the drop down menu that you wish to have Segment send contact property data to.

Be sure and note the contact list id inside the field below the chosen list because you will need to paste it into your Segment account so Segment knows where to send the data to.

Once you have this, navigate over to Segment. Within your existing or new workspace, find Mailjet in the Destinations tab. Click open the tile and paste your Authentication key within the Settings slide out.

Confirm that the contact list id is the same, click save, and then Enable Destination.

## Sending Data from Mailjet

Mailjet supports sending [email events](/docs/segment/connections/spec/email/) to data warehouses and other tools on the Segment platform. These events will be sent as `track` calls to the other destinations you've turned on.

You will have the option to enable this feature when you're on the App Connections page. Simply grab Segment's write-key and paste it in the box and save. You will see the Sources come in as `track` events in your debugger.

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

> \[!NOTE]
>
> Real-time audience syncs to Mailjet  may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field              | Description                                                                   | Required | Type   |
| ------------------ | ----------------------------------------------------------------------------- | -------- | ------ |
| Authentication key | Your Mailjet Authentication key                                               | Yes      | string |
| List ID            | Please provide the default list id for which contacts will be associated with | Yes      | string |