Mailjet

Mailjet is an email platform from Sinch. Datafly Signal adds or updates contacts in a Mailjet contact list (POST /v3/REST/contactslist/{list_ID}/managecontact) and sets their list subscription.

Why route Mailjet through Datafly Signal

• Events come from your server, not the browser. They reach Mailjet even when a tracker blocker or a failed page unload would have dropped a client-side call.
• Delivery is queued and retried. Signal buffers to Kafka and retries on 429 or a transient failure rather than dropping the event; a permanent rejection goes to the dead-letter queue with the vendor’s reason.
• One consent decision governs every destination. Mailjet is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.

Get your Mailjet credentials

Configuration

Management UI setup

1. Go to Integrations in the sidebar and open the Integration Library tab.
2. Find Mailjet under Marketing Automation and click Install.
3. Choose a preset, enter the fields above and click Install Integration.

Management API setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/mailjet/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "Mailjet",
  "variant": "default",
  "config": {
    "api_key": "your_api_key",
    "secret_key": "your_secret_key",
    "contact_list_id": "your_contact_list_id"
  },
  "delivery_mode": "server_side"
}'

What Signal sends

An example request, rendered from the default preset for newsletter_subscribed:

POST https://api.mailjet.com/v3/REST/contactslist/1234567/managecontact
 
{
  "Action": "addforce",
  "Email": "neill@example.com",
  "Name": "Neill Mcfixture"
}

Presets

Events not listed are not sent. Each preset is a starting point: add, rename or remove mappings on the installed integration.

Notes and limits

• Sign-up, identify, purchase and subscription started are listed but disabled. Their Action, addnoforce, adds a contact who is not yet in the list as subscribed, so these events would subscribe people who never asked for email. Enable them only for a list people joined knowingly.
• Contact properties are not sent by default: Mailjet rejects the whole call if a property has not been created first. Create the property in Mailjet (Contacts > Contact properties), then add a Properties.<name> mapping to the integration.

Consent

Marketing-automation integrations have no consent category by default. Assign the marketing category when you install Mailjet, so an event is delivered only when the visitor has granted it. Cookie-banner consent is not email or SMS opt-in: keep messaging opt-in in Mailjet.

Verify it’s working

1. Open the integration in the Signal Management UI and watch Live Events while you trigger a mapped event.
2. Confirm a 2xx response from Mailjet.
3. Find the contact in Mailjet and check the event or record arrived.

Troubleshooting