Learning paths by role
Who this page is for
| Audience | Why it matters to you |
|---|---|
| Everyone | See the optimal learning sequence for your situation |
Learning paths by role
Different roles need different knowledge. Choose your path below.
Implementation Engineer
Goal: Build implementations that collect the right data, cleanly and efficiently.
Time commitment: 12-16 hours
Week 1: Foundation
- Analytics Fundamentals (1 hour)
- The Variable Model — focus on the decision tree (2 hours)
- The measurement mental model (0.5 hours)
Week 2: How to build
- Implementation (3 hours)
- EA · Delivery Lifecycle (2 hours)
Week 3: Real examples
- Use Case: Site Search (2 hours)
- Use Case: Contact Form (2 hours)
Week 4: Production readiness
- Report Suites & Admin (1 hour)
- Privacy & Governance (1 hour)
- Troubleshooting Hub (bookmark, reference as needed)
Output: You can write a measurement plan, implement it in Web SDK, and debug issues.
---
Analyst / Power User
Goal: Find insights in data, understand what metrics mean, and ask good questions.
Time commitment: 6-8 hours
Week 1: The data model
- The measurement mental model (0.5 hours)
- Analytics Fundamentals (1 hour)
- Dimensions vs metrics (0.5 hours)
Week 2: How to report
- Analysis & Reporting (2 hours)
- The Variable Model — skim for understanding (1 hour)
Week 3: Real analysis
- Use Case: Site Search (1.5 hours)
- Troubleshooting: Wrong values (0.5 hours)
Output: You can segment and filter data confidently, create calculated metrics, and debug why numbers don't match.
---
Business Analyst / Product Manager
Goal: Write measurement requirements that are feasible, prioritize what to track, and understand trade-offs.
Time commitment: 3-4 hours
Day 1: Strategy
- The measurement mental model (0.5 hours)
- Server calls as design constraint (0.5 hours)
- Dimensions vs metrics (0.5 hours)
Day 2: Requirements
- EA · Delivery Lifecycle — Business requirements (1 hour)
- Use Case: Site Search (1 hour)
- EA · Delivery Lifecycle — Measurement plan (0.5 hours)
Output: You can write measurement requirements that implementers won't have to rewrite, and you understand why not everything can be tracked.
---
Analytics Admin / Manager
Goal: Understand system architecture, governance, and how to operate analytics at scale.
Time commitment: 5-6 hours
Week 1: Infrastructure
- Analytics Fundamentals (1 hour)
- Report Suites & Admin (2 hours)
Week 2: Governance
- EA · Delivery Lifecycle (1.5 hours)
- Privacy & Governance (1 hour)
Week 3: Future
- EA · Platform Strategy (0.5 hours)
Output: You can architect multi-site implementations, set up dev/stage/prod environments, and plan for CJA migration.
---
New to Analytics (any role)
Goal: Build foundational understanding before specializing.
Time commitment: 8-10 hours
- Welcome & orientation (0.5 hours)
- The measurement mental model (0.5 hours)
- Analytics Fundamentals (1.5 hours)
- The Variable Model (2 hours)
- Core Learning Journey (sessions 1-3) (3 hours with labs)
Then choose your specialization path from above.
---
Accelerated path (1 day)
For people who just need to get started:
- The measurement mental model (0.5 hours)
- Analytics Fundamentals (1 hour)
- The Variable Model — decision tree (1 hour)
- Use Case: Site Search (2 hours)
Focus: Get oriented, see a real example, know where to look for details.
---
Tips for any path
Tip 1: Take notes on pages you'll reference often (decision tree, triage method, QA checklist).
Tip 2: Implement what you learn. Read about Web SDK, then send test data. The skill sticks.
Tip 3: Bookmark this page. When you forget something, come back here and jump to the relevant section.
Tip 4: Use search liberally. You don't need to memorize everything.
---
Start: Pick your role above and begin Week 1.