← JADE DETAIL

What this shop measures

What JADE DETAIL counts, what it keeps in your browser, and what it sends to anyone else. Every value below is read from the shop's own switches when this page is served — nobody writes or edits it by hand.

Counted

Visit counting: on. Every page of this shop is counted on the server as it is served — no script of ours runs on the page to count you — except on a device that has opted out (ln_noatlas, below).

Visitor counts: off. Visitor counts are off for this shop, so no visitor row is stored: pages are counted as aggregate totals only.

Furthest room remembered: off. Visitor counts are off, so no furthest room is kept: there is no visitor row to keep it on.

Remember what brought a visitor (ln_touch): off. The visitor-cookie switch is off for this shop, so no ln_touch cookie is set for a tagged arrival and nothing is attached to an order.

Counted in aggregate: Country, Region, City, Device class, Browser, Operating system, Language, Page, Referrer host, Serving host, Campaign source, Campaign medium, Campaign name, Automated traffic.

Kept in your browser

ln_touch — not set: the visitor-cookie switch is off for this shop, so no campaign cookie is set for a tagged arrival.

ln_bag_jade-detail — set when you put something in the bag; lasts 7 days; holds the bag itself.

ln_cust_jade-detail — not set: this shop has no customer sign-in, so there is no session cookie to set.

ln_intent_jade-detail — not set: this shop has no customer accounts, so no account form sets it.

ln_fused_jade-detail — set when you check out a booking; lasts 1 hour; holds the booking that checkout is putting through.

ln_noatlas — set when you choose to keep this device out of the counts; lasts 730 days, or until you opt back in; holds a flag.

Ad pixels

Ad pixels: off. This shop runs no ad pixels. No ad network's script is on its pages.

Other code in the page head: off.

Told whether you bought: off.

Meta Conversions API: off. The Ad pixels module is off, so no paid order is reported to Meta from our server.

How long it is kept

Visitor rows: no period is set. No visitor retention period is set, so visitor pseudonym rows are not deleted on a schedule.

Aggregate counters — views per day and the dimension totals above — carry no visitor, and no retention period deletes them: a shop's totals outlive the visitor rows that fed them.

AI agents

AI agent reads: A read by software with no key is counted per door per day. The row is a shop, a day, a kind of counter, a door and a count: there is no visitor, address, user-agent or key in it, so no counter here can be tied to a person or joined across days. It counts keyless calls, not verified AI agents — any caller that names this shop's slug raises the count, so read it as activity on the shop's doors rather than as a roll of machines.

AI agent orders and holds: When an AI agent places an order or opens a booking hold through the crypto checkout, that order keeps one word for it and one for the family of AI client that asked (claude, chatgpt, grok, opencode, other). Orders and holds an AI agent placed through the crypto checkout are counted; an AI agent that pays by card is not counted yet, so the figures undercount. An order a person places gains nothing, and no key, session or address of the agent's is stored. The shop's totals over those orders are its own record, which it can already read one order at a time, and the sales figure is before fees; the per-family breakdown is withheld whole unless every family it shows covers at least five orders and either no completions or at least five of them, and subtracting those from the totals leaves nothing under five.

Families of AI client this shop can name: claude, chatgpt, grok, opencode, other.

Fields kept for this: agent_reads.tenant_id (which of this shop's doors was read — the shop, never the caller); agent_reads.day (the day a keyless read happened — a date, never a time and never who read); agent_reads.dim (which kind of counter the row is; it is `door` today, so every row here counts a door); agent_reads.key (the door itself, as a tool's name (e.g. `shop_lookup`) — the value of the key where the dimension is a door, never a caller); agent_reads.hits (how many times that door was read that day, as one counter); purchases.placed (the order's own word for who placed it: an AI agent, or nothing when a person did); purchases.agent_family (which family of AI client placed an agent's order); bookings.placed (the same word on the booking a deposit hold rides); bookings.agent_family (which family of AI client opened a booking hold).

Where a sale came from

The arrival word: With visitor counts off, no arrival word is kept at all: there is no visitor row to keep it on, so a sale reads 'not credited' rather than a guessed channel.

The word on an order: A paid order keeps one word for where it came from, decided when it is made: an AI agent that placed it, a letter its own address was sent before it paid, the campaign tags it arrived with, or the day's arrival word above copied at checkout. The last one is copied as a word and the visitor handle is never stored on the order, so an order can name a channel and never a visitor. With visitor counts off, the first three still credit and everything else reads 'not credited'. The arrival word is copied only where the referrer dimension is on as well: with it off no host is collected, so nothing is copied and the same three are what credit.

Earnings by country: Earnings per country are counted from the address the buyer typed on their own order — the same address a parcel needs — and never from an IP. A country with fewer than five orders is hidden, and the whole country table is withheld when subtracting the shown rows and the orders that gave no address from a total would give a hidden one away.

Fields kept for this: page_visitors.channel (the first way that day's visit arrived, as one of search, social, ai, link or direct — a group of referring hosts, never the host and never the full address); purchases.day_channel (the same one word copied onto the order at checkout, so the shop can say which arrival paid; the handle itself is never copied); purchases.ship_to (the address the buyer typed to have a parcel sent, and the only source of the country in the earnings table — never an IP).

Limits, said plainly

Visitor counts are off, so automated traffic is not separated from people in the totals: the machine check runs only with that switch on.

The counters are totals: there is no visitor profile to look at, hand over or delete, and no visitor counter is keyed to a person.

The same record as JSON — This page and the JSON file are generated from one object, so they cannot disagree. The file is public and needs no key.