No, the Consent Raiser is not a CMP and is not meant to replace it. It is an addition to the CMP, it works with it.
The Consent Raiser is only displayed after the user has declined consent on the CMP.
The goal: convince these users to change their mind and accept consent in exchange for a donation to the charity of their choice.

Gimii’s Consent Raiser is compatible with all the CMPs.
By default, we rely on the “consent string” to determine whether to display the Consent Raiser. So if your CMP supports the TCF (Transparency and Consent Framework), it will work seamlessly. If you are using an in-house CMP that does not support the TCF, we just need to access to the user’s consent status to determine whether to show the Consent Raiser.

We presented Gimii to CNIL France, and they did not question its legality.
As of now, there is no official CNIL certification for tech solutions, only for DPOs (Data Protection Officer) or organizations. Until such certification exists, we had an “e-privacy/GDPR” audit conducted by a certified DPO who worked for 8 years at CNIL France.
The Consent Raiser complies with all major GDPR principles:

• A visible “Refuse” button is always present, refusal is simple (one click) and free, making consent freely given.

• We do not use any personal data.

• No cookies or trackers are dropped until the user gives consent.

• The Consent Raiser appears just after the CMP or after a delay. If a delay is set, we display the CMP immediately after the Consent Raiser, ensuring the user has seen the mandatory legal text, making consent informed.

• Users can also re-open the CMP via the “cookie preferences” link on the Consent Raiser to review and change their consent choices.

• Display delays are customizable to avoid “consent fatigue” and maintain freely given consent.

• Our solution follows the principle of data minimization: we only track necessary interactions (displays, acceptances, refusals, and charity choices). We rely on client ad server data for revenue tracking, no trackers used on our end.

Gimii’s script simply checks the consent string. If the user refuses any vendors or purposes related to personalized ads, we display the Consent Raiser.
For example, if the ad server is Google Ad Manager, we refer to Google’s vendors and purposes list here. This behavior can be customized depending on which vendors/purposes you want to track.

Everything is customizable: display type (pop-in, footer, foldable footer), display delays, background color, button colors and shapes, font, text color, logo…
The goal is to make a tailor-made experience that fits seamlessly into your site’s design.

The Consent Raiser works:

• On desktop, mobile and tablet,

• On web: a script in your site’s header,

• On mobile apps (iOS & Android): an SDK to integrate.

The Consent Raiser is responsive and adapts to all screen sizes.

Currently: French, English, German, Spanish, Italian, and Dutch.
The script automatically detects the user’s browser language and displays the Consent Raiser in the same language. Need another language? We can add it quickly.

While some “re-consent” mechanisms are displaying a footer without a “refuse” button, and some argue it’s not mandatory since it doesn’t block the browsing, Gimii recommends to always include a “refuse” button to respect CNIL guidelines and legal texts. However, the final decision is up to each client and their legal team, so yes it is possible but we don’t recommend it.

Each client chooses the charities and how many to display.
You can choose from our list of 120+ partner charities or suggest your own, we will integrate them for sure.
We recommend showing 5 to 10 charities in the slider to offer enough choices without diluting too much the donations. Order in the slider is random by default but can be set manually.

When a user consents on Gimii, we trigger the CMP’s JavaScript function to opt-in all vendors and purposes, it is exactly the same as clicking on “Accept all” on the CMP. This can be customized to only opt-in certain vendors or purposes (e.g., just the ones related to personalized ads).

If the user refuses on Gimii, we do not change the consent string; we simply close the Consent Raiser. All CMP choices remain unchanged.
Example: if the user clicks on “Refuse all” on the CMP and then refuses on Gimii, we keep all the vendors and purposes as opt-out. If the user only opt-out some vendors and purposes on the CMP and then refuses on Gimii, we keep the exact same vendors and purposes as opt-out.

Yes, you can also display Gimii to users who haven’t made a choice (first visit or cleared cookies).

The law doesn’t explicitly forbid it. Although it is important to not be too insistant. That’s why we propose customizable delays to display the Consent Raiser to ensure consent remains freely given and to avoid too much “consent fatigue”.
Note: CNIL allowed the “Continue without accepting” link instead of the “refuse” button in CMPs precisely to allow occasional consent prompts after the refusal.

We recommend:

1. Displaying Gimii right after the CMP refusal for better clarity.

2. Re-prompt it every 15 days if the user refuses on Gimii.

CNIL suggests at least 10 days between re-prompts.

Two cases:

1. If Gimii is displayed right after the CMP, re-prompting the CMP isn’t necessary.

2. If there is a longer delay (over a week), it might be necessary to re-prompt the CMP to refresh user memory. The re-prompt of the CMP right after Gimii can be configured.

Moreover, a “Cookie preferences” link on the Gimii pop-in lets users re-open the CMP to change their consent choices.

No. We use a reminder pop-in shortly before the 6-month mark to inform users of the donations collected and ask if they want to keep their consent for another 6 months. With this reminder mechanism, we manage to keep the consents for a very long period of time.

This estimate is based on the French average consent rate (~59%). If your current rate is higher, gains may be smaller. Conversely, if it’s lower, you could get back more than 15 points of consent. Some of our customers reach around 90–95% of consent rate, above it is very difficult because it tends to be users who are strongly anti-tracking and anti-advertising.

Currently, Gimii helps recover between 0.8 to 1.5 points of consent per month. So it takes typically around 12 to 18 months to gain back 15 points.

Integration is simple, with no changes needed to your CMP or ad tags. You just need to add the Gimii script to your site header (it works on Google Tag Manager too).
Here are the major steps for the intergation:

1. Define your Consent Raiser settings (display type, delays, colors, logo, charities, etc…),

2. Add the script to the header of your site,

3. Set up a daily report from your ad server to track revenue from users who consented on Gimii.

Yes, an admin platform is provided to our customers to:

1. Access reports and view data:

   • Consent Raiser displays

   • Acceptances (=consents)

   • Refusals

   • Revenue generated

   • Donations per charity

   • Impacts (meals provided, trees planted, corals restored, etc…)

   • Sustainable development goals

2. Modify the Consent Raiser settings:

   • Display type

   • Colors

   • Font

   • Delays

   • Charities

Legally, it’s forbidden to offer users a direct and concrete benefit for their consent or a disadvantage for refusing. In Gimii’s case, it is the site which donates to a charity, not the user. The user does not gain anything directly (no tax benefit, no personal reward). By contrast, “paywalls” (which are legal) require users to pay if they refuse consent, that’s a clear disadvantage. Gimii is free and balanced: the user can consent or refuse freely. Additionally, a “Refuse” button is always present and equal in size than the “Accept” button.

Moreover, the majority of CMP pop-ins already influence users via design (“Accept” button with a more visible color, a small link “Continue without accepting” etc…) and wording (“support independant journalism”, “for a better experience”…), which is tolerated by CNIL.
Gimii operates in a similar, yet a more ethical way.

Gimii is registered as Crowdfunding Intermediary with ORIAS, allowing us to handle donations on behalf of our customers. But donations are legally made by the client, and Gimii only acts as intermediary. Clients receive a monthly invoice (no VAT for donations) based on ad revenues with the total amount of donations collected, and then we pay each charity. At year’s end, we provide tax receipts per charity so you can get tax reductions (in France, 60% of the donation amount is tax-deductible) as it is considered as corporate philanthropy.

Yes 100% transparent as it is based on client’s ad server data.
Example: if a user accepts on Gimii, then generates €1 in ad revenue during his visit, and chose the charity WeForest, Gimii will send an invoice for €0.10 (10% of the ad revenue) and then donate it to WeForest. Clients can verify this amount directly in their ad server or on Gimii admin platform.
Users are kept informed through:

• Our corporate site (CHARITIES page),

• Social media,

• Newsletters,

• Reminder pop-ins directly on the customer’s website.

Yes, it can.
We’re currently developing a prototype for preference pop-ins shown when users create accounts. With some development, the Gimii mechanism can be adapted to any opt-in flow.