Skip to main content
Segment is your customer data backbone — audiences, traits, events, and identity resolution across every channel. These four jobs connect Segment’s CDP capabilities to Mavera’s surfaces (Focus Groups, Custom Personas, Mave Agent) so your research reflects real behavioral segments, your personas are enriched with computed traits, and your research triggers in real time when user behavior changes.

API Reference Card

All examples use two environment variables: SEGMENT_TOKEN (Management API bearer token with Workspace Owner or appropriate scope) and MAVERA_API_KEY. The Tracking API examples also reference SEGMENT_WRITE_KEY for sending events. Python examples use requests; JavaScript examples use fetch.

Prerequisites

1

Segment workspace with sources

You need an active Segment workspace with at least one source connected and flowing events. Audiences require Segment Engage (formerly Personas).
2

Management API token

Generate an API token in Segment → Settings → Workspace → Access Management → Tokens. Grant Workspace Owner scope or narrow to specific resources.
3

Write Key (for Tracking API)

Find the Write Key in Segment → Sources → your source → Settings → API Keys.
4

Mavera API key

Get your key from Mavera dashboard.
5

Environment variables


Jobs


Rate Limits & Production Notes

Segment’s Management API has per-endpoint rate limits that aren’t always documented. If you hit 429 errors, implement exponential backoff starting at 1 second. The Tracking API’s 1,000/sec limit is generous but applies per-source.
Production checklist:

What’s Next

All Integrations

50+ API integrations with full code

Segment API Docs

Official Segment API reference

Personas API

Full reference for POST /api/v1/personas

Focus Groups API

Full reference for POST /api/v1/focus-groups

Mave Agent

Full reference for POST /api/v1/mave/chat