Configure your Cookifi property

Click on any of your created properties to open its settings. This guide will walk you through configuring your Cookifi property.

General

The General section allows you to access your integration codes and update your property details, such as the name, domain, and sitemap URL.

Cookies

The Cookies section lists all cookies discovered during the scan of your website, categorised accordingly.

While Cookifi automatically assigns cookies to categories, we recommend reviewing them to ensure accuracy. You can modify any incorrect categorisations.

Tip

If your monthly scan has already run but you’ve introduced a new tool that sets cookies (e.g., analytics cookies), you can manually add a cookie by clicking the + icon next to the relevant category.

This opens the following popup, where you can enter the cookie details:

Caution

If Cookifi cannot categorise a cookie, it will be placed in the Uncategorised section. Check back periodically to ensure all cookies are correctly classified.

Members

The Members section lists all Users and Agencies that have access to the property.

You can add an individual user or an agency to your property by clicking the + icon:

To add a user to your property, click the + icon next to Users, enter their email and set the suitable permissions:

Caution

Before adding a user, ensure they already have a registered Cookifi account. At the moment, invitations are not supported, so the user must sign up beforehand.

To add an agency to your property, click the + icon next to Agencies, search for the name of the desired agency, and set the suitable permissions:

Theme

In the Theme section, you can adjust the appearance of the cookie banner, including border radius, background and text colours to match your website design:

A real-time preview is displayed on the left.

To add your logo, click the following button:

Regions

The Regions section allows you to customise cookie banner behaviour based on a visitor’s location. This helps you comply with region-specific privacy laws.

Countries

By default, a Global region is created for your property, applying to all visitors unless a more specific region is added.

When you create a new region, it overrides global settings for visitors from that region.

To create a new region:

1. Click the + icon:

2. Search for a country or region (e.g., EEA - European Economic Area).

3. Click Create.

Once created, click the region’s icon to configure its settings:

Default consent values

In each region settings, you’ll find three cookie categories: Marketing, Preferences, and Analytics:

You can set each category’s default state to either Granted or Denied. These default values apply until a visitor makes a choice. This allows you to treat each region differently based on its privacy laws.

These values directly translate into the Google Consent Mode’s Default command categories and will also apply to any other future integrations.

Note

If you are using Cookifi to manage the Google Consent Mode’s Default command, and you make a change to any of the default consent values above, make sure to re-generate your integration script in General settings and replace the existing script in your website’s code.

Caution

Default consent values are set to denied for new regions by default. Modifying these values may impact tag behaviour and how cookies are set. We strongly recommend consulting your legal team before making adjustments.

Preference centre

The Preference centre is a floating button that allows visitors to easily review or change their consent preferences at any time:

Clicking the Preference centre opens the Cookifi popup:

You can turn the Preference centre on or off, and adjust its position on the page:

Consent user ID

Cookifi can push a consent user ID into the data layer as an event:

This allows you to retrieve the user ID using Google Tag Manager (GTM) and send it to analytics tools. If the tool supports data deletion mechanisms, you can request data removal for that user upon request.

To do this, open your GTM container.

1. Create a Custom Event trigger with the event name: cookifi-consent-user-id:

2. Create a Trigger Group trigger. Add your existing analytics trigger, and the newly created Custom Event trigger:

3. Create a Data Layer variable with the name: cookifiUserId:

4. Add the variable to your analytics tag.

Caution

Using this for Google Analytics 4 (GA4) is not recommended due to Google’s limited data deletion request options. Currently, GA4 only allows deletion requests for registered custom dimensions, but high-cardinality dimensions like consent user ID should not be registered.

---

The following three settings apply to Google Consent Mode (GCM):

GCM - Security storage

Defines whether security-related cookies should be granted or denied by default. It’s recommended to keep this granted.

GCM - Wait for update

Some tags may fire between the Default and Update Consent commands. Since the Default command is typically set to denied, this could cause implementation issues. However, Google tags can handle this using the wait_for_update parameter:

Tip

If you experience unexpected tag behaviour in terms of consent, try increasing the wait time (e.g., to 2000 ms).

GCM - Update command

If you want Cookifi to handle Google Consent Mode’s Update command, keep Send Update Command enabled:

Translations

By default, the Cookifi banner is displayed in English, but you can add translations.

How it works:

When a visitor views your website, Cookifi detects their default language.

1. If a custom (created by an admin) translation exists for the detected language, Cookifi displays it.
2. If a custom translation does not exist for the detected language, a default translation (created by Cookifi) is used.
3. If no translation is available, the default English text is displayed.

Tip

You can also use this feature to customise the banner text and button labels.

Billing

In development