Mautic

Datafly Signal syncs identified visitors into Mautic, the open-source marketing automation platform, as Contacts. Signal delivers email, name, phone, location, the visitor’s IP, and UTM attribution server-to-server to your own Mautic instance using the Mautic REST API. Because delivery is server-side, contacts are created and kept current without loading the Mautic tracking script in the browser.

Prerequisites

You need a running Mautic instance (self-hosted or cloud) that Signal can reach over HTTPS, and a Mautic user whose credentials Signal will use for the API.

Step 1: Enable the API

1. In Mautic, go to Settings (the cog icon) > Configuration > API Settings.
2. Set API enabled? to Yes.
3. Set Enable HTTP basic auth? to Yes.
4. Click Apply / Save & Close.

Step 2: Create or choose an API user

Signal authenticates as a normal Mautic user over HTTP Basic auth.

1. Go to Settings > Users.
2. Create a dedicated user for Signal (recommended) or pick an existing one.
3. Make sure the user’s role grants permission to create and edit contacts.
4. Note the user’s username and password — Signal needs both.

Step 3: Note your instance URL

Your Mautic base URL is the root of the instance, for example https://mautic.example.com. Signal appends the API path automatically.

Configure in Signal

Configuration Fields

Management UI Setup

1. Go to Integrations > Add Integration > Mautic.
2. Choose the Default preset.
3. Enter your base_url, api_user, and api_password.
4. Select the consent categories that should gate delivery (typically marketing).
5. Click Save.

API Endpoint

POST https://{base_url}/api/contacts/new

Signal sends a flat JSON Contact body authenticated with HTTP Basic auth (Authorization: Basic base64(api_user:api_password)). Mautic deduplicates incoming contacts on its unique identifier field — email by default — so repeated deliveries for the same visitor merge onto one Contact rather than creating duplicates.

Identity Signals

Mautic is your own CRM, so personal data is delivered in plaintext (no hashing). The integration maps the following from datafly.identify() traits and the request context to native Mautic Contact field aliases:

How to send user data

Call datafly.identify() when a visitor logs in, registers, or submits a form:

datafly.identify("user-123", {
  email: "jane.doe@example.com",
  firstName: "Jane",
  lastName: "Doe",
  phone: "+44 7700 900123",
  city: "London",
  country: "GB"
});

Event Mapping

The Default preset delivers identity-bearing events as a Contact upsert. All mapped events resolve to the same POST /api/contacts/new call; what differs is the trait/property data attached.

All other events are dropped (defaults.action: drop).

Example: Signed Up event

Datafly.js call:

datafly.identify("user-123", {
  email: "jane.doe@example.com",
  firstName: "Jane",
  lastName: "Doe"
});
 
datafly.track("Signed Up", {
  method: "email"
});

Mautic payload sent by Signal:

{
  "email": "jane.doe@example.com",
  "firstname": "Jane",
  "lastname": "Doe",
  "ipAddress": "203.0.113.50",
  "lastActive": "2026-06-06 14:32:10",
  "utm_source": "newsletter",
  "utm_medium": "email",
  "signal_signup_method": "email",
  "tags": ["signal-marketing-consent"]
}

Mautic responds 201 Created with the full Contact object (or 200 when an existing Contact on the same email is updated).

Testing

Troubleshooting