Changelog

Notable changes to these docs and the standards they cover, newest first. The Content Telemetry standard is at v1.0.

2026-09

• Content Telemetry v1.0 published on 2 September 2026. v1 documents declare schema_version "1.0", and schemas resolve at contenttelemetry.org/schema/v1/. v0.1 and v1.0 do not interoperate on the wire.
• content_displayed renamed to content_presented; data.display_type becomes data.presentation_type, and the required data.presentation_kind (content or source_reference) says what crossed the presentation boundary.
• The pre-release draft content_reproduced event and the preserved_in_output fingerprint field are not part of v1; v1 defines no output-side reuse reporting. Grounding fingerprints report detection only.
• Retrieval profile's bot_category renamed to purpose, an open enum classifying the access (training, inference, search, advertising); vendor signal mappings move to informative Annex C.
• ip_hash withdrawn from the edge and origin retrieval profiles; asn, asn_org and country remain.
• Manifests gain identifier_schemes (content-owner identifier prefix claims with optional resolution endpoints), telemetry.ctx_resolution (click-token resolution endpoint, agent and platform manifests), and telemetry.coverage (per-event-type coverage declarations: complete, sampled, aggregated, selected).
• Portable character counts: chars_ingested and excerpt_chars count Unicode code points and are comparable across emitters; token counts remain emitter-tokeniser-specific and supplementary.
• terms_ref added: an event can name the governing terms under which it is reported. license_ref no longer asserts the use was licensed - it is the emitter's claim about which grant applied.
• ctx_token values gain the ct_ pattern and an unguessability rule; click-token resolution is narrowed to the click's turn, with per-owner opt-in for contributing sources.
• Event batch delivery (telemetry-event-batch.json) joins session documents and standalone events as the third delivery format. Occurrence boundaries and per-event cardinality are now stated for every core event.

2026-06

• The telemetry standard is published as Content Telemetry v0.1 (preview) (since superseded by v1.0 - see 2026-09 above) - a neutral open standard stewarded by the SPUR Coalition at SPUR-Coalition/telemetry, with schemas resolving at contenttelemetry.org. OpenAttribution participates via public comment and implements the standard; it no longer hosts the wire format. These docs now refer to the standard by its neutral name throughout.
• Public comment window open from 12 June to 10 July 2026; revised versions of the standard and profiles follow by 10 August. File issues on the standard repository.
• The SPUR telemetry profile (publisher accreditation: event-level, real-time, complete delivery to a publisher-designated endpoint) published alongside the standard.
• OpenAttribution's commerce profile published as a draft: ctx_token propagation across click-outs, click manifests, multi-citation attribution.
• The third conformance level is named Citation (previously documented here as "attribution"); display and engagement events are optional lifecycle signals on top of it. A machine-readable manifest schema (manifest.json) now ships with the standard.

2026-05

• Section 8 of the telemetry spec now defines the Manifest - the JSON document a participant publishes at /.well-known/content-telemetry.json to declare who they are, their role, and where telemetry is reported. It lives alongside the event model in the same spec.
• telemetry.conformance_level clarified as emitter-side and informational; content-owner manifests no longer carry it.
• New docs pages: Quickstart, Affiliate and ad networks, Authentication, Glossary, Troubleshooting, Integrations overview, and this changelog.
• Telemetry ingest moved to its own subdomain. Events and sessions now go to telemetry.openattribution.org with flat paths (/events, /sessions/*); reads, identity, delegations, and click tokens stay on api.openattribution.org.
• Telemetry read paths flattened - /api/v1/telemetry/* became /content-owners/* and /agent/*; versioning moved into the event payload. Identity keeps the /api/v1/identity/* prefix.
• Edge emitters now use telemetry:write-scoped content-owner keys; events carry an explicit id.
• Role-aware onboarding: content owners are self-serve; platform and agent access goes through a submit-then-approve flow while the network beds in.
• .well-known guidance aligned with the v0.1 manifest; the manifest unified across roles.
• Click-token lookup documented as two-sided opt-in (share_sessions_via_click_tokens and visible_in_click_token_lookups, both default off).
• Grounding (content_grounded) promoted to a first-class stage; marketplaces guide added; "publisher" replaced with "content owner" throughout.

2026-04

• Telemetry adoption guides published from the spec repo into the docs site.
• Cloudflare integration switched to API-key auth; org_id dropped from the event payload.

2026-03

• Cloudflare integration docs rewritten for edge telemetry - the Worker detects AI crawlers and reports content_retrieved with source_role: edge, no agent cooperation needed.
• Site moved to Cloudflare Pages.

v0.1 - preview specification

First public draft of the telemetry specification: the session and event model, the content stages from retrieval to engagement, source roles, the JSON schemas, the manifest format, and protocol bindings. Since superseded by the neutral Content Telemetry standard, now at v1.0, at SPUR-Coalition/telemetry (see 2026-09 above).