Document Type: Framework
Status: Draft
Authority: Data Brain
Applies To: Affiliate Brain, Ads Brain, Conversion Brain, Experimentation Brain, Research Brain, Finance Brain
Parent: Data Brain
Version: v1.0
Last Reviewed: 2026-04-22
Purpose
The Data Brain Conversion Definition Framework defines how MWMS determines which events qualify as true conversions.
Analytics systems allow any event to be marked as a conversion.
Without discipline, this can result in:
• inflated performance perception
• incorrect optimization targets
• false learning signals
• poor scaling decisions
• distorted ROI calculations
• wasted ad spend
• incorrect offer validation
This framework ensures that conversions represent meaningful business outcomes rather than convenient tracking artefacts.
The framework protects decision quality across:
• Affiliate Brain offer validation
• Ads Brain performance evaluation
• Experimentation Brain learning loops
• Conversion Brain optimisation
• Finance Brain ROI calculations
• Research Brain behavioural interpretation
Core Principle
Not every measurable event should be treated as a conversion.
A conversion must represent a meaningful advancement in the user’s commitment toward a defined business objective.
Conversions must reflect decision significance, not tracking convenience.
Definition
A conversion is a user action that represents meaningful progress toward value creation.
Value creation may include:
• revenue generation
• lead generation
• qualification progression
• relationship initiation
• commitment behaviour
• transactional completion
Conversions represent behavioural confirmation of intent, not simply interaction activity.
Conversion Qualification Criteria
An event qualifies as a conversion when it satisfies one or more of the following conditions.
Condition 1 — Commitment Threshold
The event indicates that the user has committed to an action that requires effort, decision, or personal investment.
Examples:
• submitting a lead form
• booking an appointment
• initiating checkout
• completing registration
• submitting application
• entering payment details
These actions typically require deliberate decision-making.
Condition 2 — Business Value Signal
The event provides measurable business value.
Examples:
• purchase completion
• subscription activation
• consultation booking
• qualified lead submission
• trial activation
• paid membership signup
These actions directly contribute to commercial objectives.
Condition 3 — Intent Confirmation
The event confirms user interest in a defined solution category.
Examples:
• pricing page confirmation interaction
• offer qualification step completion
• product configuration completion
• eligibility confirmation
• demo request
These signals strongly indicate potential conversion likelihood.
Condition 4 — Funnel Progression Advancement
The event represents a critical step in a defined behavioural journey.
Examples:
• checkout initiation
• application start
• lead magnet completion
• onboarding start
• plan selection
These actions indicate forward movement in decision progression.
Non-Conversion Event Examples
Events that should not normally be classified as conversions:
Passive signals
• page view
• session start
• landing page view
• impression
• scroll depth
These indicate presence or attention but not commitment.
weak engagement signals
• time on page threshold
• video start
• video watch percentage
• navigation interaction
• category browsing
These may indicate interest but not decision commitment.
diagnostic signals
• button hover
• minor UI interaction
• filter usage
• tab change
Useful for analysis but not conversion classification.
Conversion Tier Structure
Conversions should be categorized by behavioural significance.
Primary Conversions
Core objective outcomes.
Examples:
• purchase
• qualified lead submission
• booked call
• paid signup
• completed order
• confirmed registration
Used for:
ROI evaluation
scaling decisions
offer validation
traffic evaluation
Highest priority signals.
Secondary Conversions
Strong intent signals but not final value creation.
Examples:
• checkout start
• form start
• demo request
• application start
• pricing interaction
• plan selection
Used for:
funnel diagnostics
friction identification
persuasion evaluation
Support Primary Conversion interpretation.
Micro Conversions
Intermediate signals indicating interest progression.
Examples:
• CTA click
• outbound click
• content upgrade request
• quiz start
• feature comparison interaction
Used for:
message evaluation
creative optimisation
interest validation
Do not replace primary conversions.
Conversion Integrity Rules
Rule 1
Conversion definitions must remain stable during testing cycles.
Changing conversion definitions mid-test corrupts comparability.
Consistency ensures:
clean learning signals
valid experiment comparison
reliable optimization direction
Rule 2
Conversions must reflect genuine behavioural progress.
Artificial conversion inflation distorts system feedback.
Examples of poor conversion definitions:
page view as conversion
video play as conversion
time on page as conversion
These events lack commitment significance.
Rule 3
Primary conversions must be clearly distinguished from supporting signals.
Secondary and micro conversions support diagnosis but must not override primary outcome evaluation.
Rule 4
Conversion events must align with business model structure.
Different systems require different conversion definitions.
Example:
affiliate funnel conversion
outbound click
lead generation funnel conversion
form submission
ecommerce funnel conversion
purchase
subscription funnel conversion
trial activation
Conversion meaning is context dependent.
Rule 5
Conversion definitions must be reviewed periodically.
Changes in:
offer structure
funnel design
traffic strategy
monetization model
may require conversion definition refinement.
Conversion Mapping Example
Example affiliate funnel:
Micro Conversion
CTA click
Secondary Conversion
email submit
Primary Conversion
offer purchase
Monetization Confirmation
revenue recorded
Signal progression must be evaluated across stages.
Relationship to Other MWMS Frameworks
Directly supports:
MWMS Standard Conversion Signal Ladder
Data Brain Event Value Classification Framework
Data Brain Signal Flow Framework
Data Brain Measurement Integrity Framework
Ads Brain Pre Conversion Signal Framework
Conversion Brain Funnel Optimization Framework
Experimentation Brain Test Interpretation Discipline
Finance Brain ROI evaluation logic
Governance Notes
Incorrect conversion definitions can cause:
false optimisation signals
incorrect creative conclusions
incorrect traffic evaluation
premature scaling decisions
misleading ROI calculations
Conversion discipline protects system intelligence quality.
Change Log
Version: v1.0
Date: 2026-04-22
Author: Data Brain
Change:
Initial creation of Conversion Definition Framework establishing criteria for identifying meaningful conversions and separating true outcome signals from intermediate behavioural signals.