API Status & Documentation

Universal Tracking System Endpoints

System Operational

Database

ClickHouse DB

Connected

Ingestion API

/track endpoint

Active & Receiving

CAPI Forwarding

Meta & Google

Synchronized

Attribution journey

ClickHouse multi-touch

Visitor and session IDs are stored as strings (tracker-generated). Touch types include page views, scroll depth, form submits, and CTA clicks — surfaced on the Attribution page.

Available Endpoints

POSThttps://analytics.getsolarmax.com/track

Main ingestion endpoint for the Universal Tracking System (UTS). Receives telemetry data from the tracker script. Include visitor_id and session_id as stable strings so events can be joined in ClickHouse attribution tables.

Payload Example:

{
  "site_domain": "getsolarmax.com",
  "event_name": "PageView",
  "event_category": "System",
  "page_url": "https://getsolarmax.com/",
  "visitor_id": "uts-vid-string-or-uuid",
  "session_id": "uts-sid-string-or-uuid",
  "attribution": {
    "utm_source": "google",
    "utm_medium": "cpc"
  }
}
POSThttps://analytics.getsolarmax.com/api/attribution/offline

Offline conversion webhook. Send CRM data here (e.g. from GoHighLevel) to match with previous web touchpoints.

Payload Example:

{
  "email": "customer@example.com",
  "phone": "+1234567890",
  "conversion_type": "deal_won",
  "conversion_value": 5000.00
}
GET/api/events

Dashboard internal API to fetch recent events from ClickHouse DB for UI rendering.

Query: timeRange (e.g., today_est)Query: domain
PROXY/api/admin/ghl-locations-config · /api/admin/ghl-sync-form-submissions · /api/admin/ghl-dashboard-meta · /api/admin/repush

These Next.js routes forward to the ingestion API using UTS_INGESTION_URL and ADMIN_MASTER_KEY from the dashboard environment (the browser never sees the key). Used for saving GHL Private Integration tokens, triggering form-submission sync, fetching sync status/logs, and Meta CAPI repush.