WordPress plugin, GTM draft, and manual script embed

    Three surfaces.
    One consent layer.
    No guesswork.

    ConsentEase installs via the WordPress plugin, a Google Tag Manager tag you review before publishing, or generated embed code in your HTML. Sites that allow custom scripts in the document head can use the manual method.

    Read the Docs

    Three installation surfaces

    Illustrative
    Plugin

    WordPress

    Plugin + guided account link

    GTM

    Google Tag Manager

    Drafts a new tag for you to review and publish

    HTML

    Manual embed

    Generated code in your HTML

    index.html — manual embed
    <script src="https://cdn.consentease.io/v1/ce.js"
      data-site="YOUR_SITE_ID"
      defer></script>

    Setup times depend on your platform and familiarity. WordPress requires a public HTTPS site and plugin directory access. GTM creates a draft you review and publish.

    Integration friction

    Setup complexity is where adoption breaks.

    • Multi-step setup guides create drop-off

      Many consent management platforms require OAuth flows, API keys, DNS records, and container configuration before a banner appears. The length of the process is itself a barrier.

    • Each platform has its own quirks

      WordPress needs a plugin. GTM needs a tag, a trigger, and a publication step. A plain HTML site needs a script in the head. Without a clear path for each surface, setup takes longer than it should.

    • No way to confirm the banner is working

      Pasting a script tag and deploying leaves open the question of whether the banner is actually loading. Without on-demand diagnostics, problems can go unnoticed until a visitor or audit surfaces them.

    The comparison above is illustrative. Actual setup time and complexity depends on your platform, hosting configuration, and familiarity with the tools involved.

    Typical CMP setup — 12 steps

    1. 1Create a CMP account and verify your email
    2. 2Add your domain to the vendor dashboard
    3. 3Generate an API key and copy it somewhere safeRequires developer
    4. 4Install the vendor's npm package (or copy a CDN link)
    5. 5Configure your Privacy Policy URL in the dashboard
    6. 6Map cookie categories to consent purposesEasy to misconfigure
    7. 7Create a GTM container and add a custom HTML tag
    8. 8Set the trigger and test in GTM preview modeBreaks on update
    9. 9Publish the GTM container
    10. 10Add DNS verification record to your domainRequires developer
    11. 11Wait for propagation, then confirm in dashboard
    12. 12Hope the banner loads correctly on every page

    ConsentEase — 3 steps

    1. 1Choose your method (plugin, GTM, or embed code)
    2. 2Follow the three-step guide for that method
    3. 3Verify via your ConsentEase dashboard

    Illustrative contrast. Actual setup complexity varies by vendor and configuration.

    Three installation paths

    Pick your surface. Follow three steps.

    WordPress, Google Tag Manager, and manual embed each have a guided three-step path. Shopify, Webflow, Next.js, and other frameworks are not native integration surfaces — sites that allow custom script insertion can use the manual method.

    Plugin install, then account link
    01

    Install the plugin

    In your WordPress admin, go to Plugins > Add New. Search for "ConsentEase", install, and activate.

    Requires public HTTPS and plugin directory access
    02

    Connect your account

    In Settings > ConsentEase, click Connect. You will be redirected to authorize the link — your WordPress site must be accessible over HTTPS.

    Account required
    03

    Verify in the dashboard

    Once connected, your dashboard shows the link status. Run an on-demand check from Diagnostics to confirm the banner is loading.

    On-demand check available

    WordPress installation requires a public HTTPS site and access to the plugin directory. GTM setup creates a draft tag — ConsentEase never auto-publishes; you review and publish the container yourself. GTM diagnostics are available after you have published the container.

    After installation

    A status you can inspect.

    Once installed, your dashboard shows connection status and available diagnostics. What is visible depends on the installation method and whether the site is publicly accessible over HTTPS.

    Installation statusillustrative example
    mybusiness.comConnected
    • Script presentdetected
    • Banner loadingconfirmed
    • Consent Mode defaultsbefore GTM
    • GTM diagnosticsafter publication

    Diagnostics availability depends on method. WordPress: on-demand checks available. GTM: diagnostics after you publish the container. Manual: check via your dashboard.

    WordPress plugin

    Install from the Plugins directory and link your account. Requires a public HTTPS site and plugin directory access.

    Google Tag Manager

    ConsentEase prepares a draft tag for you to review in GTM's preview mode before you publish. You control publication.

    Manual script embed

    Generated consent defaults and banner script placed in your HTML template. Works with platforms that allow custom scripts in the document head.

    Post-install diagnostics

    WordPress offers on-demand checks from the dashboard. GTM diagnostics are available after you have published the container.

    Scope note. The status panel above is illustrative. Actual diagnostics depend on your installation method and whether the site is accessible over public HTTPS. Shopify, Webflow, Next.js, and other frameworks are not native integration surfaces — sites that allow custom script insertion can use the manual method. ConsentEase does not auto-publish GTM containers; publishing is always a deliberate step you take.

    Feature comparison

    Installation surfaces, compared.

    WordPress plugin

    ConsentEase
    Plugin + guided account link
    Cookiebot
    Configuration-dependent
    CookieYes
    Configuration-dependent
    OneTrust
    Check current plan

    Google Tag Manager

    ConsentEase
    Drafts tag for you to review and publish
    Cookiebot
    Configuration-dependent
    CookieYes
    Configuration-dependent
    OneTrust
    Configuration-dependent

    Manual script embed

    ConsentEase
    Generated embed code for custom HTML
    Cookiebot
    Configuration-dependent
    CookieYes
    Configuration-dependent
    OneTrust
    Configuration-dependent

    Shopify native app

    ConsentEase
    Not currently provided
    Cookiebot
    Configuration-dependent
    CookieYes
    Configuration-dependent
    OneTrust
    Check current plan

    Webflow native embed

    ConsentEase
    Use manual embed method
    Cookiebot
    Configuration-dependent
    CookieYes
    Configuration-dependent
    OneTrust
    Configuration-dependent

    Post-install diagnostics

    ConsentEase
    On-demand (WordPress) / after publish (GTM)
    Cookiebot
    Check the vendor's tooling
    CookieYes
    Check the vendor's tooling
    OneTrust
    Check the vendor's tooling

    Auto-publish GTM container

    ConsentEase
    Never — you publish deliberately
    Cookiebot
    Configuration-dependent
    CookieYes
    Configuration-dependent
    OneTrust
    Configuration-dependent

    Neutral, configuration-dependent comparison. Competitor capabilities depend on plan and configuration — verify with each vendor before deciding. ConsentEase does not provide a Shopify native app at this time.

    See Full Comparison

    Scan first. Install in three steps.
    Diagnostics confirm it works.

    Run a free scan to see what your site currently drops, then install the banner using whichever method fits your setup.

    Contact Us
    WordPress plugin, GTM, and manual embed
    Consent Mode v2 defaults in place
    Diagnostics available after install