Segmentic technical documentation

A task-based map of Segmentic documentation: setup, data collection, engagement, analytics and developer reference.

Segmentic collects product events, builds audiences and delivers messages through the right channel. If you are connecting the service for the first time, begin with the quickstart.

#Three surfaces

Each surface has a distinct key and purpose:

• Ingest: https://in.segmentic.net with a wk_seg_... key, for recording events from a site, app or server
• Management: https://api.segmentic.net with an sk_seg_... key, for managing audiences, campaigns and reports from your backend
• Panel: https://app.segmentic.net with a user account, for configuring and inspecting your workspace

The write key is public on purpose: it is meant to ship inside your own JavaScript. It can write events, register a device, subscribe to browser push and fetch on-site messages. It cannot read a profile and it cannot mint another key. The management key is the opposite: it does whatever its role and permissions allow across the account, and it must never reach a browser. The two prefixes are separate so that a leak report is settled at a glance. A wk_ in a public bundle is working as designed; an sk_ in the same place is an incident.

#Start here

• Quickstart: create a key and record your first event
• Concepts: understand the product's core terms

#Collect data

• Designing events and the event dictionary: choose consistent names and properties
• Instrumentation: place tracking calls at the right point in your product
• Identity: connect anonymous activity to signed-in users
• Web SDK: connect a site or web app
• Android SDK: events, identity, push and in-app messages in an Android app
• Server to server: record authoritative events such as captured payments
• Devices and push: prepare mobile and browser push
• Product catalogue and webhooks: keep data in sync with other services

#Engage customers

• Segments: build audiences from behaviour and traits
• Journeys: run multi-step customer flows
• Transactional messages: send urgent messages safely
• Consent and caps: respect recipient preferences
• In-app messages: banners, modals, surveys and inboxes

#Analyze and export

• Reports and exports: funnels, retention and data files

#Developer reference

• API reference: choose the right host, key and route
• Ingest endpoints and Management API: request and response details
• Errors and limits: build a reliable client
• OpenAPI: generate clients from the machine-readable contract

#Developer tools

• Working with an AI agent: download the complete documentation and use the starter prompt
• The MCP server: let Claude, Codex or Cursor read and act on your account

#Privacy and changes

• Personal data: access, deletion and retention
• Versioning: API compatibility and change notices

#Machine-readable copies

Tools and AI agents can use /llms.txt, /llms-full.txt, /docs-en.md and /docs-fa.md. The OpenAPI document is available at /openapi.json.