Identity & runtime

Web Analytics

Name: Nexoxa Bridge
Author: Nexoxa

Self-hosted pageviews from .nexoxa/ JSONL.

The story

These pages use illustrative scenarios to walk through real workbench panels. Sidebar labels, Bridge paths, and connection schemes match the app; characters and timelines are examples for learning.

Marketing asks pageviews — Web Analytics reads .nexoxa/ JSONL on server via @nexoxa/analytics.

Self-hosted, no Google account share.

Bridge path: /server/analytics

Step 1

Read local JSONL

Pageviews spike on /pricing — JSONL parse in panel.
No third-party dashboard login.

Self-hosted pageviews from .nexoxa/ JSONL. /server/analytics.

Step 2

Data stays on server

Compliance likes local-first analytics.
SSH read only.

@nexoxa/analytics format.

Step 3

Pair Speed and SEO

Traffic up but Speed Insights LCP bad — prioritize perf.
Holistic view.

Link Speed Insights and SEO audits.

This panel appears in the Nexoxa Bridge left sidebar after you connect with the matching connection URL. See the connection docs above for postgresql://, ssh://, sftp://, s3://, or smtp:// examples.

Related connections

SSH connection URL