Cookiebot Subpage redirect issue

Jan Vanfraeyenhoven

• March 04, 2021 17:07

Hi, 

We are launching a marketing campaign on different audiences. 

we are also using different landingpages for each audience. 

So let's say 20-30 yr old visit test.com/20-30

40-50yr old visit test.com/40-50

The problem is that whenever someone enters a specific landingpage, accepts cookieconsent, the consent redirects to another page. 

So main domain = test.com

subpages = test.com/20-30 
                    test.com/40-50

someone visits test.com/20-30 -> Clicks consent 
--> Redirects to test.com 

 

How can i change this so that if someone enters a subpage, clicks consent & stays on that specific page? 

(we used Wix)

Thanks in advance

1

• Official comment

  

  Brian Mørkeberg Lundkvist

  • May 17, 2021 09:57

  Hi All

  Please do reach out to our support team with concrete examples of this and we will make it a priority to look into this. 
• 

  Wiliam

  • March 22, 2021 14:21

  Good

  0
• 

  Mark

  • April 09, 2021 09:55

  Did you manage to find a solution for this issue? We're experiencing the same issue with a manual (tag manager) Cookiebot implementation on our Wix site. The auto-blocking implementation does not have this issue but causes other undesirable results such as preventing the Wix language menu from working.

  0
• 

  ainsley2021

  • May 03, 2021 19:10

  I am facing the same issue, if you receive the solution kindly mention it here so others can take benefit.

  0
• 

  Ian

  • May 12, 2021 19:10

  Did anyone find a solution to this? As soon as anyone clicks on the 'accept' button on my site, it always redirects to the homepage, rather than staying on the page that the user has entered. I want to do some marketing with links to a specific 'lead' page on my Wix site, but this screws that up completely. 

  0
• 

  Lorenzo Bonzi 97

  • February 14, 2022 19:53

  Hi Guys, if it can help I had the chance to finally Solve this via Cookiebot support.

  You can insert this piece of code in Wix Website inside the custom code section.

  You should put this in the header and need to possibly activate all times ( or maybe just one time, not sure 100% about this), that's the setting I'm using right now and they seem to work.

  Here is the precious code:

  window.addEventListener('DOMContentLoaded', () => {
    let d = document,
        a = d.getElementsByTagName('a');
  
    for (var i of a)
      if (i.getAttribute('href') === '#')
        i.addEventListener('click', e => {
          e.preventDefault();
        });
  })

  Hope this can be helpful to others as it is for me, as I took a lot to actually find an answer :D 

  Enjoy!

  Lorenzo

  0

Please sign in to leave a comment.