Mautic

Mautic runs campaigns through segments, point rules, conditions and scheduled actions. Those functions work without a language model. At 1Life, the underlying segmentation and journeys were supplemented by Webmecanik features that generated email subjects and optimized send times from contact activity. That is a partner implementation, rather than a standard AI service operated by the Mautic project.

The practical center remains marketer designed automation: capture a lead, update its profile, change its campaign path and pass it to sales when the configured conditions are met. Downloadable assets can influence contact scores and journeys. Files may reside locally or in Amazon S3, and UTM parameters on asset links feed download reports.

The Campaign Builder executes positive and negative branches, conditions and actions configured by a marketer. Delays can use a specific date or an elapsed period, and a contact can jump to another step or move into a different campaign. Forms and segment membership determine entry. On the contact timeline, scheduled events can be rescheduled or canceled, while completed decisions expose their evaluated fields and results. Mautic offers no described approval or rollback step for external integration actions, and a campaign can change connected records once activated.

AI behavior depends on the service or plugin attached to a Mautic installation. The project does not operate a common hosted model service, and its proposed approach allows local or external models. Segment and campaign creation assistance remains a direction for development, rather than a single standard model stack. In the core campaign engine, decisions follow configured conditions and scoring rules. Model identities, generated content markings and inference retention therefore have no common setting across partner offerings; these remain properties of the selected extension and provider.

Prospectiva used Mautic with Codefive to coordinate marketing across its engineering and consulting businesses. A custom plugin handled contacts with several contracts and business relationships, cutting duplicate messages while supporting cross selling. The customer reports an ROI increase above 80 percent, without a measurement period or calculation basis, and the result reflects implementation work and custom development as well as the software.

At a wider scale, the project counts more than 200,000 companies using Mautic, a measure of adoption rather than outcomes. Prospectiva's gain came from a new data model, campaign design and implementation together.

Contact preferences can suppress individual channels, pause messages for a date range and limit communication frequency. Removing a channel creates a Do Not Contact entry for that channel, so an email opt out does not automatically represent an SMS opt out. Categories and segments provide more granular subscriptions, and the unsubscribe page can expose these preferences. Marketers control the page labels and visible choices. These are concrete controls for an existing audience, while consent verification and telephone screening depend on what each installation adds.

Mautic can disable email and link tracking, anonymize visitor IP addresses and place website tracking behind a marketing cookie consent choice. Cleanup tasks remove old anonymous visitors, audit logs and inactive contacts, while progressive forms collect information over successive interactions. A self hosted organization controls the database and the processing environment.

The software project is not the processor for every installation: a managed host supplies its own processing contract, subprocessors and transfer terms. There is no single DPA or hosting policy that governs all Mautic deployments.

Audience records arrive through customer forms, CSV imports, website activity and connected systems. The contact history distinguishes imports, form submissions, API creation and integration activity, giving marketers a way to trace how a person entered the database. Custom identifiers and email addresses help merge related records. Mautic does not supply a common prospect database with a shared sourcing license. Rights to imported lists and enrichment remain with the organization and its suppliers, and no indemnity for those external datasets comes with the software.

Salesforce connectivity uses an authorized connected app and API credentials. Field mappings connect Mautic contacts with Salesforce Leads and Contacts, while campaign or form actions can push records into the integration. This is an API workflow rather than a browser session acting as a seller. Developers can also connect systems through REST calls and webhooks.

Sending runs through whichever email service the operator configures, and the managed plans let a customer authenticate several of its own sending domains in one installation. Third party plugins extend the operating surface, so their permissions and methods vary independently of the core connector.

A self hosted Mautic database stays in the environment selected by its operator until a configured integration sends data elsewhere. The project does not host an AI service that pools those databases for model development. Adding external generation or predictive tools creates a separate data path governed by that provider. Cleanup controls can reduce stored visitor and contact information, but do not by themselves delete data already sent to an AI service. Training and retention terms differ by plugin, with no common policy across the ecosystem.

Campaign emails use the marketer's sender identity, content and contact fields. Preference pages can carry the organization's branding and translated labels, while dynamic content changes the offer or call to action according to a contact's profile. These are conventional marketing messages rather than a standard conversational agent pretending to be a salesperson. AI extensions can contribute text to that workflow.

The core product adds no automatic label to generated content, and Article 50 handling is left to each installation. The selected extensions and campaign settings shape the recipient's experience in each installation.

The Salesforce connector maps contact fields, pushes Mautic contacts into Leads and pulls Salesforce Leads or Contacts back into marketing. Activity can flow into a custom Salesforce object for reporting, or appear as a link to the Mautic timeline. REST endpoints and webhooks support custom connections beyond the packaged plugins. The application marketplace installs community plugins and themes and checks compatibility against the installed Mautic version. The result is an extensible integration layer in which choices such as field ownership and activity representation stay visible to the administrator.

Mautic can run on infrastructure the customer owns, in a private environment or with a managed hosting partner, and the operator decides where the application and database live, including in the EU. Self hosting calls for a virtual private or dedicated server rather than shared hosting, PHP 8.2 to 8.5 for the current 7.x series, MySQL 5.7 or MariaDB 10.2 and later, and Apache or Nginx. Patch releases arrive monthly, feature releases quarterly and major versions every two years. A managed provider may run a different tenancy arrangement, so residency and isolation follow the chosen architecture and host.

The Mautic Security Team handles core software, officially supported plugins and project infrastructure, takes private reports through GitHub and follows coordinated disclosure, keeping issues private until a fix ships. As a CVE naming authority under MITRE, it issues CVEs for anything in the Mautic namespace, and it gives at least two weeks' notice before any unscheduled security release.

Third party plugins and individual installations sit outside that response boundary, so administrators must apply releases and secure their own servers. No SOC 2 report or ISO certification covers Mautic deployments as a whole, and a hosting partner's certifications cover only its own service.

The downloadable software carries no license subscription and includes the core marketing automation features under the GPL. The operating bill comes from infrastructure, email delivery, maintenance and any implementation or support. Managed plans from Dropsolid start at €247.50 a month billed annually, or €275 quarterly, for up to 50,000 contacts and 50,000 emails a month, with Professional from €1,237 a month and Enterprise quoted; 40 percent of that revenue goes to the community. Older versions can buy extended security support in one year blocks. A self hosted production deployment has no single price, since capacity and services vary.

Contact lists export as CSV or Excel, and a contact's change log can be downloaded separately. CSV exports arrive through a link that requires the requesting user to sign in; the current export path supports up to one million contacts. Self hosting also gives the operator access to the underlying database and software under the GPL license. That makes continued operation possible without renewing a software subscription.

A managed host's backup handover, deletion schedule and cancellation terms remain separate, rather than a uniform offboarding promise from the project. Deleting an asset removes its download statistics, while contact points already earned from that asset remain. Unpublishing limits availability without that deletion.

Email and SMS frequency rules apply globally or per contact, and marketing email waits once a contact reaches the configured limit. The setting that allows sending to unsubscribed contacts treats a message as transactional and leaves it out of those counts, which matters when several journeys reach the same person. Delivery infrastructure belongs to the chosen host and sending service.

On the managed plans from Dropsolid, the project's official hosting partner, Essential sends from a shared IP at up to 100 emails a minute and Professional from a dedicated IP at up to 2,000, both with sending reputation monitoring.

Mautic serves teams that want to shape marketing automation around their own data and technical environment, and the project counts more than 200,000 companies as users. Prospectiva's engineering and consulting businesses and Druid's software operation show B2B uses, while the wider base includes education and consumer services. Multilingual campaigns, conditional website content and custom plugins support programs across business units and markets. Managed plans place no limit on team members. Support and localization come from the provider an organization selects, or from the community forum and Slack.