Your Cart
Elementor Cookie Consent setup

How to Configure Elementor Cookie Consent for WordPress Websites

A cookie banner is only one part of a broader consent setup. On a WordPress website, the result also depends on which cookies and third-party scripts are present, how they are grouped, when they load and how visitors can change their choices. Elementor Cookie Consent is documented as a standalone solution for managing consent, scanning cookies and scripts, recording consent interactions and controlling third-party script execution.

This guide follows the documented setup path: install and connect the plugin, choose a consent mode, scan relevant areas of the site, review categories, configure script blocking, customize the banner and test the result. The documentation describes product functionality; it does not establish legal compliance for a particular website. Your configuration should be reviewed against the actual plugins, embeds, analytics tools, advertising services and theme settings used on your site.

What Elementor Cookie Consent does and when to use it

Elementor Cookie Consent brings several tasks into one WordPress workflow. It can display a consent interface, scan the website for cookies and scripts, organize detected cookies into categories and control the execution of third-party scripts according to the selected configuration. It also records consent interactions, giving site owners a way to review how the consent system is configured and how it behaves during testing.

This means the banner should not be treated as an isolated design element. A visually polished banner does not by itself determine whether analytics, advertising, embedded media or another external service loads before the required consent state. The practical purpose of the setup is to connect the visitor-facing interface with categories, cookie records and script-blocking rules.

The appropriate configuration depends on the website, its visitors, jurisdictions, services and data flows. Elementor documentation is product guidance rather than legal advice, so selecting a template or completing a scan should not be presented as an automatic compliance guarantee.

Install the plugin and start the setup wizard

Begin in the WordPress administration area. Go to Plugins → Add New, search for Cookie Consent, and install and activate the plugin. After activation, open Elementor → Cookie Consent and select Get started. The documented flow prompts you to connect Cookie Consent to an Elementor account before continuing with the setup.

The initial sequence then presents the main consent template choices, a layout choice and the first scan. Follow these steps in order rather than treating installation as the complete configuration. The scan and later review determine whether the initial settings reflect the actual site. For Elementor One users, the documentation also describes an alternative entry point through Elementor → Home.

Confirm the initial setup choices

During the first setup, keep three decisions separate. First, choose whether the consent behavior should use an opt-in or opt-out template. Second, select the initial visual layout: Banner, positioned along the bottom of the screen, or Box, positioned in the lower-left area. Third, start the initial homepage scan. These choices provide a starting configuration; categories, script rules, design and testing still require attention afterward.

Choose opt-in or opt-out

The template choice affects how visitors interact with consent and how cookie categories behave. In the documented opt-in model, visitors must agree before the relevant cookies are accepted. In the opt-out model, cookies are allowed unless visitors actively choose otherwise. The selected mode therefore affects the loading or blocking behavior associated with the configured categories.

Do not choose between these templates solely by looking at a visitor’s country or by assuming that one option is universally correct. Review the privacy and electronic-communications requirements applicable to the website and its services. Elementor’s descriptions explain product behavior, but they do not determine the legal configuration for every site or situation.

Compare the two template behaviors

With opt-in, the visitor action is required before the relevant cookies are accepted. This makes the relationship between the consent choice and pre-consent script behavior especially important: non-essential services should be checked before the banner is published. With opt-out, the documented default is that cookies can be used unless visitors actively choose otherwise.

Whichever template you select, compare the observed behavior with the intended configuration. A scan, category assignment and script rule should work together. If a non-essential script still creates cookies or sends requests before the relevant consent action, the configuration needs further review and testing.

Run a cookie and script scan

The setup flow prompts you to scan the homepage. You can also start a scan later from Cookie Management → Scan now. Elementor documents three scan choices: Homepage, Full Scan and Custom Scan. The homepage option provides a starting view of the site, while the other options let you expand or focus the review.

A Full Scan can cover broader site areas and supports URL exclusions. A Custom Scan allows you to select specific URLs. This is useful when you need to examine particular sections that use different forms, embeds, templates or third-party services. Choose the scope according to the parts of the website you need to review, rather than assuming that one page represents every possible configuration.

After a scan, the report may include the scan status, pages scanned, credits consumed, cookies found by category, detected scripts and errors. Scan history can contain details such as the date, status, pages scanned and items found. These details help you identify whether the scan covered the intended areas and whether errors require attention.

Select the scan scope

Use the homepage scan as the documented starting point when beginning the setup. Choose Full Scan when broader coverage is needed, and apply URL exclusions where relevant. Choose Custom Scan when selected URLs represent the areas you want to inspect. The report is an inventory aid, not proof that every cookie, script, embedded service or consent dependency has been identified or classified correctly.

Compare the results with the real website configuration. Review the plugins, embeds, analytics tools, advertising services and theme settings that are active on the site. Repeat the review when those elements change.

Review categories and block scripts before consent

The documented default cookie categories are Necessary, Functional, Analytics, Advertisement and Unclassified. Their loading or blocking behavior differs between opt-in and opt-out configurations. After scanning, inspect the detected items instead of accepting every automated classification without review.

For each cookie, consider the provider, purpose, domain, duration or expiry and role in the site’s data-processing setup. A cookie name alone is not a reliable basis for classification. Elementor documents controls for editing and deleting cookie entries, adding cookies manually and moving entries between categories. These controls are useful when the scan does not fully represent the site’s actual configuration.

Clean up cookie categories after scanning

Start by reviewing the items shown in each documented category, including anything placed in Unclassified. Check whether the listed domain, duration and visitor-facing description match the service that creates the cookie. Where the site-specific review supports a different categorization, use the documented controls to move or edit the entry.

You can also add an entry manually when a cookie was not included in the scan, remove an entry that no longer reflects the site and update descriptions used for visitors. This manual pass is important because the scan should be treated as a starting inventory rather than a final decision about every service.

Configure third-party script blocking

Cookie management and script management should be reviewed together. For a third-party script, the documented settings include a script name, URL pattern, assigned category and description. The available blocking modes are Always Block, Block Until Consent and Never Block.

Select the mode that matches the intended consent configuration and the role of the script. In particular, verify that non-essential analytics, advertising and other third-party scripts do not run before the required consent state is obtained. Do not assume that the scan has identified every dependency automatically. After saving the rules, check browser cookies and network requests before and after the relevant visitor action.

Customize the banner with Elementor

Yes, the consent banner can be customized through Elementor’s documented visual workflow. Open Elementor → Cookie Consent → Design → Design with Elementor. The banner then opens in the Elementor Editor, where the documented options include visual styling, typography, layout changes and Elementor widgets. The workflow also describes editing the preferences dialog and revisit button.

The initial setup offers Banner and Box layouts, while positioning can subsequently be adjusted in the dashboard’s Design section. Access to the visual popup builder depends on the relevant Elementor subscription level. The available documentation does not provide a complete comparison of plans, prices or licensing conditions, so no assumptions should be made about access beyond that documented subscription dependency.

Separate content settings from visual design

The Cookie Consent dashboard controls the banner header, main text and button content. The Elementor editor is used for visual styling and layout changes. Keeping these responsibilities separate makes troubleshooting easier: if wording or button labels are wrong, check the dashboard; if spacing, typography or visual arrangement needs adjustment, check the editor.

Visual customization does not configure consent categories or establish legal compliance. After publishing a design, return to the technical settings and test whether the configured banner, preferences dialog, revisit button, categories and script rules work together as intended.

Test the finished configuration

Test the result in a clean browser session so that previous consent choices do not hide the actual behavior. Check the banner display, the available choices and the result of each relevant action. Then inspect the browser’s cookies and network requests before consent and after the consent state changes.

Pay particular attention to the services actually used by the site. Verify the behavior of analytics, advertising, embedded media and other third-party services. Compare what you observe with the selected opt-in or opt-out mode, the category assignments and the configured script-blocking modes. A technically correct visual banner is not enough if a script runs at the wrong point in the visitor journey.

Use scan results, scan history and browser behavior together. Repeat these checks after adding or updating plugins, embeds, analytics tools, advertising services or theme settings, because the site’s cookie and script inventory can change. Technical testing helps reveal configuration problems, but it does not replace a site-specific legal assessment.

  • Test in a clean browser session.
  • Review cookies and network requests before and after consent.
  • Check analytics, advertising, embedded media and other third-party services.
  • Compare observed behavior with the selected template, categories and blocking modes.
  • Repeat the review after relevant website changes.

Configure Elementor Cookie Consent as a connected process: install and connect the plugin, choose the consent mode, scan the relevant site areas, review the Necessary, Functional, Analytics, Advertisement and Unclassified categories, configure third-party script blocking, design the banner and test the live behavior. A scan is a useful starting point, not final proof of complete classification. Likewise, a custom banner controls presentation, not the entire consent system. Review the actual cookies, providers, scripts and data flows used by the website, and keep technical checks separate from legal conclusions. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.

Free Worldwide shipping

You can download the products right away at wpbetterplugins.com

Immediate delivery

After the payment is credited, the product is ready for download

International Warranty

Offered in the country of usage

100% Secure Checkout

Stripe / Apple Pay / Google Pay / MasterCard / Visa

Zadzwoń