Custom consent designs
Custom consent designs let you change your consent banner’s HTML and CSS, with an optional developer workflow for a fully custom consent experience. The add-on costs €10/month per organization on Starter or Pro, subject to applicable checkout taxes. It covers that organization's projects and apps; plan limits still apply.
Work with HTML, CSS, and a small set of template bindings called 1CL (1Consent Language). Edit just the banner in the Dashboard, or work locally with your developer. The browser editor has a supplied starter, HTML/CSS editing, and a real CMP preview. It does not require you to build the preference center. There is no visual drag-and-drop builder.
Themes or custom designs?
| Requirement | Included themes | Custom consent designs add-on |
|---|---|---|
| Colors, typography, spacing, radii, component styling | Theme settings; AI theme generation on Starter and Pro | Can use the same themes |
| Change the notice's HTML structure | Supplied design | Custom structure |
| Rebuild preferences or the reopening button | Supplied design | Custom views |
| Reuse your own components and shared partials | Supplied components | Author and share your own |
| Consent decisions, storage, signals, enforcement | Managed by 1Consent | Still managed by 1Consent |
Configure services, purposes, languages, framework behavior, and disclosures through their existing configuration surfaces. Hiding a control does not change the engine's rules.
Can I customize only the notice?
Yes. Choose a custom banner. You own the first-layer notice; 1Consent supplies the matching official preference center and reopening button. All views use your CMP’s selected theme. The browser editor exposes only Banner HTML and Banner CSS.
Official secondary views are maintained by 1Consent. Each published CMP freezes the reviewed official version alongside your immutable banner release. Eligible clean CMPs follow official updates; unpublished customer changes remain drafts. Pro version pins and Staging keep their existing behavior. A source save never publishes your edits.
A full custom design gives your developer ownership of all views. Existing app-owned full designs retain the advanced browser editor; the CLI and Design Kit also support full designs. The recommended browser experience is the simpler custom banner editor. Existing full designs keep that mode, including designs that contain only a notice. Cloning preserves the original mode; missing secondary files do not opt an existing design into managed views. See your first banner and publication.
Access and limits
An Owner manages the add-on in organization Billing. Owner, Admin, and Privacy Manager can author when access is active. Marketing and Read only can inspect retained designs but cannot edit. Assignment and publishing also require their configuration and publication permissions.
The current 30-day evaluation and 7-day grace period include custom designs without an automatic charge. After evaluation, continued use requires Starter or Pro plus the add-on. Buying a paid plan starts paid billing after checkout confirmation; evaluation does not postpone that purchase.
Stored designs and design collections have separate organization-wide capacities across all scopes: 15 of each on Starter; 25 of each on Pro, plus five of each per additional billable Pro app. Inactive and retained resources count. The add-on does not increase app, framework, language, or publishing-stage allowances. Check current Dashboard usage before creating resources.
Removing the add-on or suspending access retains source files but blocks authoring and custom delivery. The system design serves while custom access is unavailable. Recovery restores eligibility; review assignment and publication status before publishing further changes.
Developer guide
- Your first design: a notice-only change.
- Syntax: text, attributes, conditions, and loops.
- Components: props, children, and shared partials.
- Data and localization: runtime roots and translated content.
- Commands and consent: real runtime actions and controls.
- Styling: themes, Shadow DOM, responsive layouts, and accessibility.
- Local development: Design Kit and customer CLI.
- Publishing: drafts, releases, stages, and access lifecycle.
- Worked examples and troubleshooting.