Skip to main content
Glyph brings product events, survey responses, and notes into one customer view. You can see recurring pain points, the customers affected, and the source material behind each finding. These docs cover profiles and events sent from your product. Surveys and notes are collected inside Glyph. Events arrive through an SDK or the HTTP API, authenticated with a workspace write key.

​
How events fit in

Every message includes a userId for a known customer. Profiles describe the customer, while events record what they did. Both appear on the customer’s timeline and provide behavioral context for survey responses and notes.

Quickstart

Get a write key, install an SDK, and send your first profile and event.

Set up with AI

Give a coding agent the integration brief and Glyph’s capture rules.

​
Pick your SDK

Browser

@glyphhq/browser — client-side events and page views, via npm or a script tag.

Node.js

@glyphhq/node — server-side events from your backend, API routes, and jobs.

Python

glyphhq — server-side events from Python services, scripts, and pipelines.
All three SDKs implement the same wire contract and delivery model: batching, retry with backoff, and an error callback. See Configuration & delivery for the shared behavior.

​
What to send

Capture events that help explain a customer’s experience: activation, core value, friction, and lifecycle changes. Profile each customer with an email address; use a stable userId as the identity key.

What to capture

A practical guide to choosing profiles, events, and traits worth sending.

​
Guides

Next.js

Client and server wiring for App Router apps, including webhooks.

Backfilling history

Import an existing customer base with real timestamps, safely paced.

Troubleshooting

Work through the common reasons events don’t appear.