/
Cookie consents

Cookie consents

Purpose

The way the mobility web asks for cookie consents should be configured to comply the requirements for the current market.

Configuration

Disable cookie consents

  • In markets where this is allowed and expected, BRP staff can disable “Enable cookie consent“ (default true) on the app object.

Configure the cookie consent modal

If you use tools such as Facebook Meta Pixel or Google Ads/AdSense via a tag manager to track user data, consumers are required to provide marketing consent before any tracking occurs, as required by privacy laws.

This update introduces a configurable solution that enables customers to control marketing,preferences and statistics cookies via the Back Office and present the relevant cookies to end users.

1. Enable Marketing & Preferences Sections

By enabling the `enableCookieConfiguration` setting from the back office configuration

  • The Marketing and Preferences sections will be displayed to end users in the cookie consent modal.

  • End users will be able to provide consent for these categories directly from the modal.

image-20260331-114647.png

 

2. Cookie Configuration for the Application

  • If the setting is enabled but no cookies are configured in Configuration.

    • The Marketing and Preferences sections will display a placeholder message (for example: “We do not use cookies of this type”).

    • The Statistics section will display mandatory cookies related to Google Analytics.

image-20260331-114718.png

 

 

  • Marketing cookies are not added by default, as not all customers use marketing tools. Customers must explicitly configure them via the Back Office Configuration.

Configuring Cookies

  • After enabling the `enableCookieConfiguration` setting, a new section called Cookie Definitions will be available in the Back Office Configuration → Web and App section.

    image-20260331-114756.png

  • By default, this section includes a set of commonly used cookies for Facebook Meta Pixel and Google AdSense. These cookies can be filtered by category (Marketing, Statistics, Preferences) and by tracking tool. Currently, only these two tools are available, as they cover the majority of customer use cases.

  • If customers use additional tracking tools that are not supported by default, or if they need to define extra cookies, they can manually add them as additional cookies via the Back Office. Additional cookies can be assigned to any category as needed.

    • To add a new cookie, click the “+” icon and provide the following details:

  • Name – Cookie name

  • Category – Marketing / Statistics / Preferences

  • Tracking Tool – Optional (select if the cookie belongs to a listed tool)

  • Expiration – Duration of the cookie

  • Time Unit – Years / Months / Minutes

  • Provider – Cookie provider

  • Description – Description of the cookie

image-20260331-114837.png

 

 

  • Once the cookies are defined, they must be assigned to the application:

Go to Back Office Configuration → Apps → Select App → Cookie definition

image-20260331-114907.png

 

 

  • Move the cookies you want to display in the cookie consent modal from the left panel to the right panel and save the changes.

image-20260331-114931.png

 

  • Then, the cookies you have configured will be displayed under their respective categories in the cookie consent modal.

image-20260331-114959.png

 

 

Currently, there are no cookies configured for the Preferences section. However, this section is designed to support cookies in the future if needed. (like https://www.brpsystems.com/ cookie consent modal)