Skip to main content
When a visitor answers your cookie banner, Maestra Platform can keep that choice on the customer profile as evidence: what the visitor chose, on which browser and site, when, and through which consent tool. You can then see the choice on the customer card and find customers by it with filters. This article covers what is stored and where to find it. To set up the banner integration itself, see Consent and Tracking.
Available on request.
Storing consent on the profile is turned on per account by the Maestra Platform team. It isn’t a self-service setting. To turn it on, contact support or your Maestra Platform Forward Deployed Marketer.

​
Before you start

Maestra Platform records a choice only when the tracker knows about consent:
  • Maestra Shopify app. The app embed passes choices automatically. See Shopify notes.
  • Your own site or a tag manager. The create call must have a consent block, and your consent tool must call consent.set when the visitor answers. See Set up consent with JavaScript.
Without a consent block in create, the tracker tracks every visitor as before and records no consent.

​
What gets recorded

The tracker reports explicit choices only: These aren’t recorded:
  • Regional defaults. A state that comes from the default in create (for example, a region where your store shows no banner) is not the visitor’s choice and is never sent.
  • Repeats. A choice identical to the one already stored changes nothing on the profile. You can call consent.set on every page.
  • A decline on the first visit. A visitor who declines before ever accepting has no device ID, and none is created. There is nothing to attach the choice to.
Recording consent never creates a customer, never changes email or SMS subscriptions, and isn’t triggered by a form submission.

​
What is stored on the profile

Each choice can carry four purposes, each granted or denied: Tracking consent is analytics and marketing together: it’s granted only when both are granted. Advertising is stored separately and never affects tracking consent. Sale of data is a separate value: opted out when the visitor (or their browser, through Global Privacy Control) refuses the sale or sharing of their data. Maestra Platform keeps the current consent for every combination of customer, browser, and site. A customer who uses two browsers, or visits two of your sites, has a separate state for each. The state changes only when the choice changes.

​
System actions

Every change adds one of three system actions to the customer’s activity feed: The actions are in the Personal category. They carry these custom fields: The action date is the moment the visitor made the choice, not the moment Maestra Platform received it.

​
Change history

Each change also adds a Consent changed entry to the customer’s change history, with the browser, the site, the source, and the old and new values.

​
Where to see it in the customer card

1

Open the customer

Go to Customer Data Platform → Customers and open the customer’s profile.
2

Open the browsers list

Go to Devices → Browsers. The Tracking consent column shows Granted, Withdrawn, or No data for each browser.
3

Expand a browser

The Tracking consent group shows:
  • Changed — when the visitor made the choice.
  • Source — where the choice came from, for example Platform banner · Shopify, consent.set API, Stored choice, or GPC.
  • Sale of data — Opted out (GPC) or empty.
  • Purposes — the analytics, marketing, preferences, and advertising values.
The consent actions are also in the customer’s activity feed, and each change is in the change history. Two filter conditions are available for customers. To build a filter:
1

Open the filter

Go to Customer Data Platform → Customers and add a condition.
2

Pick the condition

Search for Tracking consent or Sale of data.
3

Pick the value

For example, choose Granted to build a segment of customers you may track on your site.
To find customers who granted tracking but refused the sale of their data, combine Tracking consent is Granted AND Sale of data is Opted out.
For filter basics, see How to Create Filters.

​
Global Privacy Control

Global Privacy Control (GPC) is a browser setting that tells websites not to sell or share the visitor’s data. The tracker reads it from navigator.globalPrivacyControl. When GPC is on and tracking is granted, the tracker sends a separate opt-out with source gpc. The profile gets the Sale of data opt-out (GPC) action, and the browser’s Sale of data shows Opted out (GPC). GPC changes only the sale of data. It doesn’t change tracking consent or the purposes. GPC is sent even when tracking is granted only by the regional default. It isn’t sent again once the sale of data is already known for that browser, and it can’t be recorded for a visitor who hasn’t granted tracking.

​
Anonymous visitors

A visitor who grants consent before you know who they are (before they sign in, subscribe, or place an order) has no customer profile yet. Maestra Platform keeps their choices for 30 days without creating a profile. When the browser is identified within those 30 days, the choices are attached to the customer’s profile in the order the visitor made them, with their original dates. A later choice wins over an earlier one. Choices older than 30 days are dropped.

​
Shopify notes

The Maestra app embed reads the visitor’s answer from Shopify’s Customer Privacy API and passes it to the tracker with provider shopify: Shopify has no separate advertising purpose. Its marketing purpose covers the merchant’s own ads, and its sale-of-data purpose covers sharing with third parties for advertising. That’s why advertising needs both. For PieEye, the embed reads PieEye’s categories with provider pieeye: On Shopify, an answer counts as a choice when the visitor refused analytics or marketing, or accepted both. Anything else is the regional default: it goes to the tracker only as the create default and is never recorded. A choice the visitor made on an earlier page (or at checkout) is recorded too, unless the tracker already remembers a choice in its cookie.

​
Limits

  • Available on request. The feature is turned on per account by the Maestra Platform team.
  • 30 days for anonymous visitors. Choices of a visitor who isn’t identified within 30 days aren’t kept.
  • Browser cookie lifetime. The tracker remembers the choice in the maestraConsent cookie for up to a year, but Safari and other browsers with tracking prevention delete cookies set by scripts after about 7 days. A returning visitor may then see the banner again. Answering it again doesn’t create duplicate actions, because a choice identical to the stored one is ignored. See Cookies and Browser Storage.
  • Sent, not confirmed. The tracker sends a choice and doesn’t wait for an answer. A request lost by the network leaves the choice off the profile.
  • Deleted customers. Deleting a customer deletes their consent records too.