pressidium

Hey, @nikodemsky!

Maybe the issue is that it looks for simplfied codes like:
de
instead of iso codes:
de-DE
?

Within the plugin’s UI, you’ll find different language options. Opting for German will attempt to detect de, while German (Germany) will try to detect de-DE, German (Austria) will result in de-AT, and so forth.

Double-check that the languages you’ve selected are consistent with the settings of your translation plugin, such as WPML, Polylang, or similar plugins.

If this doesn’t resolve your issue, please let us know and provide a link to a website where the problem can be reproduced, if it’s possible.

Just the usual ones for GA, GTM, Google Ads, facebook, and linkedin – i think those are most commonly used and would save a lot of future questions about “how to do it” from new users.

Ah, now I get it! Having some preset options for commonly used regular expressions could significantly streamline the cookie consent setup — opened this in #58.

Sure, i mean this one:

wp1

The text you’re seeing isn’t from our plugin. Based on a quick search, it seems to originate from another plugin (Backup Migration). Check if that plugin is installed on the affected website.

Still it’s kinda too close – remember that misclicks are not exclusively limited to just one click ?? Thing is that once you will delete those logs they are gone for good, if someone didn’t made a backup.

Opened this in #59 to take a look in a future iteration of the plugin, just to be safe.

Hey, @nikodemsky!

We’re pleased to hear that you find our plugin valuable and intend to use it for your projects, going the extra mile to localize it for Polish users.

I’ll do my best to address all your questions and suggestions:

data-cc=”c-settings” doesn’t really do anything, it’s from wiki so i thought it should work – i need to append pressidiumCookieConsent.showSettings() to element anyway, so it kinda defeats the idea of inline attribute

I think you’re trying to open the settings modal by clicking on an element that’s outside of the consent modal. The data-cc="c-settings" attribute only works when added to a link or button that’s inside the consent modal. For example, you could append <button type="button" data-cc="c-settings" class="cc-link">Cookie Settings</button> to your consent modal’s description.

For elements outside of the consent modal, you’ll have to call the pressidiumCookieConsent.showSettings() method, like you mentioned.

The wording in the documentation could be improved. I just updated the wiki to clarify the distinction.

Possibility to translate Cookie descriptions/expiration dates.

That’s a great suggestion! I just opened this as an issue on the plugin’s GitHub repository. You can stay up-to-date on the progress of that feature, by checking #54.

Cookie categories should hide if there’s no cookies inside – not all the websites using targeting or preference cookies

That’s a valid point. I just opened this as an issue as well. Tracking in #55.

Floating button as mentioned in #24

This is already on our radar. We’re tracking its progress in #24, like you mentioned. It’ll be included in a future iteration.

Add default regex definitions in Blocked Scripts tab instructions, it’s kinda pain to copy them everytime

What kind of regular expressions do you have in mind? Could you provide any examples of default regex definitions you have to copy frequently?

Add textarea for ALL category descriptions with autop(auto break-line) in admin area

This could also be a nice QoL improvement. Opened this in #56.

Simple percentage statistic for accepted/denied in consent records would be nice – no need for for any kind of UI, jus raw data.

Do you think any kind of filtering/categorization would benefit those stats?

Something like:

• Percentage per region
• Percentage per category
• Filtering a specific date range
• etc.

Opened this in #57 — since this is somewhat technical, we could continue the discussion there, if that’s okay with you.

“Stay on the safe side” banner”(or block?) is messed up, hides too much to the left in footer.

I’m sorry, I’m not entirely clear on what you’re referring to with “Stay on the safe side banner”. Could you please provide additional context?

“Clear records” is WAY too close to “Export to CSV”, it’s too easy here for misclick.

I believe misclicks aren’t particularly risky as there’s a confirmation dialog before any records are cleared.

Were you aware of the confirmation dialog? Despite having a confirmation, do you think it’s still an issue?

I’ll keep this topic open, and I’ll regularly provide updates as we tackle the various GitHub issues.

In the meantime, if you come across any other issues, feel free to create a new topic or open an issue on GitHub.

Hey, @ashishtiwari27!

This topic has gotten too broad. To ensure clarity and effective issue tracking, it’s preferred to create a new topic for each distinct concern. This helps us maintain clear and focused discussions, and makes it easier for future users to find the relevant topic.

Can I continue using this plugin without any glitches – I mean without any loss (ad revenue) or penalties imposed by Google.

According to the New Google consent management requirements for serving ads in the EEA and UK:

Beginning January 16, 2024, if a partner does not adopt a Google-certified CMP, no ads will be eligible to serve on EEA and UK traffic. […]

Fallback behavior: If a partner does not adopt a certified CMP, only programmatic limited ads will be eligible to serve in the EEA and/or the UK. […]

So, to ensure that you optimally serve ads to users in the European Economic Area (EEA) and/or the UK, you might want to look for another cookie consent solution that’s integrated with a Google-certified CMP.

For more information regarding Google’s consent management requirements, refer to https://support.google.com/adsense/answer/13554116

Can you visit my site once to see the consent pop-up? In that popup, which cookies do I choose to move to the Functionality & Preferences Cookies section?

I’m afraid this is slightly beyond the range of the support we offer for this plugin on the support forum. Our support scope doesn’t include site-specific assistance.

That being said, here’s a brief overview of each cookie category to help you in categorizing your cookies:

• Necessary: Cookies that are necessary for the website to function.
• Analytics: Cookies that allow you to analyze visits and traffic sources.
• Targeting: Cookies that may be set through your site by your social media providers and/or your advertising partners.
• Preferences: Cookies that allow you to provide enhanced functionality and personalization by storing user preferences.

So, under the “Functionality & Preferences” cookies category, you should list any cookies that allow you to provide enhanced functionality and personalization by storing user preferences (e.g. video recommendations).

The “Functionality & Preferences” cookies category maps to the personalization_storage consent type of Google Consent Mode (GCM). Learn more about GCM’s “Consent types” at https://developers.google.com/tag-platform/security/concepts/consent-mode.

You could also take a look at this semi-related topic about cookie categories.

I’m going to mark this as resolved. If, however, you have any further questions, please don’t hesitate to reopen it.

If you come across any other issues, feel free to create a new topic or open an issue on GitHub.

We currently have no plans to become a Google-certified CMP — at least not in the foreseeable future.

Hey, @jane65!

I would like to have a category called ‘Functional Cookies’

Starting from version 1.4.0, there’s a “Functionality and Preferences cookies” category. Cookies under that category are meant to allow you to provide enhanced functionality and personalization by storing user preferences (e.g. video recommendations).

It’s referred to mostly as “preferences” in the plugin’s settings page (and maps to the personalization_storage consent type of Google Consent Mode).

Make sure you’ve updated the plugin to the latest version, and use the “Functionality and Preferences cookie” category for your functional cookies.

I’m going to mark this as resolved. If you come across any other issues, feel free to create a new topic or open an issue on GitHub.

Hey, @ashishtiwari27!

According to the New Google consent management for serving ads in the EEA and UK:

Beginning January 16, 2024, publishers and developers using Google AdSense, Ad Manager, or AdMob will be required to use a Consent Management Platform (CMP) that has been certified by Google and has integrated with the IAB’s Transparency and Consent Framework (TCF) when serving ads to users in the European Economic Area or the UK.

[…]

Beginning January 16, 2024, if a partner does not adopt a Google-certified CMP, no ads will be eligible to serve on EEA and UK traffic. Traffic from a Google-certified CMP will continue to be eligible for personalized ads or non-personalized ads (NPA).

The?Pressidium Cookie Consent?WordPress plugin is?not?a Google-certified CMP. If you need to optimally serve ads to users in the European Economic Area or the UK, you might want to look for another cookie consent solution that is integrated with a Google-certified CMP.

Yes, the ads show correctly when “Ads data redaction” is turned off.

When the “Ads data redaction” option is enabled, the plugin simply sets ads_data_redaction to true.

According to Google for Developers docs, when ads_data_redaction is true and ad_storage is denied, ad click identifiers sent in network requests by Google Ads and Floodlight tags will be redacted. Network requests will also be sent through a cookieless domain.

Though, the ads_data_redaction parameter will have no effect when ad_storage is granted.

So, accepting the “Advertisement and Targeting” (targeting) cookies category—or just clicking “Accept all,” accepting all cookie categories—is going to set the ad_storage consent type to granted, so the ads_data_redaction should have no effect.

You could also use Tag Assistant to debug your website, and confirm that both ads_data_redaction and ad_storage are being set correctly.

What zones to add further? Currently, as you’re seeing, I’ve selected no zone or country. I’m not using GTM, so tick on gtag option.

You don’t have to set any regions. By default, the plugin is going to set all default consent states to denied for all regions. You only have to set a region (or multiple regions) to change that behavior.

What to enter in Functionality & preference cookies?

“Preferences cookies” is a new cookies category, introduced in version 1.4.0. You should use that category for any cookies that allow you to provide enhanced functionality and personalization by storing user preferences (e.g. video recommendations).

The “preferences” category gets mapped to the personalization_storage GCM consent type, which enables storage related to personalization. For more information about GCM consent types, refer to https://developers.google.com/tag-platform/security/concepts/consent-mode#consent-types.

The mapping between the plugin’s cookie categories and GCM consent types is the following:

• Necessary: functionality_storage and security_storage
• Preferences: personalization_storage
• Analytics: analytics_storage
• Targeting: ad_storage, ad_user_data, and ad_personalization

Hey, @ashishtiwari27!

Thank you for your kind words.

Here is my settings image for Google Consent Mode

Did you mean to upload a screenshot?

Ads data redaction is off. When I enable it – ads do not show?

Is this an issue only when “Ads data redaction” is enabled? Do the ads show correctly when “Ads data redaction” is turned off?

Which implementation have you selected under wp-admin -> Cookie Consent -> Consent Mode — “Google tag (gtag.js)” or “Google Tag Manager (GTM) template”?

Hey, @luciusv and @nikodemsky!

Google Consent Mode (GCM) v2 is now supported. It was addressed in 1.4.0, which was just released.

I’m going to update the status of this topic to “resolved”. If, however, you come across any issues or have any questions related to GCM, please don’t hesitate to reopen the topic ??

Hey, @antonijo01!

To ensure clarity and effective issue tracking, it’s preferred to create a new topic for each distinct concern. This helps us maintain clear and focused discussions, and makes it easier for future users to find the relevant topic.

Will you implement Orestbida v3 into plugin?

Yes, we do plan to migrate to orestbida/cookieconsent v3 in the near future.

However, there are many changes compared to v2, so it will require a bit of research, planning, and experimentation before we’re ready to update. Thankfully, v2 will continue to receive maintenance updates for a while, which we’ll try to include in the plugin as soon as they become available.

We’re tracking the progress of that in #50 on the plugin’s GitHub repository.

If you have any further questions related to orestbida/cookieconsent v3, please leave a comment on the linked GitHub issue, or open a new topic.

Hey, @ashishtiwari27!

It’s been over a month since the last message about the font customization stylesheet. I’m assuming that the issue has been resolved.

I’m going to update the status of this topic to “resolved”. If, however, you find that this is still an issue or have any further requestions related to the font customization, please don’t hesitate to reopen the topic ??

• This reply was modified 9 months ago by pressidium. Reason: Changed a word (issue -> topic)

Hey, @ashishtiwari27!

To ensure clarity and effective issue tracking, it’s preferred to create a new topic for each distinct concern. This helps us maintain clear and focused discussions, and makes it easier for future users to find the relevant topic.

Your question regarding the following Google Analytics message:

To verify that your business is collecting consent from end users in the EEA before sending personal data to Google for use in ads personalization, implement ads personalization consent signals.

Verify your consent settings for end users in the European Economic Area (EEA)

End users in the European Economic Area (EEA) must provide consent for their personal data to be shared with Google for advertising purposes.

To ensure there is no impact to your ads personalization and measurement, verify your consent settings for the Google tag and other data sources in Data streams. To implement consent signals, you can use a consent mode API or consent management platform. Learn more about sending consent signals to Google Analytics

seems related to the Google Consent Mode (GCM) implementation.

There’s an active topic about GCM v2, and we’re also tracking the progress of that feature in #51 on the plugin’s GitHub repository.

TL;DR: We’re actively working on implementing Google Consent Mode (GCM) support, which will likely be included in the next release.

Hey, @luciusv!

Thank you for your kind words.

Do you have plans to add support for Google Consent Mode v2?

Yes, we’re actively working on implementing Google Consent Mode (GCM) support, which will likely be included in the next release.

You can stay up-to-date on the progress of this feature, by checking #51 on the plugin’s GitHub repository.

Hey, @ashishtiwari27!

There’s no option to customize the font through the plugin’s UI as of now.

However, it’s possible to specify a font using the --cc-font-family CSS custom property.

You’ll need to create a child theme (or, you could use a third-party WordPress plugin that allows you to include CSS rules into your site), with the following CSS:

:root {
  --cc-font-family: Helvetica, sans-serif;
}

Substitute Helvetica with the font you’d like to use.

We’ll leave this topic’s status as “not resolved” to look into including an option to customize the font via the plugin’s settings.

If you have any more questions, let us know!

Hey, @gratielastronde!

Thanks for your kind words.

How can I add another cookie category?

Unfortunately, creating custom cookie categories isn’t supported right now. However, we’re planning to add this feature in a future iteration.

You can stay up-to-date on the progress of this feature, by checking #13 on the plugin’s GitHub repository.