NewJobs: scheduled actions created from chat, personal or shared.Learn more

Segment + Memtro

Ask what a customer did and where your event data flows.

Connect Twilio Segment with a read-only Public API token to see your sources, destinations, warehouse syncs and tracking plans. Add your Unify Space ID and a Profile API token and Memtro can look up any customer's traits, identifiers and recent events by user id, email or anonymous id.

What you can do with Segment in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Segment tool, reads what it needs, and answers with the source cited.

01

Support with context

An agent asks about a customer before a call: Memtro pulls their plan, company and last events from Unify so the conversation starts informed.

02

Data governance checks

Before launching a feature, the team checks the tracking plan to confirm the new event and its required properties already exist and which destinations will receive it.

  • Workspace, sources and their labels and status
  • Destinations connected to each source and warehouse syncs
  • Tracking plan events and the properties they expect
  • Customer profile traits and merged identifiers (Unify)
  • A customer's recent events with properties (last ~14 days)

Ask it like this

Questions people ask once Segment is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.

  • ›What did jane@acme.com do in the product this week?
  • ›Which destinations receive data from the iOS source?
  • ›Do we have a tracking plan rule for Order Completed and which properties are required?
  • ›Is the Snowflake warehouse sync enabled?

Where it fits

Teams that get the most from Segment in Memtro, with the rest of their stack attached.

Better together

A record in Segment is rarely the whole story. Connect the systems that hold the rest and the agent cross-references them by default, then remembers what it learned so the next question starts further along.

Also in Analytics

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

How to connect

  1. 01In Segment go to Settings → Workspace settings → Access Management → Tokens and create a Read-only Public API token.
  2. 02Optionally open Unify → Unify settings → API access and copy the Space ID and an access token.
  3. 03In Memtro add a Segment connection, paste the token (and the Unify fields), set region to eu if your workspace is in the EU, and test.
Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Segment tools are the same everywhere.

Clients and agents →

Questions

Can Memtro change anything in Segment?
No. The Segment connector is read-only: every tool reads, searches or lists. Nothing is created, sent, updated or deleted, and the credentials you give it should be read-only too.
Who can use a Segment connection?
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Does Memtro store my Segment data?
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
How do I connect Segment?
API key. In Segment go to Settings → Workspace settings → Access Management → Tokens and create a Read-only Public API token.

Connect Segment in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.