# Idea from Berlin sprint: Separate mandatory elements from "classic" (consent-based) mtc.js

**URL:** <https://forum.mautic.org/t/idea-from-berlin-sprint-separate-mandatory-elements-from-classic-consent-based-mtc-js/38335>\
**Category:** Ideas and Feature Requests\
**Created:** [July 6, 2026, 1:46pm UTC](https://forum.mautic.org/t/idea-from-berlin-sprint-separate-mandatory-elements-from-classic-consent-based-mtc-js/38335 "2026-07-06T13:46:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ekke](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/ekke/32/296_2.png) [@ekke](https://forum.mautic.org/u/ekke)\
**Post date:** [July 6, 2026, 1:46pm UTC](https://forum.mautic.org/t/idea-from-berlin-sprint-separate-mandatory-elements-from-classic-consent-based-mtc-js/38335/1 "2026-07-06T13:46:21Z")

</div>

My idea is:  
Certain Mautic features rely on mtc.js which also provides the tracking capabilities.  
Problem: If user does not give consent to tracking, also the other features are broken.  
Specific example: On [mautic.org](http://mautic.org), we cannot easily set a focus item to “show only once” but have to keep annoying people all the time. You all noticed, I’m sure 😉

Thus:

- Move those features into a second javascript snippet
- Namely, make sure that Focus Items, DWC and Forms (incl. captcha, …) work as desired (maybe other? Assets?)
- Ensure that privacy is not violated (e.g. no unnecessary cookies being set)

I think these groups of people would benefit from this idea:

- all who live in privacy-respecting countries yet want the good Mautic features that are currently “collateral damage”

Are you willing to work on this idea?:

- yes

What skills and resources do you need to explore this further?

- All thoughts or ideas welcome!