Integrations / Marketing Automation

Mailjet

Server-side contact sync to a Mailjet contact list via the managecontact REST API. Upserts each identified visitor as a Mailjet contact, subscribes them to the configured list (addnoforce, never force-resubscribing opted-out contacts), and writes name plus marketing-opt-in as contact properties.

Datafly Signal delivers first-party events to Mailjet server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Mailjet expects.

Why route Mailjet through Datafly Signal

Profiles update from the server, not the browser

Events reach Mailjet even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.

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.

What ships in the blueprint

Mapped events

identifynewsletter_subscribednewsletter_unsubscribedpurchasesign_up

Vertical presets

Default. Each preset starts from a working configuration for that vertical rather than a blank field map.

Full field mappings, configuration fields, and troubleshooting are in the Mailjet documentation.

Frequently asked questions

Does Datafly Signal integrate with Mailjet?

Yes. Datafly Signal delivers first-party events to Mailjet server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Mailjet expects. The integration is included in every deployment at no additional cost.

How is server-side Mailjet tracking different from the Mailjet tag?

The Mailjet tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Mailjet from your server, so delivery does not depend on browser conditions.

Which events can Signal send to Mailjet?

The blueprint ships with mappings for identify, newsletter_subscribed, newsletter_unsubscribed, purchase, sign_up. Any event in your schema can be mapped to Mailjet through pipeline configuration without a code change.

Do I need to keep the Mailjet tag on my site?

No. Signal delivers to Mailjet from the server, so no client-side Mailjet script is required on your site.

Ready to move Mailjet server-side?

See how Datafly Signal delivers first-party events to Mailjet from infrastructure you control, with hashed identity and consent enforcement built in.