Skip to main content
A visitor who clicks an email usually lands on your site before they answer the cookie banner. They might browse two or three pages before clicking Accept, or never answer at all. What happens before they answer depends on the consent mode you choose:
  • Buffer — the tracker saves the landing page in the visitor’s browser without sending anything to Maestra Platform. If the visitor accepts, it’s sent and recorded. If they decline, it’s deleted.
  • Gate — nothing is collected until the visitor accepts.
Here’s a closer look at each mode.
Use buffer to keep email and campaign attribution.
Choose gate only if your legal team requires that no data is stored in the browser or sent to Maestra Platform before consent.
If a visitor accepts and later switches to Decline, Maestra Platform:
  • Deletes its identifier cookies (maestraDeviceUUID, directCrm-session) and the data it keeps in local storage and IndexedDB.
  • Stops sending tracking requests from that page on.
If they accept again, tracking starts over with a new anonymous identifier.
The visitor’s choice is remembered.
Once the visitor accepts or declines, the choice is saved in the maestraConsent cookie for up to one year. On later pages, the tracker applies it right away instead of waiting for the banner. The cookie holds the choice, its date, the purposes, and where the choice came from — no identifiers. Safari and other browsers with tracking prevention delete it after about 7 days, so a returning visitor may see the banner again.
The Maestra app embed reads the visitor’s choice from Shopify’s Customer Privacy API. It works with the native Shopify cookie banner and with any consent app that reports to Shopify.
1

Open App embeds

In Shopify admin, go to Online Store → Themes → Customize → App embeds.
2

Open the Maestra embed

Find the Maestra embed and open it.
3

Set Consent mode

  • Buffer until consent — buffer mode (default).
  • Don’t load before consent — gate mode.
4

Click Save

How the Shopify integration handles consent:
  • Maestra Platform tracks a visitor only when they allow both analytics and marketing. A visitor who allows analytics but not marketing isn’t tracked.
  • In regions where your store doesn’t show a cookie banner, tracking starts on page load, as before.
  • The Shopify Web Pixel (cart and product events) follows the same choice. No separate setup needed.
  • The app also reads PieEye’s choice directly, even though PieEye doesn’t report to Shopify.
  • The app passes the visitor’s purposes (analytics, marketing, preferences, sale of data) with each choice. See Shopify notes for how they map.
Remove hand-pasted tracker code from your theme. If your theme has its own maestra('create', …) snippet that runs before the app embed, that snippet wins and consent settings are ignored — the visitor is tracked before they answer the banner. Remove the snippet and keep only the app embed.
Consent apps that don’t report to Shopify. Some consent tools don’t pass the visitor’s choice to Shopify’s Customer Privacy API, so the Maestra app can’t see it. PieEye is the exception: the app reads it directly. For any other such tool, pass the choice to the tracker yourself with consent.set, as described below.
If you install the tracker with a code snippet or through a tag manager, add a consent block to the create call, then pass the visitor’s choice from your consent tool to the tracker.
Without the consent block, the tracker works as before and tracks every visitor from the first page.
If the consent block is invalid — for example, default is missing or misspelled — the tracker tracks no one until the visitor makes an explicit choice. Check the browser console for errors after setup.
In gate mode on your own site, the tracker script still loads — it just keeps and sends nothing. If you need zero requests to Maestra Platform before consent, load the tracker snippet only after the visitor accepts.

2. Pass the visitor’s choice

Call consent.set from your consent tool’s callback when the visitor answers the banner or changes their choice later:
You can call it on every page with the current choice. Repeating the same value does nothing. A string sets every purpose to the same value. If your consent tool reports purposes separately, pass an object instead:
Unknown keys are ignored. If a value is invalid, the call is ignored and the consent state doesn’t change. consent.get and consent.subscribe still return the state as a string.

3. Read the current state (optional)

Calls made while consent is pending — product views or cart updates, for example — are held in the browser. They’re sent if the visitor accepts on the same page and discarded if they decline.

What lands on the customer profile

When storing consent on the profile is turned on for your account, every explicit choice is also kept on the customer profile:
  • A system action — Tracking consent granted, Tracking consent withdrawn, or Sale of data opt-out — with the source, consent tool, browser, sale of data, and each purpose.
  • The current consent for each browser and site, on the customer card under Devices → Browsers.
  • A Consent changed entry in the customer’s change history.
The tracker sends a grant right after it registers the visit, and a withdrawal just before it deletes its identifiers. If the browser has Global Privacy Control on, it also sends a separate sale-of-data opt-out. Defaults from create are never sent. You can then find customers with the Tracking consent and Sale of data filters. For details, see Consent on the Customer Profile. Consent adds two records to what Maestra Platform keeps in the visitor’s browser. List them in your cookie policy under whichever category your legal team chooses. For identifier cookies and everything else Maestra Platform stores, see Cookies and Browser Storage.

How to check it on your site

Open your website in a private window, so no earlier choice is stored, and open your browser’s developer tools.
1

Check Network before answering the banner

Go to Network and filter by maestra. In buffer mode, you should see only the tracker script (tracker.js). In gate mode on Shopify, you should see nothing.
2

Check cookies and session storage

Go to Application → Cookies. There shouldn’t be a maestraDeviceUUID cookie yet. In buffer mode, Session Storage holds maestraLanding with your landing page.
3

Click Accept

In Network, you should see visit requests. maestraDeviceUUID and maestraConsent appear in Cookies, and maestraLanding disappears.
Questions? Reach out to your Maestra Platform Forward Deployed Marketer.