How sentryco/telemetric works
Main Components
a) Client Application Layer:
• IOS/macOS app integration point
• Main Telemetric interface class
• Event Collector mechanism
b) Core Components:
• Tracker System
• Event Processing
• Identity Management
• Storage & Caching
c) External Systems:
• Google Analytics 4 (GA4) Backend
• Measurement Protocol API
Specific Implementation Details
┌─ Application Layer ─────────────────────┐
• iOS/macOS Client App │
• ┤
• Telemetric Interface │
• (TelemetricKind Protocol) │
• ┤
• Event Management │
• ┌─────────────┐ ┌──────────────┐ │
• Event │ │ Event │ │
• Collector │◄───│ Builder │ │
• ┘ └──────────────┘ │
• ┤
• Core Services │
• ┌─────────────┐ ┌──────────────┐ │
• Tracker │ │ Identity │ │
• Service │ │ Manager │ │
• ┘ └──────────────┘ │
• ┌─────────────┐ ┌──────────────┐ │
• Timing │ │ System │ │
• Tracker │ │ Utils │ │
• ┘ └──────────────┘ │
• ┤
• Storage Layer │
• ┌─────────────┐ ┌──────────────┐ │
• Keychain │ │ UserDefaults │ │
• Storage │ │ Storage │ │
• ┘ └──────────────┘ │
• ┘
• ▼
┌─ External Services ──────────────────────┐
• Google Analytics 4 (GA4) │
• Measurement Protocol API │
• ┘
Important Flows to Highlight
a) Event Flow:
• Event creation
• Batch collection
• Processing
• Transmission to GA4
b) Identity Management Flow:
• Three-tier identity storage (vendor, userDefault, keychain)
• Client ID generation
• Persistence management
Key Technical Details to Note
• Batch processing limits (25 events per request)
• Payload size limits (130kB)
• Data persistence options
• Timing tracking mechanisms