Can Lyro rotate a compromised write key?

Yes. Remove Source Write Key revokes an existing write key from a source, which is the action to use for scheduled rotation or after a key has leaked. Delete Source is the heavier option and permanently removes the source itself, so Lyro confirms the source ID before either one runs.

How does Lyro avoid hammering the tracking API?

Batch Segment Analytics Events sends several Identify, Track, Page, Screen, and Group calls in one request instead of one call each. When a conversation produces a burst of events, Lyro collects them and posts them together, which cuts HTTP overhead against your API call allowance.

Can Lyro backfill events with their original timestamps?

Yes. Import Historical Data loads past events in bulk while preserving their original timestamps rather than stamping everything at the moment of import, so a migration or a replay does not distort the time-series that downstream tools build from the same data.

What happens if our workspace is on the EU stack?

Get Destination tries the US public API first and falls back to the EU public API and then the legacy app endpoint. When the fallback returns legacy HTML or fails to parse, it returns a minimal valid envelope, so Lyro reports a partial result rather than treating the destination as missing.

Segment MCP integration

Records conversation events, updates customer traits, links anonymous visitors to known profiles, and reports source and destination delivery health.

Connect Segment See all integrations

17actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Segment identify
Lyro registers a user in Segment and updates their profile traits in real-time. Support teams enrich customer records with new information gathered during conversations.
Segment track event
Lyro records a custom user event through Segment's tracking API. Analytics teams gain visibility into specific customer actions without developers implementing new instrumentation.
Batch segment analytics events
Lyro sends multiple analytics events to Segment in a single batch request. High-volume integrations process events more efficiently with fewer API calls.

See all 17 actions

How businesses use Segment + Lyro

Each card is one request a support team gets, and the Segment actions Lyro runs to close it.

Record what happened in a conversation
Lyro sends a custom event when something worth tracking occurs, sets or updates the traits on that person's profile, and records the page they were on when they asked.
Segment Track EventSegment IdentifySegment Page View
Join an anonymous visitor to a known customer
Lyro aliases the previous anonymous ID onto the identified one, associates that person with their company group and traits, and batches the calls into a single request.
Segment AliasSegment GroupBatch Segment Analytics Events
Answer whether data is actually flowing
Lyro reports the daily API call count per source for a period, pulls the event delivery metrics summary from a destination, and returns that destination's full configuration.
Get Daily Per Source API Calls UsageList Delivery Metrics SummaryGet Destination
Keep sources labelled and configured
Lyro tags a source with the metadata labels your team organises by, updates its settings, and reads back the schema configuration and connected warehouses behind it.
Add Labels to SourceUpdate SourceList Schema Settings in Source

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Segment actions it has and picks the ones a request needs.

01
Connect Segment
Authorize the Segment account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Segment actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Segment · Lyro

Everything else about Segment

Setup, permissions, and the limits of what Lyro can do inside Segment.

Yes. Remove Source Write Key revokes an existing write key from a source, which is the action to use for scheduled rotation or after a key has leaked. Delete Source is the heavier option and permanently removes the source itself, so Lyro confirms the source ID before either one runs.

Every action available in Segment

All 17 actions your agent can call on Segment, straight from the live MCP connection.

Add labels to source
Add existing labels to a Source.
Segment alias
Alias a previous user ID to a new user ID.
Batch segment analytics events
Send multiple analytics calls in a single batch request.
Delete source
Delete a Segment Source.
Get daily per source API calls usage
Fetch daily API call counts per source for a given period.
Get destination
Retrieve a Destination by ID.
Segment group
Associate an identified user with a group via Segment HTTP Tracking API.
Segment identify
Identify a user and set/update traits via Segment HTTP Tracking API.
Import historical data
Import historical data in bulk with support for historical timestamps.
List connected warehouses from source
List warehouses connected to a Source.
List delivery metrics summary from destination
Get an event delivery metrics summary from a Destination.
List schema settings in source
Retrieve schema configuration settings for a Source.
Segment page view
Record a page view via Segment HTTP Tracking API.
Remove source write key
Remove a write key from a Source.
Segment screen event
Record a mobile app screen view.
Segment track event
Record a custom user event via Segment HTTP Tracking API.
Update source
Update a Source's metadata and settings.