JSON input
valid
TypeScript output
Paste a Segment track call payload (server-side or warehouse export) and get a TypeScript interface for type, event, userId, properties, context, and integrations.
Segment's track call envelope is well-specified (type, event, userId / anonymousId, properties, context, timestamp, messageId, integrations) but the context block balloons over time — library, page, campaign, app, device, ip, locale, network, os, screen, traits, userAgent, timezone — and the properties block is whatever your application puts in it. For Segment-spec semantic events like Order Completed, the properties shape is loosely standardized across the ecosystem, so a generated TypeScript interface is a good starting point.
Use the result in a server-side analytics-node integration, a Segment Functions destination, a webhook receiver from Segment Connections, or an analyzer that reads the warehouse track table. The generated types let you inline a typed track() wrapper that catches missing properties at compile time before they reach your analytics warehouse.