Mautic is flexible out of the box, but the setup that actually fits your business — custom fields, branded themes, a proper mail transport, locked-down access — takes real configuration work. Your vibe-code agent can do that work: it edits app/config/local.php, touches themes and templates, runs console commands, and restarts services while telling you each step. Here are ten customizations to ask for.
1. Add custom contact fields the right way
Out of the box, contacts lack things like plan tier, account owner, or renewal date, and those are exactly the fields your segments and scoring will need. The assistant creates the field with the correct type and choice list, then confirms it appears in forms, segment filters, and imports. It also checks that the column exists in the database and is indexed sensibly.
Plan the fields once, with names you’ll still understand in a year — plan_tier beats field_4. The assistant can also backfill the new field from existing data if you have it. Ask: “Add a ‘plan_tier’ contact field with choices Starter, Growth, and Enterprise, and make it usable in segments and forms.”
2. Brand a landing page theme
The stock themes look generic, and your landing pages are where paid traffic lands. The assistant can copy a theme into a new one, swap your logo, colors, and fonts in the theme config and CSS, and leave the original untouched for reference. It can then build a test page using the new theme so you see the result immediately.
Keep brand values in one place in the theme config so future changes are one-line edits. Say: “Copy the ‘blank’ theme into a new theme called ‘acme’, change the primary color to our brand blue #1D4ED8, and swap in our logo.”
3. Restyle a form to match your site
Mautic forms render with default styling that clashes with most sites, and the form builder’s style controls only go so far. The assistant overrides the form HTML: full-width inputs, your brand color on the button, and a redirect to your thank-you page after submit. It can also inject the CSS your site already uses so the form inherits your fonts.
Check the result on a real page, including mobile width, before embedding everywhere. Try: “Make my ‘newsletter-signup’ form match my site — full-width inputs, our brand color button — and redirect to /welcome after submit.”
4. Set up a serious mail transport
Default PHP mail lands in spam folders, which quietly kills open rates before you even measure them. The assistant configures SMTP or a provider like Amazon SES in local.php, sets the default from address and sender name, and sends a test message through the real path. It can also check your SPF and DKIM records so authentication aligns with the sending domain.
This is the highest-leverage single change on a fresh install. Everything downstream — campaigns, digests, alerts — depends on mail actually arriving. Ask: “Switch Mautic to send through Amazon SES with these credentials, set the default from address, and send me a test email.”
5. Add an exit-intent focus item
Focus items are Mautic’s built-in popups, bars, and notification boxes, and each one ties to a form you already have. The assistant creates the item, sets it to trigger on exit intent for visitors on your pricing page, links the offer form, and checks the tracking script on the target page. It can verify the item renders before you call it done.
Keep the offer specific — a buyer’s guide beats “subscribe to our newsletter” for exit intent. One focused item per page is plenty. Say: “Create a focus item that shows an exit-intent popup on the pricing page offering our buyer’s guide, linked to a Mautic form.”
6. Tune configuration for your server size
Mautic’s defaults assume a roomy machine. On a small VPS, batch sizes and memory limits in local.php decide whether an email send to ten thousand contacts finishes or dies halfway and confuses your cron state. The assistant can right-size the settings for your RAM and CPU and explain the trade-off between batch size and send time.
It can also enable the queue for emails if you’re sending in bulk, which smooths spikes and keeps the UI responsive. Ask: “My server has 2 GB of RAM — review local.php and set batch sizes and limits so email sends don’t exhaust memory.”
7. Lock down admin and API access
A marketing server that holds your entire contact list is a real target, and defaults are wider than they should be. The assistant can disable basic-auth API access so only OAuth2 clients work, verify the admin account uses a strong password, tighten file permissions on the app directory, and confirm the install blocks directory listing.
It can also review which API endpoints are actually in use and disable the rest. Small surface, fewer surprises. Say: “Turn off basic auth for the API so only OAuth2 works, and check that admin access is properly locked down.”
8. Serve forms and tracking from your own domain
By default, Mautic pages, forms, and the mtc.js tracker live on the server domain, which some browsers and ad blockers treat with suspicion. The assistant adjusts site_url and the web server virtual host so everything serves from your domain, and updates the tracking script references on your site to match.
The win is trust: forms on your own domain look like your forms, and tracking is far less likely to be blocked. Expect a short testing pass after the switch. Ask: “Point forms.mydomain.com at this server and serve forms, landing pages, and tracking from it instead of the default domain.”
9. Create OAuth2 credentials for integrations
Tools like n8n, your CRM, or your own scripts need API access, and guessing the OAuth2 flow from docs is slow. The assistant creates the API credentials inside Mautic, documents the token endpoints and scopes, and proves it with a working call. It can also store the client secret in a config file on the server rather than a sticky note.
One credential per integration, so you can revoke a single tool without breaking the rest. Try: “Create OAuth2 API credentials for my n8n integration and show me a working curl call that lists contacts.”
10. Run a safe upgrade with a rollback path
Skipping Mautic upgrades means falling behind on security fixes, but blind updates break installs, especially across major versions. The assistant checks PHP version compatibility against the target release, takes a full backup first, runs the update from the console, and verifies afterward that cron jobs run, emails send, and campaigns trigger.
Ask for the verification step explicitly — “it upgraded fine” and “Mautic works” are different claims. Say: “Prepare an upgrade to the latest Mautic release — check PHP compatibility, back everything up first, run the update, and verify campaigns still trigger.”
Every customization above is a change you can inspect: config diffs, theme files, and test emails. Ask the agent to show what it changed, keep the backups it makes, and your Mautic install stays yours.
