Extending Ember with Analytics
summary
Provides a concrete Ember implementation that wires pageviews and actions into analytics rather than copy‑pasting vendor snippets, using Google Analytics/Adobe SiteCatalyst examples. It hooks the router via didTransition hook and exposes a centralized analytics object with route‑specific data, reopens the ActionHandler to override send, and merges global and route data before calling the tracker. Demo shows an online‑bank app logging login, OTP delivery choice, a $200 transfer and an error case to the console instead of a remote call proving the approach works for route changes model changes programmatic and template actions.
AI-written summary · about
chapters (12)
- 0:00Web analytics in Ember
- 2:02Analytics with SPAs
- 3:48Page views and user actions
- 5:12Naive page view tracking
- 7:22Page view tracking with didTransition
- 8:49Naive action tracking
- 10:14Centralized analytics object
- 13:00Action handler mixin
- 14:24Route-level action handling
- 18:41Declarative analytics pattern
- 19:02Demo of analytics integration
- 22:14References and closing
related talks
31mEmber on Rails: #REALTALK
29mIdiomatic Ember, Sweet Spot of Performance and Productivity
24mNew to Ember: What ARE All These Things?
29mDebugging Ember With Empathy
46mArt and Science of Shipping Single Page Apps with Ember.js
32mAn Animated Guide to Ember Internals
25mThe Great Migration, Redesigning and Rewriting our App in Ember.js
26mAmbitious UX for Ambitious Apps