Product and documentation changelog

This page records material changes to GraphJSON’s product documentation, public developer experience, and customer-facing operating guidance from July 26, 2026 forward.

For endpoint compatibility, breaking-change notices, and machine-contract changes, use the API compatibility and changelog. A feature appearing here does not change the API contract unless the API changelog says so.

July 26, 2026#

Operational analytics, data architecture, and customer workflows#

Type: Documentation expansion

Added twelve production guides that close the next set of gaps between an initial analytics implementation and a system that can be operated, changed, recovered, and exposed safely:

• Structured application logs, including a stable log schema, severity, correlation, privacy, delivery, sampling, and investigations
• Native Data API frontend, including a server-owned report registry, tenant-safe caching, response normalization, complete React states, accessibility, and tests
• Event-time state and reference data, covering transitions, point-in-time lookups, snapshots, corrections, and current-versus-historical semantics
• Journey and path analysis, including ordered paths, noise removal, drop-off, time-to-convert, maturity windows, and funnel promotion
• Metric and SQL tests in CI, with source-controlled definitions, fixtures, exact expectations, boundary cases, and a staging smoke-test pattern
• Analytics asset change management, covering dependency inventory, change classes, parallel migration, reconciliation, cutover, and rollback
• Collection architecture at scale, including ownership, sensitivity, environment, retention, volume, tenant, and migration boundaries
• Durable raw archive and dual-write, using one canonical outbox, independently checkpointed consumers, manifests, reconciliation, and tested restore
• SLOs, error budgets, and alerts, with explicit native-alert limits, burn-rate measurements, shared-fate protection, and independent paging
• Public metrics and status dashboard, including publication contracts, sanitized snapshots, freshness states, accessible delivery, and incident fallback
• Customer health and account scoring, with interpretable components, cold-start behavior, validation, reason codes, and versioned rollout
• Customer support account timelines, including event allowlists, server authorization, correlation, pagination, redaction, and investigation auditing

The documentation index and advanced learning paths now route readers to these guides by task. No ingestion endpoint or authentication behavior changed as part of this documentation release.

Production analytics and integration playbooks#

Type: Documentation expansion

Added production guidance for the parts of an analytics system that become important after the first event and chart:

• Executable event contracts, including schemas, fixtures, compatibility rules, and CI enforcement
• High-volume ingestion and backfills, including resumability, throttling, reconciliation, and abort criteria
• Identity stitching and account lifecycle, including anonymous-to-known transitions, account switching, merges, and deletion
• Bad-data containment, correction, and replay
• Product metrics cookbook, including activity, activation, adoption, retention, resurrection, and revenue retention
• an expanded experimentation and funnel guide covering assignment, exposure, sample-ratio mismatch, power, guardrails, and rollout decisions
• File, database, and object-storage migrations
• Operating managed integrations
• production references for Next.js and Node, Python, Rails, and Go
• Accessible and localized embedded analytics

This release also added exact Data API response contracts, response examples, and validation patterns for native embedded-analytics clients.

No ingestion endpoint or authentication behavior changed as part of this documentation release.

Public developer and operational reference#

Type: Documentation and tooling

Published or substantially expanded:

• the OpenAPI and Postman toolchain
• API compatibility policy
• service behavior and operational expectations
• service status and incident communication
• security review and shared responsibility
• guides for event governance, delivery, browser/mobile collection, SQL operations, migrations, privacy, billing, and account recovery

The documentation is now served on graphjson.com/docs/... so product, API, and operational guidance share one canonical domain.

Documentation lifecycle established#

Type: Documentation policy

GraphJSON documentation now carries a review month and follows the lifecycle below. Earlier product and documentation history has not been reconstructed, so the absence of an older entry is not evidence that no change occurred.

How to read an entry#

Each entry should identify:

• Date: when the change became available or the guidance became canonical
• Type: product, API, documentation, policy, correction, deprecation, or developer tooling
• Scope: affected workflows, endpoints, roles, or deployment environments
• Action: what a customer must do, or an explicit statement that no action is required
• Links: the canonical instructions and any migration path

When a change is corrected after publication, the entry should retain the original decision and add the correction date rather than silently rewriting history.

Documentation lifecycle#

GraphJSON treats documentation as part of the product:

1. A feature or behavior change identifies its affected documentation during planning.
2. Public guidance is updated before or with customer availability.
3. Examples are checked against the current request and response contracts.
4. High-risk pages are reviewed after material API, security, billing, privacy, or operational changes.
5. A page’s last_reviewed month means it was checked for current behavior; it is not the original publication date.
6. Superseded guidance is redirected or marked with a replacement instead of being left ambiguous.

The current public documentation does not yet offer an automated changelog subscription. Teams with a business-critical integration should maintain a support contact with GraphJSON and review the API changelog before integration upgrades.

Report a gap or correction#

If the product behaves differently from the documentation, email hi@graphjson.com with:

• the affected page
• the exact step, request, or response
• approximate time and time zone
• collection or report name, when relevant
• a redacted error message or screenshot

Never send an API key, complete embed URL, payment data, or an unredacted customer payload.