Tringify uses one set of optional cookie categories wherever a storefront records consent: the CTX consent root in hosted themes, the consent_give hosted action, and app event delivery. The categories are defined by the platform, not per store, and every consent banner offers all of them. Essential storage, such as the cart, checkout, and sign-in, is always allowed and is never offered as a choice.
Categories#
The keys are snake_case everywhere a category is sent or returned as a value.
Key |
Label |
What it allows |
|---|---|---|
|
Analytics |
Measure how the store is used: analytics sessions, referrers and entry pages, and analytics pixels. Without it, activity is still counted, but without a session, device, IP address, or location detail. |
|
Advertising |
Advertising measurement: campaign parameters and ad click identifiers on visits, ad attribution, the advertising browser identifier, and advertising pixels. |
|
Advertising data |
Share the shopper's data with advertising services, such as the signed-in customer's identity sent with events for conversion matching. |
|
Personalized advertising |
Ads personalized for this shopper, such as remarketing audiences built by advertising apps and their pixels. |
|
Personalization |
Personalize the storefront from the shopper's own history, such as recently viewed products shared across a signed-in customer's devices. |
Where the categories appear#
Surface |
How categories appear |
|---|---|
CTX (hosted themes) |
consent.categories lists the categories the visitor granted; consent.available_categories lists the ones the banner offers. Both use snake_case keys. |
Hosted Actions |
consent_give takes a repeated categories field with snake_case keys, or accept_all for every category. consent_withdraw removes every optional category. See Localization and consent. |
App event delivery |
Each delivered event names one category as its consent purpose, and it is delivered only when the visitor granted that category. See Event delivery. |
When visitors are asked#
Merchants set up the banner in Store Admin under Settings > Compliance > Consent Banner. Enable consent banner turns it on; the privacy policy and cookie policy must both be published first. Show in countries chooses where it applies: All visitors, or Selected countries.
Banner setting |
Visitor's country |
Must ask (consent.required) |
Before the visitor chooses |
|---|---|---|---|
Off |
Any |
No |
Every optional category is granted. |
On, All visitors |
Any |
Yes |
No optional category is granted. |
On, Selected countries |
In the list |
Yes |
No optional category is granted. |
On, Selected countries |
Not in the list |
No |
Every optional category is granted. |
On, Selected countries |
Unknown |
Yes |
No optional category is granted. |
The visitor's country is the country detected from the visitor's connection. When it cannot be detected, the storefront uses the shopping country. A visitor's recorded choice always applies, wherever they are: banner settings never widen a saved choice, and a withdrawal stays a withdrawal.
Banner settings in each API#
CTX does not expose the banner's country targeting; consent.required already applies it to the current visitor.
For hosted themes, see Customers, carts, and consent.