Integrations
      Back to home
      1. Help Center
      2. Integrations

      Integrate with Cookie Consent Management Platforms (CookieConsent.io)

      No personal data is used or stored in Convert Experiences if you use the default settings.

       

      Introduction

      To comply with the GDPR and ePrivacy Convert's EU customers as well as non-EU customers processing personal data of visitors from EU/EEA have to respect the user's choice with respect to cookie tracking. This means that the website owner needs the ability to control when a cookie-setting script is executed on the website.

      This is required as the GDPR and ePrivacy state that the website owner is required to block cookie-setting script until they have collected consent from the user.

      Compliant use of cookie tracking can be achieved by first executing cookie setting scripts after the user has given their consent.

       

      How GDPR & ePrivacy influence tracking

      Under GDPR and ePrivacy, you need to notify your customers about what personal data you are processing through a privacy notice and also need to collect consent for processing this personal data. You can collect consent by using one of the Cookie Consent Management Platforms (CMP) (Cookiebot, OneTrust, CookieConsent, CookieInformation, UniConsent, ConsentManager, Civic Cookie Control) for tracking the visitor by adding a “tracking consent” notice on your webpages. This notice should contain a button that the visitor can click to give their consent.

      From a user perspective, a CMP is a tool that enables the pop-up boxes on many of the websites you visit. For each visit, the CMP asks for the user’s consent to data collection and cookie placement. Upon the consent selection by the user, the CMP is then providing an indicator that can be used to conditionally execute (fire) tags – resulting in cookie placement and data collection. 

      The style of pop-up box displayed, language used for consent, and granularity of options will depend upon the use and configuration of the CMP. By optimizing the combination of these factors, an organization can maximize the proportion of consenting users (allowing you to collect data about their behavior and place cookies for advertising). This is referred to as Consent Rate Optimization.

      One common complaint about CMPs is that there is no native functionality within the platforms to test the user behavior when presented with various options for banner configuration. For example – do more users accept consent when presented with a small banner at the top of a webpage, or when presented with a full-screen message?

       

      Integrate Convert with CMP 

      To address this deficiency, we are presenting below a custom configuration of A/B testing using CookieConsent.io banner deployed through Convert. With this configuration, you will be able to answer the following questions:

      1. How many users arrived on the website? Which consent option were they presented with, and did they consent or not?
      2. How many users consented or rejected with each consent type?
      3. What is the potential traffic loss or visibility loss from users that don’t consent with each consent type?
      4. How are other top-line metrics such as pageviews, bounce rate, etc. impacted by the consent experience?
      5. What is the percentage of Consent Rate Optimization?

      For the sake of this article we are going to use CookieConsent.io as the CMP and describe how this is feasible with Convert.

       

      Step 1 - Create a CMP account and add your domain

      Request a demo to create a CookieConsent.io account. Once you have a plan with them, log in to your account and add your website domain name(s). Save. The website will now be scanned (please allow up to 24 hours for the scan to complete).

       

      Step 2 - Build your own cookie consent banner exactly the way you want it

      With a Pro subscription you can easily style the banner. To change the layout, you can add the CSS below to your style sheets. These are of course examples and can be adjusted as you see fit.

       

      Step 3 - Insert the CookieConsent.io scripts on your website 

      You can add the CookieConsent.io consent popup by adding the script below between the <head> html tags. Replace the 000000000000-0000-0000-0000-000000000000 with the ID provided to you in the support e-mail.

      <script type="text/javascript" src="https://edge.cookieconsent.io/prod/js/000000000000-0000-0000-0000-000000000000.js&hidden=false&backdrop=false&position=center&marketing=false&analytics=true&google_consent_mode=true"></script>

      You can configure certain options by adding query parameters to the source file. These options override the default value entered in the manager. 

       

      Step 4 - Insert the Convert script on your website 

      Use these instructions to install the Convert tag on your site.

       

      Step 5 - Create an A/B Experience to modify consent banner design

      Next you need to setup an A/B experience through your Convert account.

      In the variation, either by using the Visual Editor or the Custom HTML/JS/CSS editors you will be able to change the design of the consent banner. 

      You may test any variable that may impact the "conversion rate" for accepting cookies, including:

      • Presentation (popup/lightbox vs accordion)
      • Copy (tone, length, motivators / value props for accepting cookies, headline)
      • Calls to action (label, size, style, color, placement)
      • Point-of-action assurance (copy, motivators)

      To change the colors:

      1. You can change the colors by clicking on any element of the banner and then use the CSS Editor.
      2. Choose the color you like – either by clicking anywhere on the color palette or by entering a HEX code.
      3. Click ‘Save changes’ to apply the chosen color.
      4. Preview the styling to see what it would look like on your website 
      5. If you are happy with the styling, save and continue.

      To customize or add a logo:

      1. Decide if you want to display a logo on the cookie consent banner or not
      2. Use your own logo. Use an image/logo from the internet or select a file to upload
      3. Save your changes

      To change the consent options:

      1. Decide which are the words you would like to use for Consent/Agree - No Consent/Disagree by following GDPR principles for consent
      2. Preview the styling to see what it would look like on your website 
      3. If you are happy with the styling, save and continue.

       

      Step 6 - Define your goals and what you want to measure

      You can now define your own goals and what you want to measure.

      For example you can measure how many visitors clicked on the "I Accept" option of the consent banner while you changed its color.

      You can also add goals to measure which visitors have consented to all cookies and which of them have consented only to Necessary. This can be done by using the Advanced Goal Editor and add your own JS conditions there.

       

      Step 7 - Run the A/B Experience 

      Once you are ready with all changes you can activate the experience and wait for the results. Use our A/B Testing Statistical Calculator to answer all your pre- and post-analysis questions.

      Below for example the hypothesis was that uniformizing the colors would not change users' behavior, but it ended up doing so. We observed a statistically significant dip of -9%, at a 99% confidence level and a power of 72%. 

       

      Step 8 - Exclude Visitors who selected No Consent

      In the above A/B experience you need also to take care of visitors who selected No on the cookie consent banner and accepted only the Strictly Necessary cookies. In such case there are some challenges:

      • Allowing experience users to opt out of testing and analytics cookies means no tracking after the conversion event (in this case opt in, out or abandonment)
      • If users opt out, you are expected to honor their request forever. Allowing them to opt out before you absolutely have to ask means losing out on data and disabling site features that could improve conversion rates
      • If running a cookie permission test concurrently with other tests, it's not guaranteed the tests will play nicely together.
      • This type of test may have a short half-life, meaning that consumer behavior is expected to change over time. As people get used to encountering permission requests, they are likely to become more tolerant, and respond to prompts differently than today.

      CookieConsent.io has a function called "cookieconsent_necessary" which you can use and disable this single A/B experience for non consented users by using the parameter "_conv_eignore". For example once a visitor navigates to your page and select the No option on cookie consent banner you can have this:

      http://www.convert.com/page1.html?_conv_eignore=experienceID

      This would disable any variations showing and collecting any experiment data.

       

      Conclusion

      In the new privacy environment, consent is in many cases a requirement. It is important to start looking at user consent as the first conversion point and looking critically at the user experience driving consent in this manner. Employing strategies such as A/B testing on the consent experience will lead to an optimization of the proportion of consenting users for whom you can collect data and use in audience creation – giving your business a competitive advantage over your competition. This is how you can achieve your website's Consent Rate Optimization.