--- name: product-analytics-integration description: Enrich support tickets with real-time customer product usage data including feature adoption, session replays, error logs, and behavioral analytics for better context-aware support. Use when integrating product analytics into support platform, adding usage data to tickets, enabling session replay for agents, correlating product errors with support tickets, or building usage-based support workflows. Triggers on phrases like "product analytics integration", "usage data in support", "session replay", "behavioral analytics", "Mixpanel integration", "Amplitude support", "product usage context", "feature adoption tracking". --- # Product Analytics Integration Enrich support tickets with real-time customer product usage data, enabling agents to understand exactly what customers are doing in the product before responding. ## Workflow ### 1. Usage Data Collection and Ticket Enrichment 1. **Real-time usage data sidebar**: ``` PRODUCT USAGE CONTEXT — Customer: Acme Corp (Enterprise) ========================================================= USAGE SNAPSHOT (Last 7 Days): Last login: 2 hours ago (user: john@acme.com) Active users this week: 23 of 45 licensed (51.1%) Sessions this week: 187 (avg 12.5/session — normal baseline: 14.2) Feature adoption: 8 of 12 core features active (66.7%) FEATURE USAGE BREAKDOWN: Feature | Used | Users | Frequency | Health ----------------------|------|-------|-----------|------- Dashboard | ✅ | 22 | 187/day | ✓ Healthy Reports | ✅ | 18 | 142/day | ✓ Healthy API Integrations | ✅ | 15 | 89/day | ⚠ Below baseline (was 120/day) Data Export | ✅ | 12 | 34/day | ✓ Healthy Team Collaboration | ✅ | 20 | 156/day | ✓ Healthy Automated Workflows | ✅ | 8 | 23/day | ⚠ New feature, adoption low Custom Dashboards | ✅ | 5 | 12/day | ⚠ Below expected for Enterprise Alerting | ✅ | 14 | 67/day | ✓ Healthy SSO | ✅ | 45 | active | ✓ Healthy Billing Module | ❌ | 0 | never | ⚠ Not activated (Enterprise feature) Audit Log | ❌ | 0 | never | ⚠ Not activated (Enterprise feature) Webhooks | ❌ | 0 | never | ⚠ Not activated (Enterprise feature) RECENT ERRORS (Last 24 Hours): Error | Occurrences | First Seen | Users Affected ------------------------------|-------------|------------|--------------- API rate limit exceeded | 23 | 14:30 UTC | 3 Webhook delivery failed | 8 | 11:15 UTC | 2 Report generation timeout | 5 | 09:45 UTC | 2 RECENT SESSION HIGHLIGHTS: 2 hours ago: john@acme.com — Attempted API integration setup, failed at step 3 4 hours ago: jane@acme.com — Created 3 reports, all generated successfully 6 hours ago: john@acme.com — Tried to configure webhooks, encountered error TRENDS (Last 30 Days): Overall usage: ↗ +8% (improving) Active users: ↘ -2% (slight decline) Error rate: ↗ +15% (investigate — correlates with ticket volume increase) ``` 2. **Session replay integration**: - Agent clicks "View Session Replay" → loads 5-minute video of customer's product session - Shows exact pages visited, clicks, errors encountered, mouse movements - Filter by: user, time range, error events, specific features - Privacy: PII automatically blurred (emails, names, sensitive data masked) - Agent uses session replay to understand exact customer pain point - Resolution: Agent can guide customer past exact failure point 3. **Error correlation engine**: - Auto-match product errors to support tickets by: user, timestamp, feature - "3 customers reporting API errors → 12 API rate limit errors in last 2 hours" - Alert: Correlated error spike → potential outage or bug - Root cause visibility: Agent sees error logs alongside customer complaint ### 2. Proactive Support Triggers from Usage Data 1. **Usage anomaly detection**: - Customer login frequency dropped 50% vs baseline → trigger re-engagement - Feature abandonment: Started setup wizard but didn't complete → send help article - Error rate spike: User generating 3x normal errors → proactive outreach - Usage approaching limits: API calls at 80% of plan limit → notify before throttling 2. **Onboarding progress monitoring**: - New customer hasn't completed setup after 3 days → trigger onboarding help - Team members not activated (23 of 45 licensed) → suggest activation campaign - Core feature not used after 7 days → send tutorial and offer demo 3. **Expansion opportunity identification**: - Customer using all features in current plan → ready for upgrade - Hitting usage limits regularly → plan too small - Requesting features only available in higher tier → expansion signal - Team growing faster than licenses → seat expansion needed ### 3. Agent Workflow Integration 1. **First ticket interaction**: - Agent opens ticket → usage sidebar auto-loads (2-second load time) - Highlighted context: "Customer last used API Integrations 2 hours ago, encountered rate limit error" - Suggested resolution: Link to "API Rate Limits Explained" article - Agent doesn't need to ask customer what they were doing 2. **Multi-ticket customer context**: - Customer has 3 open tickets → all enriched with same usage data - Pattern detection: "Customer's tickets correlate with API usage errors" - Root cause hypothesis: API misconfiguration causing multiple issues - Resolution strategy: Fix root cause → resolve all 3 tickets 3. **Post-resolution tracking**: - After ticket resolved, monitor usage for 7 days - Verify: Error rate decreased, feature usage resumed - If issue recurs → auto-flag for follow-up - If resolved → update customer health score upward ## Templates & Frameworks ### Product Analytics Integration Dashboard ``` PRODUCT ANALYTICS INTEGRATION DASHBOARD — January 2026 ======================================================= INTEGRATION STATUS: Mixpanel connection: ✅ Active (last synced: 30 seconds ago) Amplitude connection: ✅ Active (last synced: 45 seconds ago) Session replay (FullStory): ✅ Active (1,240 sessions captured today) Custom event tracking: ✅ Active (234 events tracked) Data freshness: Real-time (<30 second latency) Coverage: 23,847 of 24,100 accounts enriched (99.0%) USAGE ENRICHMENT IMPACT: Tickets enriched with usage data: 8,920 this month (↑ 18%) Average enrichment load time: 2.1 seconds Agent utilization of usage sidebar: 73% (↑ 12% from last month) Tickets where usage data led to faster resolution: 3,240 (36.3%) Average time saved per enriched ticket: 3.4 minutes First Contact Resolution improvement: +18% (enriched vs non-enriched) Agent satisfaction with usage data: 4.3/5.0 PROACTIVE TRIGGERS FIRED: Trigger Type | Fires This Month | Resolution Rate ----------------------------------|-----------------|----------------- Usage drop alert | 342 | 67% resolved Feature abandonment | 287 | 54% recovered Error rate spike | 156 | 89% prevented ticket Approaching usage limits | 98 | 100% notified Onboarding stall | 234 | 71% resumed Expansion opportunity detected | 89 | 23% converted Total proactive interventions: 1,206 Estimated tickets prevented: 743 (62% of interventions) SESSION REPLAY USAGE: Sessions replayed by agents: 890 this month Average replay duration viewed: 3.2 minutes Session replay leading to resolution: 612 (68.8%) Average diagnostic time saved: 8.5 minutes per replay Most replayed features: 1. API Integrations setup (234 replays) 2. Report builder configuration (156 replays) 3. Webhook configuration (123 replays) ERROR CORRELATION: Product errors auto-correlated to tickets: 1,340 Correlation accuracy: 87% Average time from error to ticket correlation: 4.2 minutes Outages detected via error correlation: 3 (all caught <15 min before tickets) Top correlated errors: API rate limit exceeded → 234 tickets (all had matching error logs) Webhook delivery failures → 123 tickets Report generation timeouts → 89 tickets EXPANSION OPPORTUNITIES: Opportunities detected from usage data: 89 Opportunities passed to sales/CSM: 89 (100%) Converted to revenue: 21 ($187,000 MRR) Average deal size from usage-detected opportunities: $8,900 MRR Top expansion signals: 1. API usage approaching limit (34 detected, 9 converted) 2. Team growth exceeding licenses (23 detected, 7 converted) 3. Feature request for higher-tier capability (18 detected, 3 converted) 4. Requesting add-on not in current plan (14 detected, 2 converted) DATA QUALITY: Accounts with complete usage data: 23,847 (99.0%) Accounts with session replay available: 22,100 (91.7%) Real-time tracking active: 23,847 (99.0%) Data gaps (manual enrichment needed): 253 (1.0%) RECOMMENDATIONS: 1. Increase session replay retention from 30 to 90 days (requested by 6 agents) 2. Add "Customer Health Score" visualization to usage sidebar 3. Implement usage trend alerts for CSM dashboard integration 4. Create automated report: "Usage Drop → Support Ticket" correlation ``` ### Usage-Based Support Triage Framework ``` USAGE DATA → SUPPORT RESPONSE MATRIX ======================================= SCENARIO | USAGE SIGNAL | AGENT ACTION -----------------------------|----------------------------------|--------------------------- API errors complaint | Rate limit errors in logs | Check API key config, suggest optimization "Can't find feature" | Feature never activated | Send activation guide, offer walkthrough Login issues | No login in 7+ days | Check account status, verify credentials, offer reset Slow performance | Session replay shows long loads | Check data volume, suggest indexing, escalate if needed Integration broken | Webhook failures in error log | Provide webhook debugging guide, check endpoint Billing questions | Payment failed in billing module | Check payment method, resend invoice, offer payment link Feature request | Customer not using related feature| Explain current feature, offer demo Account access | Team members not activated | Guide activation process, check invitation settings "Product doesn't work" | Session replay shows misconfig | Walk through configuration steps, share template Competitor comparison | Customer using competitor features| Highlight unique capabilities, offer migration help PROACTIVE OUTREACH TRIGGERS: Trigger: Usage dropped >30% in 7 days Action: Send "We noticed you haven't been active" email with personalized tips Timing: Within 24 hours of detection Trigger: Setup wizard abandoned at step 3+ Action: In-app message: "Need help completing setup?" with live chat option Timing: Within 2 hours of abandonment Trigger: Error rate >3x baseline for specific user Action: Proactive support ticket: "We noticed errors in your account" Timing: Within 30 minutes of pattern detection Trigger: 80% of usage limit reached Action: Email: "You're approaching your plan limits" with upgrade option Timing: At 80% threshold Trigger: New feature available for customer's segment Action: In-app notification + email: "New feature you might find useful" Timing: 48 hours after feature availability ``` ## Integration Points - **Product analytics** (Mixpanel, Amplitude, Heap, Segment): Usage tracking, feature adoption, behavioral events, cohort analysis - **Session replay** (FullStory, Hotjar, LogRocket): User session recordings, click heatmaps, rage click detection, error tracking - **Error monitoring** (Sentry, Datadog RUM, Bugsnag): Real-time error capture, stack traces, error correlation - **Help desk** (Zendesk, Intercom, Freshdesk): Ticket enrichment, agent sidebar, usage data display - **CRM** (Salesforce, HubSpot): Usage data synced as account health indicators - **Product platform**: Real-time API for querying current usage state, feature flags, configuration - **Data warehouse** (Snowflake, BigQuery): Historical usage data for trend analysis and ML models - **Real-time streaming** (Kafka, Kinesis): Event streaming for sub-second data freshness ## Edge Cases - **Customer on free trial with no historical usage baseline**: Cannot compare current usage to "normal": - Use cohort baseline: Compare to other trial customers at same day number - Day-1 benchmark: Expected setup completion by day 3 - Alert thresholds adjusted: More lenient for new customers - Onboarding focus: Trigger onboarding help instead of anomaly alerts - Escalation: Trial customer showing zero usage after 5 days → immediate CSM outreach - **Enterprise customer with 500+ users**: Usage data too granular for sidebar display: - Aggregate view: Show org-level metrics, drill-down on demand - Active user percentage: Primary metric (e.g., "127 of 500 active this week = 25.4%") - Highlight only anomalies: Don't show all 500 users, just those with errors or usage drops - Performance: Cache aggregated data, load in <2 seconds - Privacy: Anonymize individual user data, show only aggregate patterns - **Session replay captures sensitive customer data**: Customer processes PII in product (e.g., customer data platform): - PII auto-blurring: Email patterns, phone numbers, SSNs automatically masked in replay - Custom masking rules: Customer can configure additional sensitive fields - Compliance: Session replay data stored encrypted, access logged - Agent access: Only agents with ticket ownership can view that customer's replays - Retention: Session replays auto-deleted after 90 days (configurable) - **Product analytics integration lagging behind real-time**: Analytics pipeline delayed by 15 minutes during high traffic: - Fallback: Use cached data from last successful sync (stamped with timestamp) - Agent visibility: "Last updated: 14 minutes ago" badge on sidebar - Alert: Ops team notified when sync lag exceeds 10 minutes - Root cause: Analytics pipeline capacity issue → scale up or batch - Prevention: Implement event streaming (Kafka) for real-time sync during peak - **Different analytics platforms for different product areas**: Mobile app uses Mixpanel, web uses Amplitude, desktop uses custom tracking: - Unified query layer: Abstract analytics source, present unified view - Data normalization: Standardize event names across platforms - Missing data handling: Gracefully handle gaps when one platform is down - Agent clarity: Show data source per metric ("Usage: Mixpanel", "Errors: Sentry") - Migration path: Gradually consolidate to single analytics platform ## Output ### Integration Health Report ``` PRODUCT ANALYTICS INTEGRATION HEALTH — Monthly ================================================ CONNECTION STATUS: All integrations: ✅ Operational Uptime this month: 99.97% Data freshness: <30 seconds (target: <60 seconds) ✓ ENRICHMENT COVERAGE: Accounts with usage data: 23,847 / 24,100 (99.0%) Gaps: 253 accounts (3 on legacy plan, 250 on hold pending data migration) Resolution: Data migration scheduled for February 15 AGENT ADOPTION: Agents using usage sidebar daily: 73% of support team Trend: ↑ 12% from last month Top 10% agents (highest sidebar usage): Avg 2.3 min faster resolution Bottom 25% agents: Coaching on usage data utilization planned BUSINESS IMPACT: Estimated tickets prevented by proactive triggers: 743/month Average cost per ticket: $14.50 Monthly savings from ticket prevention: $10,774 Expansion revenue from usage-detected opportunities: $187,000 MRR RECOMMENDATIONS: 1. Increase agent adoption: Add usage data highlight to ticket assignment email 2. Extend session replay retention: From 30 to 90 days (cost: +$500/month) 3. Add mobile app usage data: Currently only web/desktop tracked 4. Build "Usage Health" automated report for CSM dashboard ```