Common questions.
Quick answers about scope, current status, data handling, and where Cartograph fits relative to your existing stack.
Frequently asked
What is Unidentified Traffic?+
Unidentified Traffic is the planned percentage of eligible storefront request events, observed through complete server/CDN/origin log coverage, that lack sufficient deterministic evidence for one of the four non-`unclassified` v0.1 labels. It is a request-level share of traffic we could not label — not human share, agent share, readiness, conversion impact, or economic loss.
What does Cartograph observe?+
Cartograph does not currently operate a public automated scanner. The website and early-access form do not scan your storefront. If a read-only assessment capability is activated in future, it is planned to evaluate only public, non-authenticated commerce surfaces after merchant authorization, using read-only `GET` and `HEAD` requests. It is not planned to log in, create accounts, submit forms, mutate carts, initiate checkout, enter payment data, place orders, test security controls, or bypass access controls.
Is Cartograph a bot detector, PIM, analytics tool, or PSP?+
No. Cartograph is being built as the agent-commerce evidence layer across them. The planned integration connects evidence from those systems without replacing them.
Who is Cartograph for?+
Ecommerce, analytics, product data, security, and payments teams at merchants preparing for AI-mediated shopping.
Does observing my store affect the live experience?+
Submitting a form does not trigger observation or automated requests against your storefront. Any future assessment would require merchant authorization and would follow the planned read-only boundary: only public, non-authenticated commerce surfaces, using read-only `GET` and `HEAD` requests, with no logging in, account creation, form submission, cart mutation, checkout initiation, payment data entry, order placement, security-control testing, or access-control bypass.
Will Cartograph ever exercise cart or checkout directly?+
Authorized diagnostics are planned to exercise selected cart and checkout steps in merchant-approved environments. Merchant authority would be separately verified. Staging or another merchant-approved test environment is preferred; production requires separate explicit authorization. Diagnostics stop before authentication, payment submission, order placement, or any irreversible action. Synthetic evidence remains separate from merchant traffic metrics. Nothing here implies current availability or counsel clearance.
How do you handle our data?+
We use the information you intentionally submit through the website, and data from any service you explicitly connect, to evaluate your request and follow up about it. We do not sell merchant data. Any aggregate benchmarks we publish in future will be anonymized. See the Privacy page for details.
Can you guarantee AI agents will choose our store?+
No. Cartograph is being built to document merchant-side evidence about named surfaces and exact milestones. It cannot guarantee or infer whether an external model will understand, prefer, recommend, or choose a merchant.