2.0 Beta

Smootify 2.0 is in public beta. Your 1.x store keeps working. Move when you want.

What changed

smootify-consent

Cookie banner and preferences panel built over Shopify's Customer Privacy API: shown while Shopify asks for consent and the visitor has not answered, the preferences while open. With button[data-is="preferences-button"] inside (one component, e.g. in the Footer, the banner in a [popover] or [consent-panel]) it stays for the button wherever the consent applies, the banner closed until asked; elsewhere it is hidden whole (2.0).

v2.0 beta
Open .md
On this page
  1. Where it can go
  2. What it requires
  3. Fields in the form
  4. Attributes on the element
  5. Attributes inside it
  6. Loading

Where it can go

  • Anywhere on the page.
  • Out of place, it stays in the page and does nothing.

What it requires

Nothing beyond Smootify: it works on every plan.

Fields in the form

Each field’s name attribute tells Smootify what the field holds.

NameFieldWhat it does
analytics, marketing, preferences, sale_of_data (or saleOfData)input type="checkbox" (name exactly)Checked: that kind of tracking is allowed, saved by [data-action="save"]; the boxes follow the stored consent.

Attributes on the element

  • Smootify writes is-loaded, is-required, is-open, is-sale-of-data-region, is-applicable on it: do not set them yourself.

Attributes inside it

GroupAttribute nameValues
Cookie consentdata-action11
Cookie banner (condition)consent-condition1

Loading

Its code loads only on pages that have smootify-consent.

    ↑ ↓ to moveEnter to openEsc to close