Ezoic did not recognize Consent since IAB wit Borlabs Cookie 3.0

fniesen

Hi,
Since I changed my Wordpress site to a new theme and Borlabs Cookie 3.0, because of the TCF 2.2 integration, Ezoinc does not always recognise the consent. Or could this also be related to Leap? To be on the safe side, I have put the Borlabs Javascripts on every exception list I have found.
Any ideas?

Regards Fabian

Ethan

fniesen Hey, you do need to follow a couple of steps so Borlabs Cookie works effectively with Ezoic: https://support.ezoic.com/kb/article/how-do-i-connect-borlabs-cookie-with-ezoic

If you already followed the guide and are having issues let us know and we'll take another look for you.

fniesen

I Ethan,
I know this article, but that did not help always. Also, 3.0 is completely rewritten from scratch, so expect there are some issues with that. Seehttps://borlabs.io/borlabs-cookie-3-0/

Ethan

fniesen Got it, thanks for clarifying. Can you provide a little more detail on how Ezoic isn't respecting/recognising the consent? For example, is it that ads show regardless of the consent option selected, or that ads don't show after clicking any of the cookie options?

I am currently facing issues accessing the site and received a Cloudflare time out error. This seems to be a http error, are you using any SSL technologies outside Ezoic?

fniesen

Sometimes it takes several clicks/pages after the consent until Ezoic ads are shown. I also see that the earnings have dropped since the migration to the new platform with IAB TCF integrated Borlabs.
I have enabled Ezoinc, Google and my affiliate Partners in Borlabs.

fniesen

Regarding the errors, no that is still the Ezoic Leap cache crawler overloading the webserver. That is also the reason why I had asked if there is a limitation setting for the cache mode. The crawler utilizes the 2 CPU cores for my hosting up to the max possible value from 800% util.
But on the hosting side, I only could block the crawler in total, not limit him.

Ethan

fniesen We don't have an option to limit the setting for the cache mode, no. You could try disabling Ezoic caching entirely. It seems possible the caching/timeout error and the cookie consent taking a while to be recognised are interrelated issues. If you still have issues with the consent modal once the timeout issue is fixed let us know and we'll look into it with the privacy team.