This guide will help you configure the Cookie Banner offered by My Agile Privacy according to your design requirements.
The main customisation possibilities available are described below.
The cookie banner can be configured to match the design of your site. These are some of the main customisation options:
You can display a real-time preview to check changes before publishing.
These options are available by clicking on the My Agile Privacy menu in the administration of your WordPress site.
If you want to customise the banner beyond the possibilities offered by the available options, we have thought of that too.
Simply go to My Agile Privacy > ‘Advanced’ tab and you will find two options that will allow you advanced customisation.
Important note: We do not recommend using the settings described below if you are not familiar with the basics of CSS, the style sheets for graphic customisation of html pages.
This option allows you to write custom CSS that will be inserted into your pages.
The My Agile Privacy banner cookie has a specific ID, which is my-agile-privacy-notification-area.
By targeting this specific ID, or the elements it contains, it is possible to carry out a finer and deeper customisation of the appearance of the banner itself, and of texts, buttons, etc.
The details of IDs and classes of internal elements can be seen from the browser's javascript console by selecting the banner cookie and analysing the DOM structure.
Remember that the CSS code you write here will be embedded in all pages of the site as long as My Agile Privacy is active.
This option allows you, in combination with the previous option, to customise the pages displaying the policy texts.
In fact, by ticking the option, the policy texts inserted via shortcode will be interceptable via a specific CSS selector, the myagileprivacy_text_wrapper class.
The addition of the class makes it possible to customise the appearance of policy texts via CSS, e.g. by inserting a background colour, adjusting size and font, etc.
The customisation CSS can be inserted within the field seen above, Custom CSS.
The Cookie Banner texts can be edited by accessing the My Agile Privacy > Texts and Translations menu.
The editing system allows you to see in real time how the banner looks after the text changes.
By selecting the desired text, you can customise it to suit your needs.
These customisations are available individually for all languages supported by My Agile Privacy, and provided for in the plan in use.
Important note: it is advisable to consult your privacy advisor before making any changes to texts, in order to avoid any risk of non-compliance.
What if I want to revert to the original texts?
You can do this by clicking on the appropriate option 'Do you want to revert to the default contents? Click here to reset the current language'.
Again, you can reset the texts for each individual language, remembering to save the settings after resetting to make the changes effective.
My Agile Privacy allows you to show the user warning messages if specific cookies have not been accepted.
This possibility makes it possible, for example, to let the user know that the submission of a contact form may fail if the Google ReCaptcha cookie has not been accepted, or that the newsletter form (included via external code) is not visible if the relevant cookie is not accepted, etc.
It is possible to display the message in specific places on the pages: it is a matter of inserting a block of html code.
The message, which is automatically hidden when the relevant cookie is accepted, looks like this:
Warning: your cookie choices do not allow the display of this content. Click here to review your preferences.
If you click on the message, the cookie banner will be shown again and you can change your preferences if you wish.
You can create a custom message that is tied to a specific cookie, and therefore visible when that cookie has not been accepted.
The creation is very simple and can be done in a few minutes.
1. Identify the cookie for which you want to show the message
For example, if I want to show a message when the Gooogle ReCaptcha cookie has not been accepted, I will go to My Agile Privacy > cookie list
and among the cookies detected I will enter the Google RECAPTCHA cookie.
2. Copy the API KEY of the cookie
All cookies have a specific API KEY indicated within the cookie settings.
This API KEY will be used to link the warning message to that individual cookie.
In the case of the Gooogle RECAPTCHA cookie, the API KEY is google_recaptcha
3. Customise the message code
This is the html code of the warning message below:
<div class="map_custom_notify map_api_key_APIKEYHERE showConsentAgain" style="display: block;">
Warning: Your cookie choices do not allow this element to be displayed. Click here to review your preferences.
</div>You will have to customise the code by replacing APIKEYHERE with the API KEY of the cookie for which you want to display the message
Likewise, if necessary, you can customise the message inside For example, for the Gooogle RECAPTCHA cookie, it makes more sense to inform the user that the form submission may not work, instead of mentioning ‘displaying the element’.
The message code for the Google RECAPTCHA cookie will therefore be customised as follows
<div class="map_custom_notify map_api_key_google_recaptcha showConsentAgain" style="display: block;">
Warning: your cookie choices do not allow the form to be submitted. Click here to review your preferences.
</div>Note how APIKEYHERE has been replaced with google_recaptcha, and the message has been changed to fit the context
For a complete configuration of My Agile Privacy you can consult these resources
