slug: segment
provider: Twilio Segment
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 7
edges:
- tag: Track
  spec_file: segment-track-api-openapi.yml
  capability_id: BC-4280.10
  capability_id_l1: BC-4280
  capability_name: Product Telemetry Instrumentation
  confidence: 0.75
  evidence: POST /track  "Track an event"; schema TrackCall; "record analytics data from any website or
    application"
  reason: The track call ingests product usage events from client and server runtimes, which is precisely
    product telemetry instrumentation rather than any domain-specific business process.
- tag: Events
  spec_file: segment-events-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: GET /collections/users/profiles/{externalId}/events  getUserEvents  Get user events; 'read
    user-level and account-level customer data from Segment Unify ... including external IDs, traits,
    and events'
  reason: Reads the unified customer profile's event history by external ID — retrieval from the unified
    customer record used for real-time personalisation. Customer Data Management is the best fit; some
    ambiguity with usage analytics keeps this below 0.8.
- tag: External IDs
  spec_file: segment-external-ids-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: GET /collections/users/profiles/{externalId}/external_ids  Get user external IDs; "read user-level
    and account-level customer data from Segment Unify ... including external IDs, traits"
  reason: Reading the external identifiers attached to a unified customer profile is identity resolution
    over the customer golden record, i.e. customer data management; it is not generic IT plumbing because
    the object is the customer profile itself.
- tag: Page
  spec_file: segment-page-api-openapi.yml
  capability_id: BC-4280.10
  capability_id_l1: BC-4280
  capability_name: Product Telemetry Instrumentation
  confidence: 0.7
  evidence: POST /page  "Record a page view"; schema PageCall; "record analytics data from any website
    or application"
  reason: Capturing page-view events from client/server runtimes is product usage telemetry instrumentation;
    the tag is an event type, not a pagination control.
- tag: Screen
  spec_file: segment-screen-api-openapi.yml
  capability_id: BC-4280.10
  capability_id_l1: BC-4280
  capability_name: Product Telemetry Instrumentation
  confidence: 0.7
  evidence: POST /screen  "Record a screen view"; schema ScreenCall
  reason: Recording mobile screen-view events against a defined event schema is product usage telemetry
    instrumentation.
- tag: Tracking Plans
  spec_file: segment-tracking-plans-api-openapi.yml
  capability_id: BC-4280.20
  capability_id_l1: BC-4280
  capability_name: Telemetry Quality & Governance
  confidence: 0.7
  evidence: 'POST /tracking-plans createTrackingPlan; schemas: TrackingPlan, TrackingPlanRule — within
    a platform for ''event collection (the HTTP Tracking API with identify, track, page, screen...)'''
  reason: Segment tracking plans define and enforce the event schemas that product/customer telemetry
    must conform to, which matches schema governance of usage telemetry rather than any analytics-consumption
    capability. Confidence held below high because the operations are plain CRUD and the governance intent
    is inferred from the resource ('TrackingPlanRule') rather than stated.
- tag: Traits
  spec_file: segment-traits-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: '''provides endpoints to read user-level and account-level customer data from Segment Unify
    ... including external IDs, traits, and events that make up a user''s journey''; GET /collections/users/profiles/{externalId}/traits'
  reason: Reads the unified customer profile (external IDs and traits) — i.e. consumption of a customer
    golden record / identity-resolved profile, which is Customer Data Management. Not segmentation, since
    no segment definition operations exist here.