Skip the manual navigation

Cookie consent and double opt-in for email marketing

Show visitors a cookie consent banner where it's required, choose who sees it, and set your double opt-in preference for email marketing.

6 min read · Updated October 3, 2026 · Screenshots use demonstration accounts

On this page
  1. 1. Open Customer privacy
  2. 2. Choose who sees the cookie banner
  3. 3. Set the region list
  4. 4. Override the banner for one market
  5. 5. Know what a visitor sees
  6. 6. What this holds back
  7. 7. Set double opt-in
  8. 8. Know how confirmation works
  9. 9. Save
  10. Completion checklist
  11. Troubleshooting
Before you start

On a phone? Open the admin menu to find the same section. Screenshots below show the desktop view; tap “Open full size” for a closer look.
STEP 1

Open Customer privacy

Go to Settings → Customer privacy.

STEP 2

Choose who sees the cookie banner

Under Show the banner, pick Off, To every visitor, or In regions that require it. Off means analytics (Google Analytics) and marketing pixels (Meta, TikTok) run for every visitor unless they opted out earlier. To every visitor shows the banner to everyone and holds those pixels back until they choose. In regions that require it shows it only to visitors in the regions you list below — and to a visitor whose location can't be detected, so no one who might need it is skipped.

  • Off
  • To every visitor
  • In regions that require it
STEP 3

Set the region list

With In regions that require it chosen, enter two-letter country codes separated by commas, or a state such as US-CA, in the Regions box. Click Use the recommended list to fill it with the EU and EEA, the UK, Switzerland, Brazil and California (California only matches when the visitor's state is known).

STEP 4

Override the banner for one market

A single market can show the banner differently from your store-wide setting: open Markets → that market → Customer privacy and choose Use store setting, To every visitor, In regions that require it, or Off for that market alone. An override can turn the banner ON for a market even where your store-wide setting is Off, but it can't turn it off for a visitor whose real location requires it under your region list.

STEP 5

Know what a visitor sees

Where the banner applies, a first-time visitor is offered Accept all, Decline, or Manage preferences (which splits Analytics and Marketing into separate switches; necessary cookies are always on). Nothing analytics- or marketing-related loads until they choose. Their choice is remembered for 180 days, and they can reopen the banner any time from the "Cookie settings" link in your store's footer.

STEP 6

What this holds back

Where the banner applies, tracking code in your theme (head snippets and custom scripts) is held back until the visitor consents, when it's recognisable as a known tracker — Google Analytics, Tag Manager and Ads, Meta, TikTok, Snap, Pinterest, Clarity and Hotjar. This check is pattern-based, so a disguised or unrecognised tag can still load before consent; load those yourself behind `window.swPixel('analytics', …)` or `'marketing'` so they wait too. Google Analytics, Meta and TikTok pixels you've connected in Analytics follow the same rule automatically.

STEP 7

Set double opt-in

Under Email marketing, turn on Require double opt-in for email marketing so new subscribers must confirm by clicking a link in an email before they're actually subscribed. Once it's on, a footer or section newsletter sign-up, the checkout marketing opt-in box, a customer's own account profile, and a marketing opt-in collected through store chat all record the shopper as PENDING and send them a confirmation email instead of subscribing them right away.

STEP 8

Know how confirmation works

The confirmation email links to a page with its own Confirm subscription button — opening the email, or a link preview or security scanner fetching it automatically, never subscribes anyone by itself. The link works for 14 days; after that, or after the shopper unsubscribes, it stops working and signing up again sends a fresh one. If someone who's already pending signs up again, Lulu won't re-send the email more than once every 10 minutes. While a subscriber is pending, they get no marketing email at all.

STEP 9

Save

Click Save.

CHECK YOUR WORK

You’re ready when…

  • Chose Off, To every visitor, or In regions that require it for the cookie banner
  • Set or used the recommended region list if you chose regions
  • Checked any market that needs a different banner setting under Markets → that market → Customer privacy
  • Linked your cookie and email practices from your Privacy policy
  • Know double opt-in now sends its own confirmation email for newsletter/footer, checkout, account-profile and chat sign-ups — separately from any double opt-in setting inside the Postbox app

IF SOMETHING DOESN’T LOOK RIGHT

Troubleshooting

I set the banner to regions, but a visitor outside my list still saw it.

A visitor whose location can't be detected is shown the banner too, by design — when Lulu can't tell where someone is, it asks rather than assume they don't need it. That's different from a market-level override, which can only add the banner for a market, never remove it for a visitor whose real location requires it.

A market's Customer privacy page shows a different banner setting from my store-wide one.

That market has its own override, set under Markets → that market → Customer privacy. Choose "Use store setting" there to go back to following Settings → Customer privacy.

Will turning on double opt-in re-confirm my existing subscribers, or start sending confirmation emails?

It doesn't touch anyone already subscribed — their consent stays as it was. But from the moment you turn it on, every NEW sign-up (newsletter or footer form, checkout, account profile, chat) is recorded as pending and sent a confirmation email instead of being subscribed right away. The Postbox app has its own, separate double opt-in setting for the sign-up forms it builds.

A pixel or tracking script still runs before a visitor accepts.

Lulu can only hold back scripts it recognises as a known tracker by pattern — a disguised or unusual tag can slip through. Wrap it in `window.swPixel('analytics', function () { … })` or `'marketing'` in your theme code so it waits for consent like the rest.

In this section: Store policies & privacy

Still need help?

Tell us your store address and what you’re trying to do. Leave out passwords and payment details.

Contact support