Document Type: Framework
Status: Active
Version: v1.2
Authority: MWMS HeadOffice
Parent: Data Brain Canon
Last Reviewed: 2026-04-26
Purpose
The Data Brain Event Measurement Framework defines how MWMS structures user behaviour into measurable events so that important actions can be captured, interpreted, and used for decision-making.
The framework ensures behavioural measurement is based on:
clear event logic
clear parameter logic
meaningful interaction capture
consistent interpretation discipline
reliable downstream reporting
The framework protects MWMS from weak measurement design by ensuring significant user actions are defined properly at the point of capture.
If event structure is weak, reporting quality deteriorates.
If reporting quality deteriorates, signal interpretation becomes unreliable.
Reliable event design improves system intelligence.
Event design determines signal quality.
Signal quality determines interpretation quality.
Interpretation quality determines decision quality.
This framework is extended to ensure event measurement supports:
- attribution accuracy
- full journey reconstruction
- cross-channel visibility
- behavioural lag analysis
- decision-grade intelligence
Scope
This framework applies to:
- behavioural event design
- event parameter design
- interaction capture structure
- user-action tracking logic
- meaningful event naming discipline
- signal measurement architecture
- conversion event structure
- behavioural progression capture
- attribution data readiness
- cross-channel measurement alignment
This framework governs how MWMS defines and structures event-based measurement.
It does not govern:
- final dashboard design
- final report layout
- traffic strategy
- experiment approval
- capital decisions
Those remain governed by Data Brain, Ads Brain, Experimentation Brain, Finance Brain, and related frameworks.
Core Principle
Everything meaningful that happens in a digital environment should be measurable as an event.
An event represents a user interaction or system action.
An event becomes useful when paired with descriptive parameters and aligned with behavioural meaning.
Events without context create weak data.
Events with structured parameters create interpretable signals.
MWMS measurement must capture:
what happened
where it happened
what context surrounded the action
what behavioural stage the action represents
what decision relevance the action implies
Measurement logic begins at the event layer.
Event Structure Rule
Every measurable event must contain:
- a clear event name
- a clear behavioural meaning
- a defined role inside the signal hierarchy
- supporting parameters where required
The event name identifies what happened.
The parameters describe the context.
Example structure:
event = form_submit
parameters = form_type, page_location, traffic_source
The event captures the interaction.
The parameters capture the context.
The classification frameworks capture the meaning.
Event Naming Discipline
Event names must be:
clear
consistent
behaviour-based
machine-readable
Event names must describe the interaction, not the interpretation of the interaction.
Correct examples:
page_view
form_submit
product_view
checkout_start
video_progress
Weak examples:
high_intent_user
good_lead
strong_interest
Interpretation belongs later in the signal chain.
Event naming belongs at the measurement layer.
Measurement clarity improves interpretation clarity.
Parameter Structure Rule
Parameters describe the event in greater detail.
Parameters may define:
location
content type
product type
traffic context
device context
step within a sequence
interaction depth
offer context
Parameters must add context that improves future interpretation.
Parameters must not be collected without purpose.
Useful parameters improve:
segmentation
comparison
signal diagnosis
attribution analysis
behavioural pattern detection
The event carries the action.
The parameters carry the context.
Context enables interpretation.
🔴 Macro Conversion And Micro Conversion Rule
Events must be classified as either:
Macro Conversions
Micro Conversions
Macro Conversions represent:
- final business outcomes
- revenue-generating actions
- completed lead or purchase events
Examples:
purchase
lead_submit
booked_call
Micro Conversions represent:
- behavioural steps leading to macro outcomes
- engagement progression
- intent signals
Examples:
product_view
add_to_cart
form_start
cta_click
Macro conversions define outcomes.
Micro conversions define journey progression.
Attribution requires both.
Significant Interaction Rule
Not every action deserves equal measurement priority.
MWMS prioritises significant interactions.
Examples of significant interactions:
page view
scroll milestone
video progress
product view
CTA click
form start
form submit
checkout step
purchase event
lead event
Significant interactions must reflect behavioural progression.
Measurement must reflect decision relevance.
Events should map to behavioural stages.
Business Purpose Alignment Rule
Measurement design must begin with the purpose of the environment being measured.
Questions to ask:
What is the purpose of the page?
What is the purpose of the funnel?
What is the purpose of the system?
Which actions indicate progress toward that purpose?
Events must be selected based on decision relevance.
If an event does not improve understanding of business purpose, it should not be prioritised.
Measurement should follow behavioural logic, not technical convenience.
Event Hierarchy Principle
Events operate at different levels of decision importance.
Typical event hierarchy:
Foundation Events
Attention Events
Engagement Events
Intent Events
Progression Events
Outcome Events
Hierarchy improves interpretation clarity.
Not all events should be treated equally.
🔴 Journey Reconstruction Rule
Events must support reconstruction of full user journeys.
Event design must enable:
- sequence tracking
- cross-session linking
- multi-touch journey mapping
- behavioural path analysis
Events must not exist as isolated records.
They must be linkable into:
→ full behavioural journeys
Without journey reconstruction:
→ attribution becomes unreliable
→ behavioural understanding becomes fragmented
🔴 Cross Channel Event Capture Rule
Event measurement must extend beyond on-site interactions.
MWMS must capture or integrate:
- ad clicks
- ad impressions
- email sends and opens
- affiliate interactions
- cost data
- external touchpoints
Attribution requires cross-channel data.
On-site events alone are insufficient.
🔴 Attribution Readiness Rule
Event systems must meet minimum conditions before attribution is trusted.
Requirements:
- macro conversions clearly defined
- micro conversions clearly defined
- event hierarchy implemented
- cross-channel inputs available
- cost data available where required
- signal integrity validated
If these conditions are not met:
→ attribution must not be used for decision-making
🔴 Time And Lag Measurement Rule
Every event must include accurate timestamp data.
Event systems must support:
- time between interactions
- time to conversion
- lag analysis
- behavioural pacing
Time is a core behavioural signal.
Without time:
→ attribution loses accuracy
→ journey understanding weakens
Event Measurement Quality Rule
Good event measurement requires:
correct event firing
correct parameter attachment
consistent naming
stable tracking logic
correct destination mapping
consistent behavioural meaning
If events are captured incorrectly from the start, later reporting becomes unreliable.
Tracking quality precedes reporting quality.
Measurement reliability depends on structural clarity.
Event Integrity Compatibility Rule
Event design must support reliable downstream interpretation.
Events must align with:
Event Value Classification Framework
Conversion Definition Framework
Measurement Integrity Framework
Behavioural Event Analysis Framework
Event structure must support:
conversion clarity
signal hierarchy clarity
behavioural sequence interpretation
experiment reliability
Events should not be defined in isolation.
Events must support ecosystem-level interpretability.
Dimension and Metric Relationship
Events produce measurable records.
From these records, dimensions and metrics are formed.
Dimensions describe categorical context.
Metrics describe quantitative outcomes.
MWMS must preserve the distinction between:
event
parameter
dimension
metric
Mixing these layers causes interpretation drift.
Event Based Interpretation Rule
The event-based model reflects real-world reasoning.
Something happens.
Questions are then asked about that thing.
Event-based reasoning enables structured behavioural understanding.
Segmentation Compatibility Rule
Event design should support future segmentation.
Useful segmentation dimensions may include:
traffic source
content category
device type
page type
campaign type
funnel stage
offer type
Well-structured events improve:
analysis depth
comparison quality
experiment interpretation
attribution clarity
Drift Protection
The system must prevent:
event naming based on vague interpretation
event collection without clear behavioural purpose
parameters being added without analytical value
different parts of MWMS measuring the same interaction differently
weak tracking architecture being accepted as sufficient
missing cross-channel data affecting attribution
loss of time data affecting behavioural analysis
Architectural Intent
The Data Brain Event Measurement Framework ensures MWMS captures behavioural reality in a structured and reusable way.
The event layer is the foundation of signal quality.
Signal quality is the foundation of interpretation quality.
Interpretation quality is the foundation of decision quality.
Strong event design improves every downstream Brain system.
Change Log
Version: v1.2
Date: 2026-04-26
Author: MWMS HeadOffice
Change:
Major upgrade to support attribution intelligence:
- added Macro vs Micro Conversion Rule
- added Journey Reconstruction Rule
- added Cross Channel Event Capture Rule
- added Attribution Readiness Rule
- added Time And Lag Measurement Rule
- extended framework to support attribution and decision intelligence
Change Impact Declaration
Pages Created:
None
Pages Updated:
Data Brain Event Measurement Framework
Pages Deprecated:
None
Registries Requiring Update:
No
Canon Version Update Required:
No
Change Log Entry Required:
Yes