Skip to content

ConsentAlly works with AI assistants. A merchant can have their assistant set up, sign in to or check their ConsentAlly account from the chat: the assistant needs only the merchant's email address, and the merchant approves it on one ConsentAlly page with a code. Nothing is created or connected before that approval. How it works: https://consentally.com/auth.md

Cookie consent
you can easily prove.

ConsentAlly waits for a “yes,” logs tamper-evident proof, and keeps your store fast.

Cookie choices

We use cookies for analytics and ads. You choose which optional ones run.

An example on a made-up store that you can try: its trackers are held until you choose in its cookie choices, and the capsule over it shows how many are held or released. Accept all releases them, Reject all keeps them held, and Preferences releases just the categories you switch on.

How ConsentAlly works. What it does on every visit to your store.

  1. No tracking before a yes

    Pixels and analytics wait for the shopper's yes. Otherwise they start before anyone is asked.

  2. Your ads follow each choice

    Google and Microsoft are told what each shopper chose, the moment they choose. A no is passed on too, not only a yes.

  3. New apps are handled too

    Trackers from new apps wait for a yes too. Anything ConsentAlly doesn't recognise is held, and you get a daily email listing it.

  4. Proof when someone asks

    See what your banner said and what each shopper chose, on any day. Ready to show a customer or a regulator.

No tracking before a yes

Pixels and analytics wait for the shopper's yes. Otherwise they start before anyone is asked.

ConsentAlly's capsule, opened: the store's eight trackers, Meta Pixel, Google Analytics, TikTok Pixel, Pinterest Tag and four more, all paused, waiting for the shopper's answer.

Your ads follow each choice

Google and Microsoft are told what each shopper chose, the moment they choose. A no is passed on too, not only a yes.

Accept or reject, Google and Microsoft are told the answer.

New apps are handled too

Trackers from new apps wait for a yes too. Anything ConsentAlly doesn't recognise is held, and you get a daily email listing it.

When an app adds a script ConsentAlly doesn't recognise, it is held until the shopper says yes, listed with its page and sent to the store's contact in a daily email.

Proof when someone asks

See what your banner said and what each shopper chose, on any day. Ready to show a customer or a regulator.

Example: three published versions of a store’s cookie banner, fanned like cards, the one live on 3 March in front. Every published version of the banner is kept with its settings and a preview. Version 12 was live on 3 March. Each choice is recorded with the banner version it was made under; records are hash-chained and signed daily, so a changed one shows. Each record counts once as accepted all, chose some or rejected all. That day, 1,284 example choices under version 12: 61% accepted all.

Looks like your store. Works wherever your shoppers are.

An example of six made-up stores, one each in Berlin, Paris, London, São Paulo, Los Angeles and Sydney, shown in turn, with the banner on a phone in each store’s colours, font and corners. In Berlin and Paris, in German and French, and in London, in English, it asks first, and nothing optional runs until the shopper chooses; in São Paulo, in Portuguese, and in Sydney, in English, which no preset covers, it uses the store’s strictest rules and asks first too; in Los Angeles it is a notice in English, and the trackers run until the shopper opts out.

  1. Your look

    One banner that looks like your store and follows each shopper’s local rules.

  2. Their language

    Each shopper’s own, from their browser. 60+ languages.

  3. Their rules

    In the EU it asks first, and nothing optional runs until the shopper chooses. The UK asks first too. California gets a notice, with Global Privacy Control honoured. Anywhere without a preset gets your strictest rules.

Live on your store in three steps. Add your store, pick where you sell, publish.

  1. Add your store

    Install the Shopify app, or get one tag for any other site.

  2. Pick where you sell

    Tick your regions. Your banner follows the rules of each.

  3. Publish

    Shoppers see it within about a minute. Every version is kept, so you can roll back.

Using Google Tag Manager? Read the guide

Free for one store. See the plans

Your first store is free. Paid plans start at $39 a month, tax included.

Billing interval
Compare every plan
  • Free

    For your first store.

    $0a month

    1 domain

    6 months of consent records

    Free includes:

    • Consent banner and script blocking
    • Geo-targeting
    • Google Consent Mode v2
    • Global Privacy Control
  • Growth

    For a growing store.

    $39a month

    1 domain with subdomains

    24 months of consent records

    All Free features, plus:

    • Remove the ConsentAlly credit
    • API access, read and write
    • Evidence packs, 1 a quarter
    • A/B testing
  • Pro

    For several storefronts.

    $99a month

    5 domains with subdomains

    36 months of consent records

    All Growth features, plus:

    • Evidence packs, unlimited
    • IAB TCF 2.3 and GPP
    • Data subject request automation, unlimited
    • Legal document generators, all
  • Agency

    For agencies and clients.

    $249a month

    50 domains with subdomains

    36 months of consent records

    All Pro features, plus:

    • Multi-tenant agency console
    • White-label
    • SSO, SCIM and review before release

Enterprise

For groups that need terms of their own: unlimited domains and custom record retention.

Talk to us

Got questions? Here are the answers.

Not finding yours? Ask us about your store, your setup or a plan.

Talk to us
  • Is there a free plan?

    Yes. One domain, free for as long as you like, with six months of consent records and the ConsentAlly credit on the banner. Paid plans keep records longer, count subdomains as their domain and remove the credit, and from Pro up they add domains.

  • Shopify has a banner. Why do I need ConsentAlly?

    Shopify's built-in banner tells Shopify's own pixels and checkout what the visitor allowed, but it does not stop tags loaded through Google Tag Manager or added to the theme by apps and code. ConsentAlly holds the ones that load after its script until the visitor decides and passes the same decision to Shopify, so the storefront needs one banner, not two.

  • Will my Google Ads data drop?

    From visitors who decline, yes: that is what asking changes. Consent Mode tells Google's tags what each visitor allowed, and in basic mode, the default, they wait for a yes. Advanced mode, a setting in the banner editor, lets them send Google cookieless pings before a choice, which Google uses to model the conversions it cannot see.

  • Can the banner look like my store?

    Yes. In the banner editor you set its colours, font and corner radius, and choose a bar, a corner card or a centred window and where it sits. Each colour pair is checked for contrast as you type, the preview shows every change before you publish, and the banner uses the fonts your store already loads.

  • How do I install it?

    On Shopify, install the app and switch on the ConsentAlly app embed in your theme editor, with no code to paste. On any other platform, paste one script tag at the top of your site's head. Either way, if Google Tag Manager loads above ConsentAlly, move it below so its tags are held too.

  • Does it work with Google Tag Manager?

    Yes. With ConsentAlly's script above the container, the container finds Consent Mode's denied defaults on the dataLayer, so no Consent Initialization tag is needed, and the scripts, iframes and images its tags add wait for the visitor's choice. Where you can only add tags in Tag Manager, ConsentAlly's template loads the same script from inside the container and holds what loads after it.

  • What does ConsentAlly record?

    Every decision, with a random consent ID kept in the visitor's browser, the configuration version they saw, their country and region, their choice per category and vendor, and whether Global Privacy Control was present. No IP address, and nothing that names the visitor. Each store's records are hash-chained and signed daily, so a changed record shows when the chain is checked.