{"version":"2.0.33","anchor":"segment-analytics-telemetry","canonical_anchor":"segment-analytics-telemetry","heading":"Segment Analytics Telemetry","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.0.33\/e\/segment-analytics-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.0.33","markdown":"### Segment Analytics Telemetry\n\n**What:** Dual telemetry system that sends all events to both Statsig and Segment analytics platforms **How to use:**\n\n`# Telemetry is enabled by default and respects existing opt-out mechanisms export DISABLE_TELEMETRY=1 # Disables both Statsig and Segment export CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 # Also disables both` **Details:**\n\n- All existing telemetry events (tool usage, file operations, security checks, etc.) now tracked to Segment in addition to Statsig\n- Uses anonymous IDs by default (`claudecode.v1.{uuid}`), adds user IDs when authenticated with Claude.ai\n- Feature-gated behind `tengu_log_segment_events` Statsig flag for controlled rollout\n- Events batched (15 per flush) and auto-flushed every 10 seconds\n- Graceful shutdown ensures no data loss on exit\n- **Evidence**: Analytics SDK integration at `pF0` (line 19111), tracking function `Os2()` at line 475587, dual-tracking wrapper `j1()` at line 475648, initialization `Ms2` at line 475622"}