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

Docs pages

Publish your banner

Every change to your banner starts as a draft, which visitors never see. Publishing makes the draft the next numbered version, visitors get it within about a minute, and every version stays in the history, ready to roll back to.

Edit and preview the draft

  1. Open Banner: in the dashboard it is under Store in the side menu, and in the Shopify app it is in the app's menu.
  2. Change what you need in its five sections: Layout, Theme, Text, Categories and vendors and Consent signals. A section you changed says Changed, and one with a problem says Needs a fix.
  3. Keep your changes with Save draft in the dashboard's top bar, or Save in the Shopify app's save bar.

The preview beside the form is the real banner, drawn from your unsaved changes as you make them. Switch it between desktop and phone, the banner and the preferences, light and (when your theme has a dark palette) dark, and the places and languages your banner covers, to see what each visitor gets.

Changing where you sell changes the draft too: publish again so visitors get the new rules.

Publish

  1. Select Publish in the dashboard's top bar, or Review and publish in the Shopify app. Unsaved changes are saved first, then Publish and history opens.
  2. Read Changes since the live version: each change in the editor's words, with what it was and what it is now.
  3. Select Publish version followed by its number. In the Shopify app, confirm it in the dialog that opens.

A draft with a problem cannot be published: the page lists what to fix and in which section, and visitors keep getting the live version meanwhile. When your draft is the same as the live version, there is nothing to publish.

Discard changes puts your draft back to the live version. Nothing changes for visitors.

When visitors get it

Publishing saves the new version at once, and ConsentAlly's edge then serves it to visitors, usually within a minute. Until it does, the page says which version visitors still get, and the history marks the new version Publishing, then Live. If it has not reached visitors after five minutes, the page says so, and delivery keeps trying.

A visitor's browser can reuse the configuration it fetched for up to a minute, so a page opened in that minute can still show the version before.

Until you publish for the first time, visitors get no banner. A page that already carries the tag meanwhile holds third-party trackers and shows nothing.

Each store can publish or roll back 5 times in 10 minutes and 30 times in a UTC day. Past that, the page says how long to wait.

The history

Publish and history lists every version, newest first, with when it was published (in UTC), who published it and its fingerprint, the start of a hash of its content. Open a version to see its settings and a preview of it, and how it differs from the live version.

Roll back

Roll back on an earlier version asks first, then makes that version live again: visitors get it within about a minute, and the version you rolled back from stays in the history. Your draft is replaced with the version you rolled back to, so changes you had not published are lost.

When ConsentAlly's rules for your regions have changed since that version, rolling back publishes its settings under today's rules, as a new version.

If your banner does not show on your site at all, see Waiting for the tag. What ConsentAlly does not do is listed on the Limitations page.