Built to be read, measured and wired in.

What it does

What AI agents can read

• /llms.txt lists published entries, up to 500, each with its Markdown copy, and leaves out what you hide from search.
• Those pages and posts have Markdown copies at /content/pages/<slug>.md or /content/posts/<slug>.md. /content/index.md lists them, and /sitemap.md maps the site in Markdown.
• /content/jsonld.json holds validated schema.org data for those entries. /content/openapi.json describes these read-only files in the OpenAPI format. /content/mcp.json describes the site's resources for agents that speak the Model Context Protocol. /content/validate.json compares what was exported with the site's own facts.
• All of it is read-only, and published content only. A members-only article's body is cut from these files.
• A members-only page's body is cut from these files too. Coming soon.
• Which agents may read, and whether they may train on what they read, is the site's own bot policy, changed behind a card.

Events from your code

• window.praxis.track(type, props) sends an event from your own code.
• The type starts with a lowercase letter and continues with 2 to 63 lowercase letters, digits or underscores. The props are a plain object; anything else is sent as an empty one. A call whose type breaks the rule is ignored.
• Wherever the measurement script runs, it is defined, and it checks the visitor's consent on every call. When analytics is not allowed, it does nothing, quietly; it never throws into your code.
• A visitor who has refused analytics, or whose browser sends Global Privacy Control, gets no measurement script at all on a page without your own page scripts, so call it guarded, as below.
• A type that arrives without a definition waits on Insights › Events & Capture › "Needs review" until someone defines it.
• Each page has an event budget. Past it, events are not sent, the browser console says "Praxis analytics: this page reached its event budget; further events are not sent.", and the drops are counted on "Capture health".
• window.praxis.on("capture", handler) lets your code see every event as the page sends it, so your own tag manager or consent tool can mirror it. A handler that throws never breaks capture.

// Count a quote request. Quietly does nothing until the visitor allows analytics.
window.praxis?.track?.("quote_requested", { service: "roof_repair", value: 1200 });

// See every event that leaves the page, for your own tag manager.
window.praxis?.on?.("capture", (event) => {
  // event.type and event.props, exactly as they were sent
});

Identity

• When your own sign-in succeeds, a call from your page to /api/dxp/identity/link with the account id joins this browser to a person. A call to /api/dxp/identity/detach takes it off again, and the next page load gives the browser a fresh anonymous identity.
• The visitor id itself lives in a cookie that page code cannot read. The call sends your account id, never the visitor id, and the server decides which browser is speaking.
• Whether the account id is kept follows the site's counting policy and the visitor's saved consent, decided on the server, and a browser that sends Global Privacy Control cannot save that consent. Wherever the measurement script runs, it adds praxis.identify and praxis.logout, which make these two calls.
• On the person's record in Privacy & Data › Visitor Data, the "Identity" tab shows every browser joined to them, with "Take browser off this person".

// After your own sign-in succeeds
fetch("/api/dxp/identity/link", { method: "POST", headers: { "content-type": "application/json" }, body: JSON.stringify({ accountId: "account-id-from-your-system" }) });

// When the person signs out
fetch("/api/dxp/identity/detach", { method: "POST" });

• Your site gets its own identity secret, stored encrypted, the first time one of its pages signs the link for a visitor signed in to the site. From then on, the link refuses a call without that signature. Until then, it trusts the account id your page sends, so call it only from a signed-in session that your own server vouches for.

The consent signal for your tags

• window.praxis.consent.get() returns the visitor's current choices. subscribe(handler) hands you the current state at once, then every change, and returns a function that stops it. update(decisions) records a choice made in your own interface and resolves with the new state.
• Each change also reaches the dataLayer as a praxis_consent_change event, and the window as a praxis:consent-change event.
• The state holds what the visitor chose for each purpose (analytics, personalization and marketing), what is in effect, the regime, whether Global Privacy Control was sent, the policy version, where each choice came from, and a sequence number.
• This runtime is installed in the page's head before any of your entries, so your code always finds it.
• A consent tool of your own can tell the page it is ready with signalReady(id) on window.praxis.integrations. If it does not answer in time, the native notice is shown instead; the timeout never changes anyone's consent.

const now = window.praxis.consent.get();
if (now.effective.marketing) { /* load your marketing tag */ }

window.praxis.consent.subscribe((state) => {
  if (state.gpc) { /* the browser sent Global Privacy Control */ }
});

// In a tag manager, listen for the dataLayer event:
// { event: "praxis_consent_change", praxisConsent: state }

Data out

• Exports. Privacy & Data › Exports › "Export a range" writes events, decisions, goals, audience transitions, audiences, profiles, consent and daily rollups as gzipped NDJSON, with a manifest. "Run history" keeps every run, with its downloads and a zip of the whole run, and "Warehouse ingestion" gives recipes for DuckDB, BigQuery and Snowflake.
• Where they land. In the platform's own export storage, under your site's own folder.
• On a schedule. Daily, on chosen weekdays, or monthly. Scheduled exports are available on request.
• One person's data. "Export this visitor's data" on the person's record.
• Everything else that downloads. Form submissions as CSV, up to 1,000 rows; orders, up to 5,000; the copilot's "Activity" as CSV or JSON; your account's Security log as CSV, the newest 10,000 rows; and EmDash's Site transfer, the site as one archive.

Your team's directory

• SCIM. Mint a token on your account's Security tab, shown once, and your directory can add team members and switch them on or off.