Question 1

Can Ana read Segment Unify profiles?

Accepted Answer

Yes. The Profile API exposes unified identity-resolved profiles and computed traits, and Ana can query them by user ID, external ID, or trait filter. This is powerful for answering questions that need Segment identity resolution on top of warehouse data.

Question 2

Does Ana monitor Segment pipeline health?

Accepted Answer

Yes. The admin API exposes source and destination delivery metrics, error rates, and sync statuses. Ana can surface failing destinations or sources and correlate them with warehouse-measured downstream effects like missing events or stale dashboards.

Question 3

How are Segment tokens secured?

Accepted Answer

Access tokens are encrypted at rest in TextQL's credential vault and injected by our egress proxy at the network layer. Ana's Python sandbox never sees the raw token. Tokens can be rotated at any time from the TextQL admin console without changing prompts.

Question 4

Can I use a scoped Segment token?

Accepted Answer

Yes. Segment lets you create tokens with specific permission sets and workspace scopes. We recommend creating a dedicated read-only token for TextQL. Admins can store multiple tokens and assign them to different user groups for separation of duties.

Question 5

Does Ana see Segment raw events?

Accepted Answer

Segment's Profile API returns aggregated traits rather than raw event streams. For raw events, the best pattern is to have Segment load to your warehouse and let Ana query them there. This keeps raw event queries efficient and centralized.