You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The instrumentation plan will focus on measuring the health of the delegation funnel without introducing heavy analytics infrastructure or invasive tracking.
Because Explorer is already hosted on Vercel and Livepeer already has a Pro account, our primary recommendation will be to use Vercel Web Analytics with a small set of custom events. This should keep implementation low-lift while still giving the Foundation enough visibility to measure whether future UX improvements are helping users move through the delegation journey.
The event spec will be documented as a lightweight tab in the Google Sheet.
Event Scope
The plan will focus on aggregate funnel events, such as:
Delegation page viewed
Delegate CTA clicked
Wallet connected for delegation
Orchestrator selected
Delegation review opened
Delegation transaction submitted
Delegation transaction confirmed
Delegation transaction failed
Delegator dashboard viewed
Switch orchestrator started
Unbonding / exit started
Privacy and Scope Constraints
The goal is to measure funnel health, not build user profiles.
The plan will avoid:
PII
Session replay
Heatmaps
Fingerprinting
Wallet-level behavioral profiles
Unnecessary long-term user tracking
Baseline Measurement
The plan will also propose a simple baseline measurement approach so future Explorer changes can be evaluated.
Baseline metrics may include:
Delegation page views
Delegate CTA clicks
Wallet connects
Orchestrator selections
Delegation attempts
Confirmed delegation transactions
Failed delegation transactions
Return visits to delegation / monitoring views
The goal is to make future improvements measurable without turning this RFP into an analytics buildout.
Deliverables
Lightweight instrumentation event spec documented in the Google Sheet.
Recommended Vercel Web Analytics custom events for the Explorer delegation funnel.
Minimal event-property guidance that stays compatible with a low-lift Vercel Analytics setup.
Privacy and scope notes covering what should not be tracked.
Baseline measurement approach for evaluating future delegation UX improvements.
Mapping between key funnel events and the relevant delegation journey stages.
Acceptance Criteria
The plan can be implemented without introducing a new backend or heavy analytics infrastructure.
The event spec focuses on aggregate funnel health rather than individual user profiling.
The recommended events cover the major delegation funnel stages: discovery, intent, wallet connection, orchestrator selection, transaction submission, confirmation/failure, monitoring, and exit.
The plan avoids PII, session replay, heatmaps, fingerprinting, and wallet-level behavioral profiles.
The event-property guidance is intentionally minimal and suitable for Vercel Web Analytics on Pro.
The baseline measurement approach is clear enough to evaluate whether future UX changes improve delegation conversion.
Instrumentation Plan
The instrumentation plan will focus on measuring the health of the delegation funnel without introducing heavy analytics infrastructure or invasive tracking.
Because Explorer is already hosted on Vercel and Livepeer already has a Pro account, our primary recommendation will be to use Vercel Web Analytics with a small set of custom events. This should keep implementation low-lift while still giving the Foundation enough visibility to measure whether future UX improvements are helping users move through the delegation journey.
The event spec will be documented as a lightweight tab in the Google Sheet.
Event Scope
The plan will focus on aggregate funnel events, such as:
Privacy and Scope Constraints
The goal is to measure funnel health, not build user profiles.
The plan will avoid:
Baseline Measurement
The plan will also propose a simple baseline measurement approach so future Explorer changes can be evaluated.
Baseline metrics may include:
The goal is to make future improvements measurable without turning this RFP into an analytics buildout.
Deliverables
Acceptance Criteria