See the agents on your store, exactly.
Install Parlox on your store, send it your sales, and see exactly what it collects, where it is kept and how it is secured.
Get started
- How Parlox worksAI agents reach a store in two ways, and each is seen by a different part of Parlox.
- Quick startAdd a site, install the browser part and the server part, and see your first agent visit.
- Choosing an install routeWhich install fits your store: the wizard, the npm packages, the pinned tag or the HTTP call.
Install
- The npm package@parlox/browser for sites with a build step: React, Next.js, Vue and any bundler.
- The pinned script tagOne tag for Shopify themes, WordPress, plain HTML and Google Tag Manager, pinned with its integrity hash.
- The install wizardnpx parlox init: the stacks it covers, every change shown as a diff first, and how to undo it.
- The server part@parlox/server reports the AI fetchers and crawlers that never run JavaScript, on any stack.
- Shopify checkoutShopify runs no theme scripts on checkout, so checkout events come through a custom pixel.
- Verifying the domainProve you own the site's domain with the tag, a token your server answers, or a DNS record.
Sales
- Cart and checkout eventsHow a visit's product views, cart and checkout reach Parlox, and how much each source is trusted.
- Purchases from the serverThe purchase of record comes from your server: purchase() in Node, or one HTTP call from any stack.
- People sent by AI assistantsHow Parlox knows a person arrived from an AI assistant, and the visits it cannot know about.
How it works
- How a visitor is identifiedEvery label says what it rests on: verified, declared or inferred.
- Visits and outcomesHow requests become visits, and how a closed visit gets one outcome from recorded facts.
- Agent recordingsVisits by automated browsers are recorded as a masked replay of your page. People's are not, with one edge case.
- The control mapWhat each button on your site means, learned from what followed a click, never from its words.
Data and security
- What is collectedExactly what the browser part and the server part send, and what they never read.
- MaskingWhat is masked before anything leaves the page, and the attributes that change it.
- ConsentKeep Parlox off until your consent tool says yes, and stop it when consent is withdrawn.
- SecurityPinned and hashed releases, open source with provenance, narrow keys, and code that fails safe.
- Where data lives and how longThe regions that store and process your data, and how long visits and recordings are kept.
- Which features use an AI modelThe features that send data to an AI model, what they send, and on which sites they run.
Reference
- Browser API@parlox/browser: init and its options, track, consent and sessionId, and the tag's attributes.
- Server API@parlox/server: the adapters, createParlox, purchase, ucp, flush, and every option.
- Keys and accessThe public key, the three kinds of secret key, what each can reach, and how to replace one.
- Content-Security-PolicyThe directives each install route needs on a site with a Content-Security-Policy.
- LimitsRequest sizes, batch sizes and the other fixed bounds of the gateway and the SDKs.