Set up your bannerConfigure Your ToolsMarketing Automation and CRM

Mautic

How to configure Mautic at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Support marketing analytics, Receive personalised marketing offers

Overview

This guide explains how to implement different privacy configurations for Mautic and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. Mautic open-source marketing automation: the mtc.js tracking script on the website and Mautic forms.

What the service does in this scope. The tracking script is loaded from the Mautic instance (https://<your-mautic>/mtc.js). Mautic sets the first-party cookies mautic_device_id, mtc_id, mautic_referer_id and mtc_sid; Mautic's own site lists mautic_device_id with 12 months. Mautic merges actions into the contact with the same cookie or creates one based on the device ID. The tracking pixel (mtracking.gif) in emails and landing pages can set cookies without checking consent.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskSelf-hosted Mautic in the EU; mtc.js loaded after consent; anonymous visits and form-identified contacts.
Configuration B — Higher riskMautic hosted by a third party (e.g. Mautic SaaS partner); mtc.js after consent; contact tracking linked to email clicks.

No configuration without prior consent. All four cookies are set by mtc.js. Note that Mautic landing pages and tracking pixels can set cookies independently of the website script; block or configure these as well.

Step 1 — Configure Mautic

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionSupport marketing analyticsSupport marketing analytics; Receive personalised marketing offers
2HostingOperator infrastructureSelf-hosted (EU)Third-party host
3Tracking scriptmtc.js via Consenter script blockingAfter consentAfter consent
4Mautic landing pages / tracking pixelMautic configurationAvoid on pages without consentUsed in emails

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesSupport marketing analyticsSupport marketing analytics, Receive personalised marketing offers
Tracking methodFirst party tracking (cross-session)First party tracking (cross-session)
IdentifierDevice identifiers, Direct identifier (after form submission)Device identifiers, Direct identifier
Data categoriesBrowsing and interaction data, Device characteristics, Device identifiers, IP address, User-provided dataAs A, plus direct identifier, Users' profiles
Legal role of data recipientSelf-hostedProcessor
Personalisation modelGroup based (behaviour)Profile based
Maximum storage duration12 months (mautic_device_id, per Mautic's own site)12 months
Processing locationOwn EU serverPer hosting contract; add the United States if a US provider hosts the instance

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page