Cookies
Cookies are small pieces of data stored in the user’s browser that help websites function correctly, measure performance, and comply with legal requirements.
What are cookies?
Section titled “What are cookies?”Cookies are small text files that a website stores on a user’s device when they visit it.
They are commonly used to:
- ensure basic website functionality
- remember user preferences
- collect analytics and performance data
- comply with privacy and consent regulations (GDPR, ePrivacy, etc.)
Depending on their purpose, cookies can be essential, functional, analytics, or marketing-related.
Cookies at Terra
Section titled “Cookies at Terra”At Terra, cookies are always implemented through a cookie management platform and never manually.
Currently, Terra supports two cookie management solutions:
A widely used consent management platform with strong GDPR support and automatic cookie scanning.
A lightweight and flexible cookie consent solution, often used in simpler setups or specific client requirements.
Scenarios of working with cookies
Section titled “Scenarios of working with cookies”Depending on the project and the client, cookies can be implemented in two different ways:
01: Client provides the script
Section titled “01: Client provides the script”- The client provides the Cookiebot or CookieYes script
- Terra only defines or shares styling guidelines (colors, branding)
- The script is added to the project header
- No direct access to the cookie platform is required
This option is common when the client manages cookies centrally across multiple projects.
02: Full platform access
Section titled “02: Full platform access”- The client provides full access to the Cookiebot or CookieYes platform
- Terra retrieves the script directly from the platform
- The team configures and styles the cookie banner completely
- Consent setup and visual customization are fully managed by Terra
This option offers more flexibility and control over the cookie experience.
Cookie setup workflow
Section titled “Cookie setup workflow”Regardless of whether the project uses Cookiebot or CookieYes or the case scenarios, the general setup workflow is the same.
01. Create the cookie configuration and add the domain
Section titled “01. Create the cookie configuration and add the domain”- Add the project domain to the cookie platform (Cookiebot or CookieYes)
- Select the applicable regulations (GDPR, ePrivacy, etc.)
- Treat stage and production as separate domains
Don’t forget
To test the cookie configuration and banner, always work in the stage environment first.
When a project is launched, don’t forget to update the domain to the production URL.
02. Configure banner and cookie categories
Section titled “02. Configure banner and cookie categories”- Configure cookie categories:
- necessary
- functional
- analytics
- marketing
- Define banner behavior (position, interaction, default state)
- Update banner text and links (e.g. Privacy Policy)
03. Implement the cookie script via GTM
Section titled “03. Implement the cookie script via GTM”- The cookie script must always be implemented via Google Tag Manager (GTM).
- Never hardcode the script directly in the project
- All third-party scripts must respect the selected consent categories
Using GTM ensures consistent behavior and proper consent handling across environments.
4. Test and verify consent behavior
Section titled “4. Test and verify consent behavior”After implementation, always verify that:
- the banner is displayed correctly
- non-essential cookies are blocked before consent
- cookies are enabled only after the user accepts
- consent is stored and persists across page loads
Knowledge Check
Test your understanding of this section
Loading questions...