Customer debug
Server-rendered (Liquid)
| customer present | no (logged out OR cache stripped session) |
| customer.id | — |
| customer.email | — |
| customer.tags | (none) |
| customer.b2b? | false |
| has 'scent-society' tag | false |
| localization.country.iso_code | AU |
| localization.market.handle | australia |
| server time (rendered) | 2026-07-23 15:58:18 -0400 |
Client-side (JS)
| client time (now) | — |
| cache age (server vs client) | — |
| /account.js status | checking… |
| /account.js → id | — |
| /account.js → tags | — |
| /account.js → has 'scent-society' | — |
| document.cookie names | — |
Portal API (account.elementbrooklyn.com/api/me)
| /api/me status | checking… |
| /api/me → logged_in | — |
| /api/me → scent_society | — |
How to read this:
The brand is on Shopify New Customer Accounts, so the server-side Liquid
customer object is unreliable and often empty even when you're signed in via the portal — that's expected, not a cache bug. The source of truth for membership is the Portal API section above: logged_in from the portal session cookie, scent_society from element-ops's view of customer tags.
If /api/me returns error: Failed to fetch while you're signed in on account.elementbrooklyn.com, check (a) the portal session cookie has SameSite=None; Secure (cross-origin credentialed fetch otherwise drops it) and (b) CORS allows https://www.elementbrooklyn.com with credentials.
Raw /api/me
loading…
Raw /account.js
loading…
