How can GDRP tools like Borlabs collaborate more effectively with Mautic?

Hello, everyone! Because we use Mautic in Germany, we must adhere to GDPR. Borlabs is the name of the cookie-blocking banner we use. Moreover, the GDPR option for the Mautic WordPress Plugin is enabled. This combination fails because Mautic creates two profiles: one anonymous with page tracking information (because the contact is not tracked) and one identified without page tracking information.
This quickly leads to problems with speed. The other issue is that we want to be able to enable tracking when a form is submitted because the user has to agree to our policy, and we are now permitted to track.
However, because the cookie consent banner prevents the mautic cookie from being sent, the form that sends the mautic cookie cannot enable tracking because Borlabs controls that cookie. As a result, we are now developing a workaround that does not use mautic forms but rather a different form editor in WordPress.
A good solution for us would be a setting that states that if a Mautic form is submitted, a second Mautic cookie that allows tracking is set (a cookie that is only sent when a visitor agrees to GDPR and is never set initially), so that the cookie consent banner does not block the cookie. Is that a viable option for developing mautic, or did we overlook another option?

Thank you in advance for your assistance!


Hi @jameswbush

Another option would be to create in your CMS a tickbox in a web form that stores the OK or KO of the RGPD acceptance tickbox, and in Mautic to create a custom field “RGPD” that receives this data when synchronising the website contacts.


There is no real need to use the plugin. In fact it makes things more complicated.

We have Borlabs Cookie enabled. Send events to Matomo Tag Manager (Googles would work too, but hey). If tracking is agreed to, we fire the tracking script (mtc.js) via Matomo. We always load the forms however. They don’t track as long as you don’t submit anything. Submission sets some cookie though. Which can probably be agreed to by the data privacy statement, everybodiy agrees to, when submitting it actively.

Does this help @jameswbush ?