Athena — roomy-mobile/archive/changes/2026-01-05-fix-notification-permissions/tasks/004-create-analytics.md


skill-level: medior status: done

Task: Create Notification Permission Analytics

End Goal

Full analytics funnel tracking for the notification permission consent flow.

Currently

  • No analytics for notification permission flow
  • NotificationAnalytics may exist for other notification events

Should

  • Analytics events for:
    • notification_banner_shown
    • notification_banner_tapped
    • notification_consent_sheet_shown
    • notification_consent_accepted
    • notification_consent_cancelled
    • notification_permission_granted
    • notification_permission_denied

Constraints

  • [ ] Follow existing analytics pattern (extend TAnalytics)
  • [ ] Include location parameter for event origin
  • [ ] Use existing analytics service infrastructure

Acceptance Criteria

  • [ ] All 7 analytics events are implemented
  • [ ] Events follow project's TAnalytics pattern
  • [ ] Events include appropriate parameters

Implementation Checklist

  • [x] 4.1 Create or update NotificationPermissionAnalytics class in lib/notifications/analytics/
  • [x] 4.2 Extend TAnalytics with location parameter
  • [x] 4.3 Implement bannerShown() method
  • [x] 4.4 Implement bannerTapped() method
  • [x] 4.5 Implement consentSheetShown() method
  • [x] 4.6 Implement consentAccepted() method
  • [x] 4.7 Implement consentCancelled() method
  • [x] 4.8 Implement permissionGranted() method
  • [x] 4.9 Implement permissionDenied() method
  • [x] 4.10 Run flutter analyze to verify no issues

Notes

  • Analytics helps understand conversion funnel and identify friction points
  • Location parameter helps identify where in the app events originate

Reacties

Nog geen reacties