The Cookie Consent component is a global system component in headful.
It applies project-wide and is displayed on all pages.
The functionality is intentionally reduced:
Tracking is either allowed or blocked.
There are no consent categories.
There is no granular script control.
There is no automatic logging or documentation.
The component is suitable for simple setups with basic tracking approval.
How It Works
When a page loads, the system checks:
Consent granted → Tracking scripts are loaded.
Consent denied → Tracking scripts are blocked.
The effect is global across the entire project.
Design Customization of the Native Cookie Consent Component
The native Cookie Consent component provides basic customization options.
Color Scheme
One of the color schemes created within the project can be applied.
The visual appearance follows the selected color scheme.
Individual design adjustments outside the selected color scheme are not supported.
Text Customization
The title can be defined individually.
The description text can be edited using the Rich Text Editor.
This allows alignment with brand language or legal requirements.
Structural or functional extensions are not possible.
When an External Consent Tool Is Recommended
An external tool is required if the following features are needed:
Multiple consent categories (e.g., statistics, marketing, preferences)
Legally compliant logging
Automatic cookie scanning
Geographic differentiation
Advanced consent logic
Suitable providers include:
Step-by-Step Guide for Integrating an External Cookie Tool
Preparation with the Provider
Create an account with Cookiebot or iubenda.
Set up a domain or project.
Copy the generated script (embed code).
Integration in headful
Open the Company Dashboard.
Go to Projects.
Open the three-dot menu
of the desired project.Select Edit.
Navigate to Settings.
Open Custom Code.
Activate the Upper Window toggle.
Paste the generated script into the Head field.
Save the changes.
After saving, it may take a short time for the update to become active.
The external tool will then load globally across all pages of the project.Schritt-für-Schritt-Anleitung für Integration eines externen Cookie-Tools
After saving, it may take a short time for the update to become active.
The external tool will then load globally across all pages of the project.
Design in External Consent Tools
For external providers, design configuration is handled:
Directly within the provider’s dashboard.
Through the available design and layout settings.
Optionally via additional CSS configuration provided by the tool.
The design is not controlled through the headful color scheme.
System Dependencies
The script is embedded in the project’s Head section.
The integration applies project-wide.
Only one consent system should be active at a time.
Changes may appear delayed due to caching.
Tips & Tricks
Use only one consent system at a time.
Test the setup in an incognito window after integration.
Verify tracking behavior for both consent states.
Allow a short waiting period after changes.
FAQ
Does the Cookie Consent component apply to only one page?
Does the Cookie Consent component apply to only one page?
No. It applies to the entire project.
Can I create consent categories within the native component?
Can I create consent categories within the native component?
No. Only basic allow or block functionality is available.
Where is the external script inserted?
Where is the external script inserted?
Company Dashboard → Projects → Edit → Settings → Custom Code → Upper Window → Head section.