How to customise the My Agile Privacy® cookie banner

This guide will help you configure the Cookie Banner offered by My Agile Privacy^® according to your design needs.
Below you'll find the main available customisation options.

Graphic Customisation of the Cookie Banner

The cookie banner can be tailored to match your site's look and feel. Here are some key options:

• Size and layout: 4 layouts to choose from — Big and Branded (default), Big, Wide, and Boxed.
• Positioning: vertical (top, centre, or bottom of the page); horizontal (left, centre, or right), available with the Big and Boxed layouts.
• Floating banner: the banner can float detached from the page edges or stick to them.
• Shadow and entrance animation: shadow effect (soft or strong) and entrance animation (slide or fade).
• Banner title: optional, with dedicated text and background colours for the heading.
• Colours: ready-made colour presets (Light, Dark, and more) or fully customisable background, text, and button colours.
• Buttons: display order of Accept, Reject, and Customize, plus button icons.
• Typography: adjustable font size and line spacing.
• Curvature radius: set rounded corners for banner and buttons.

A real-time preview lets you view changes before going live.
All options are available via the My Agile Privacy^® menu in your WordPress admin area.

Customising the Cookie Banner: Custom CSS and Wrappers

If you wish to go beyond preset options, My Agile Privacy^® allows for advanced customisation.
Go to My Agile Privacy^® > Advanced tab and find two advanced settings.
Important note: Do not use these settings unless you're familiar with CSS and styling HTML pages.

Custom CSS Option

Write your own custom CSS, injected into all your site’s pages.
The banner has a specific ID: my-agile-privacy-notification-area. Target that ID or inner elements for deep customisation of the banner, text, buttons, etc.

You can inspect IDs/classes in the browser console on the banner.
All CSS in this field is loaded site-wide while My Agile Privacy^® is active.

CSS Wrapping Option

Ticking this option applies a .myagileprivacy_text_wrapper class to policy texts displayed via shortcode, making it easy to style background, font, size and more via CSS.

Put your custom style rules in the same “Custom CSS” field as above.

Customising Texts

You can edit every Cookie Banner text via My Agile Privacy^® > Texts and Translations.
You’ll see real-time previews, and can customise text for every supported language in your plan.


Important: Consult your privacy advisor before changing legal texts, to avoid any risk of non-compliance.

Resetting Texts to Default

To revert to original texts, click 'Do you want to revert to the default content? Click here to reset the current language'. You can reset for each language, but remember to save your changes afterwards.

How to customize Revisit Widget

Users must be able to change their cookie choices at any time.
Customize or hide the revisit widget from the Consent Widget box in the Consent tab. If you choose to hide it, make sure you add an accessible link or button (e.g. in your footer) so users can reopen the consent banner—instructions are available within the tab.

Please note: if you disable the consent widget, you need to add the dedicated shortcode indicated in the tab instructions, so that users can review their choices at any time. If the re-consent widget is disabled and the shortcode has not been added, the re-consent widget will still be displayed. This is a way to help you keep your site compliant.

How to show a warning message for non-accepted cookies

My Agile Privacy^® lets you display warning messages if a user has not accepted specific cookies.
This is useful for informing users why a feature (e.g., a contact form with Google ReCaptcha) doesn't work, or a newsletter form isn’t shown.
In the Cookie Banner tab you’ll find two ready-made options:

• Notification Bar: shows a bar on the site listing the content blocked on the current page until consent is given. You can display it even before any consent choice and set it to close automatically after a timeout.
• Blocked Content Widget: a placeholder widget is displayed instead of the blocked content (e.g. a Google Map), and you can set its text and background colours.

Alternatively — or in addition — you can manually add an html block where needed.
The message (which disappears when the cookie is accepted) looks like this:

Clicking the message will re-open the banner and let the user change preferences.

How to create custom messages for specific cookies

When a piece of content is blocked because the visitor has not given consent to the cookie that governs it, you can show a clickable notice in its place that reopens the preferences panel.

From version 3.3.7 the plugin generates the code for you.

How to do it

1. Open My Agile Privacy^® › Cookie List and click the cookie you are interested in (for example Google reCAPTCHA).
2. In the Script Installation box press Generate reconsent widget code.
3. If your website is multilingual, choose the language from the drop-down menu.
4. Press Copy and paste the code into your page, where the blocked element appears.

You don’t have to look up or replace any key: the generated code already contains the key of the cookie you are editing.

How the notice behaves

The notice is visible only to visitors who have not accepted that cookie. When the visitor gives consent, the message disappears on its own and the blocked content becomes available again. Anyone who accepted on an earlier visit never sees it at all.

The text is clickable: clicking it reopens the cookie preferences panel.

You can change the text

The generated code is ordinary HTML: you can rewrite the message between the two tags however you like. Do not change the classes (map_custom_notify, map_api_key_…, showConsentAgain, mapShowItem): they are what ties the notice to the cookie and governs when it appears.

One notice per cookie, per page

If you have more than one element blocked by the same cookie on the same page, insert a single notice. For different cookies you can insert one for each.

Alternatively: the manual procedure

If you prefer to write the code by hand, or you are working on a version earlier than 3.3.7:

1. Identify the cookie in My Agile Privacy^® › Cookie List and open its details (e.g. Google reCAPTCHA).
2. Copy its API KEY from the cookie settings (e.g. google_recaptcha).
3. Customise this code:

<div class="map_custom_notify map_api_key_APIKEYHERE showConsentAgain mapShowItem">
Warning: your cookie choices do not allow this element to be displayed. Click here to review your preferences.
</div>

4. Replace APIKEYHERE with the cookie’s key. You can change the message text.

Example for Google RECAPTCHA:

<div class="map_custom_notify map_api_key_google_recaptcha showConsentAgain mapShowItem">
Warning: your cookie choices do not allow the form to be submitted. Click here to review your preferences.
</div>

Useful Resources

For a complete My Agile Privacy^® configuration, check out:

• How to automatically detect and block cookies with Cookie Shield
• How to make contact forms GDPR-compliant