Context around Segment’s track use includes references to the track specification, the Pixellint linting tool, and related articles that explain why every call must include a person and an event name, with links and commands for linting (for example, using pixellint validate json @batch.json).

The HTTP API acts as a collector, not a validator; a 200 status only confirms bytes were received, not that the payload conforms to the spec.

Timestamp handling requires ISO 8601; epoch timestamps are invalid, and events can omit a timestamp if Segment will stamp it at processing time.

A common issue is a batched Segment track call that omits the required event name, yet the HTTP response returns 200, causing downstream destinations to miss the event.

Identity is essential: every call must include a userId or anonymousId, otherwise destinations cannot attribute the event; a track with properties or a timestamp without identity isn’t usable for destinations.

Batch processing rules require each row to have a type (identify, track, page, screen, group, or alias), and mixed batches must be linted to enforce correct types per row.

Pixellint validates Segment payloads and flags the error vendor.segment.body.track_requires_an_event_name, with guidance to include the event name and a link to the official track spec.