Boros CMP is a stand alone Consent Management Provider solution compliant with the "Transparency & Consent Framework" standard established by the IAB Europe.
Boros CMP is registered with ID 129
- Open Source project
- Supports the IAB specification
- Supports consent management for a single site or multiple sites from a single brand
- Stand alone project (without User Interface). We also developed a User Interface and a bundle project including UI + CMP
- Have a look at our CMP Showcase and try Boros
- Importable as a library from NPM.
- Developed in Javascript (ECMAScript 6) using Promises and Events
- We ❤️ Domain Driven Design
- Supports local storage using single site cookie
- Supports global storage using multi site cookie via iFrames
Boros CMP is available as npm package named @schibstedspain/boros-cmp.
To install the last stable version:
npm install --save @schibstedspain/boros-cmpTo initialize Boros CMP using default configuration values:
import boroscmp from '@schibstedspain/boros-cmp'
boroscmp.init()
.then(()=>{
// do your stuff ...
})To initialize Boros CMP using customized configuration values:
import boroscmp from '@schibstedspain/boros-cmp'
const customConfig = {
gdpr: {
gdprApplies: true,
storeConsentGlobally: false
},
consent: {
consentScreen: 1,
consentLanguage: 'es'
}
}
boroscmp.init({config: customConfig})
.then(()=>{
// do your stuff ...
})Notice that init method is returning a Promise but you can subscribe to cmpReady event instead:
import boroscmp from '@schibstedspain/boros-cmp'
window.document.addEventListener("cmpReady", (event) => {
// do your stuff ...
// like calling window.__cmp( ...
})
boroscmp.init()You could also import directly the library instead the bundled version. By using this, it will assume you're providing the @babel/runtime dependency, helpers and polyfills needed to get it working but it will give you a better size by reusing your packages.
import boroscmp from '@schibstedspain/boros-cmp/lib'
boroscmp.init()
.then(()=>{
// do your stuff ...
})There are some default configuration values that can be overwritten before CMP is loaded. Following you will find all the configuration properties and their default values.
| Property | Description | Default Value |
|---|---|---|
| gdpr.gdprApplies | Defines if GDPR applies or not. | true |
| gdpr.storeConsentGlobally | Defines if Consent Storage is Global (true) or Local (false). | false |
| gdpr.globalConsentLocation | The source URL of global storage html. | |
| consent.consentScreen | Screen number where consent was given. | 1 |
| consent.consentLanguage | Defines the language for the UI. | es |
| vendorList.host | Host URL to retrieve Vendor lists. | https://vendorlist.consensu.org |
| log.level | Defines the Log level. | 3 |
Defines if GDPR applies or not.
Defines if Consent Storage is Global (true) or Local (false).
The source URL of global storage html.
Defines the Screen number in the CMP where consent was given. The screen number is CMP and CmpVersion specific, and is for logging proof of consent
This language will be used by the User interface using CMP. Language values are ISO 639-1 (2 letter codes). By default, es will be used.
Check the available translations here: https://register.consensu.org/Translation
To find Vendor lists, CMP tries to retrieve a JSON named vendorlist.json and uses the IAB version structure, as follows:
- Latest Vendor list: https://vendorlist.consensu.org/vendorlist.json
- Specific Vendor list version: https://vendorlist.consensu.org/v-${vendorListVersion}/vendorlist.json
- where ${vendorListVersion} is the specific version to retrieve. For example: https://vendorlist.consensu.org/v-2/vendorlist.json
Available log level values:
| Code | Level |
|---|---|
| 1 | debug |
| 2 | info |
| 3 | warn |
| 4 | error |
| 5 | off |
CMP version is set according to the version defined inside the package.json file. IAB standard uses only one number to define this version, so only the major version (first digit) will be used.
CMP is MIT licensed.