A simple and readable structure The tarteaucitron service list is defined as a JavaScript object. Each service corresponds to a clear, readable, and self-contained configuration block. This block describes the service type, name, information links, potential cookies, and most importantly how the service is loaded or blocked. Loading and fallback Each service exposes a loading … Read more
An event-based mechanism tarteaucitron relies on a simple principle: events triggered by explicit user actions. These actions can occur in the management panel or directly within the page when dealing with iframe-based services. As long as the user has not agreed to load a given service, it remains blocked. No script is loaded and no … Read more
Setting clear boundaries From the beginning, tarteaucitron has been built on explicit choices. Some are technical, others relate to the project’s positioning. These limits are not shortcomings, but safeguards. I prefer to clearly state what tarteaucitron will never do, rather than letting people assume it could cover everything. A simple economic model tarteaucitron will never … Read more
A tag manager first tarteaucitron.io is first and foremost a tag manager. Its role is to condition the loading of third-party services based on the user’s choice. It is not an analytics tool and not a legal service, but a technical mechanism running in the browser. In the free version, this requires explicit integration. For … Read more
The context in 2014 The first commit of tarteaucitron dates back to September 14, 2014. At that time, cookie regulations were starting to emerge, with little technical guidance. I was running several blogs and an audience measurement tool. The goal was simple: comply with the law. There were no CMPs as we know them today. … Read more