Cookies Consent and Mida's Adherence

Created by LiRou C, Modified on Fri, 9 Aug at 4:29 AM by LiRou C

Under data protection rules like GDPR, you may need to ask visitors for permission before using cookies or trackers to gather their information. One way to do this is by showing a cookie banner, telling visitors about cookies and getting their consent to be tracked.


Mida follows these rules and doesn't gather sensitive details. However, the decision to implement Mida with cookie consent or not is entirely up to you.


To find the best fit, seek guidance from your legal team on complying with data privacy laws in your operating countries. Now, let's see the different ways you can set up Mida.



1. Standard Mida Implementation (without cookie consent banner)


With this setup, you can run the Mida script without asking visitors for permission first. This means you can start using cookies or trackers to collect visitor data as soon as they arrive on your website.


If you're considering this approach, simply follow the standard Mida installation guides here to implement Mida on your website. 



2. Mida Implementation with a Cookie Consent Manager


To comply with data protection policies in your operating countries, you need visitor consent before using cookies or trackers to gather visitor data. For this, you may be using third-party consent management tools like OneTrust, Usercentrics, etc.


With Mida, you can conduct A/B testing directly on your website without needing user consent. 


Here's how it works:

  1. Test variants are shown to new visitors before they decide on the cookie banner.
  2. No cookies or trackers are deployed until visitors opt to accept the cookie banner.
  3. If consent isn't given, visitor information and test results aren't collected thus not included in Mida reports.
  4. When consent is given, user data is sent to the Mida server for generating live reports.


This method ensures your users can access the website seamlessly, without any disruption to their experience (like the flicker effect caused by switching between different designs, such as one with a white background and another with a black background).


More importantly, no personally identifiable information or personalized segment data is collected. By adopting this approach, you ensure compliance with data protection regulations while leveraging Mida's A/B testing capabilities seamlessly and responsibly.


For effective implementation of this approach, Mida scripts should be placed before your Cookie Consent Manager script or as high as possible in the HEAD section.


Here's how to implement this approach:


Step 1: Add a new 'cookie=1' parameter to your Mida script. For example: 


This will prevent Mida from collecting test variant data and persisted variant on returning visits while still serving temporary variant. 


Step 2: Execute the following code when cookie consent is accepted or declined through GTM or your Consent Management Tools:

// to accept consent
mida.grantConsent(true)

// to decline consent
mida.grantConsent(false)

This will give Mida permission to send data back to the Mida server for reporting and persistent user experience purposes.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article