The measurement plan
Purpose: Translate requirements into analytics variables.
Who this page is for
| Audience | Why it matters to you |
|---|---|
| Architects | Create measurement plans |
| Implementers | Follow the plan |
The Measurement Plan
A measurement plan maps business requirements to analytics variables.
Structure
Business Question → Metric → Variable → Implementation
"How many form submissions?" → Count → event5 → fire when form submits
"By form type?" → Dimension → prop2 → set to "contact" or "complaint"
"By device?" → Dimension → automatic → already trackedExample: Example Super complaint form
| Requirement | Metric | Variable | Type | Implementation |
|---|---|---|---|---|
| Count form submissions | Form Submissions | event5 | Event | Fire on form submit |
| By form type | N/A | prop2 | Prop | Set to form type |
| By device | N/A | automatic | Dimension | Device type (auto) |
| By traffic source | N/A | eVar1 | eVar | Set on first hit |
Output: Measurement plan doc
- Stakeholder sign-off (requirement is correct)
- List of all variables needed
- Implementation order
- Test scenarios
---
Next: The Solution Design Reference