> ## Documentation Index
> Fetch the complete documentation index at: https://www.glyphhq.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Send customer profiles and product events to Glyph.

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](/docs/reference/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.

<Card title="Quickstart" icon="rocket" href="/docs/quickstart" horizontal>
  Get a write key, install an SDK, and send your first profile and event.
</Card>

<Card title="Set up with AI" icon="wand-magic-sparkles" href="/docs/ai-setup" horizontal>
  Give a coding agent the integration brief and Glyph's capture rules.
</Card>

## Pick your SDK

<Columns cols={3}>
  <Card title="Browser" icon="globe" href="/docs/sdks/browser">
    `@glyphhq/browser` — client-side events and page views, via npm or a script tag.
  </Card>

  <Card title="Node.js" icon="node-js" href="/docs/sdks/node">
    `@glyphhq/node` — server-side events from your backend, API routes, and jobs.
  </Card>

  <Card title="Python" icon="python" href="/docs/sdks/python">
    `glyphhq` — server-side events from Python services, scripts, and pipelines.
  </Card>
</Columns>

All three SDKs implement the same wire contract and delivery model: batching, retry with backoff, and an error callback. See [Configuration & delivery](/docs/reference/configuration) 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.

<Card title="What to capture" icon="list-check" href="/docs/guides/what-to-capture" horizontal>
  A practical guide to choosing profiles, events, and traits worth sending.
</Card>

## Guides

<Columns cols={3}>
  <Card title="Next.js" icon="layer-group" href="/docs/guides/nextjs">
    Client and server wiring for App Router apps, including webhooks.
  </Card>

  <Card title="Backfilling history" icon="clock-rotate-left" href="/docs/guides/backfill">
    Import an existing customer base with real timestamps, safely paced.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/docs/guides/troubleshooting">
    Work through the common reasons events don't appear.
  </Card>
</Columns>