Analytics Enhancement - Page-Level Tracking
Adds page-number tracking to project name reveal and download events, enabling page-level engagement analysis.
What this file does
Adds page-number tracking to project name reveal and download events, enabling page-level engagement analysis.
When to use it
- You have a multi-page presentation or slide deck and want to know which pages users interact with
- You need to correlate project reveals with specific pages in a digital brochure
- You want to build a dashboard showing page-level engagement metrics like reveals and downloads
- You are adding analytics to a paginated content experience and need event schema examples
Assumes this stack
Analytics Enhancement - Page-Level Tracking
🎯 What Was Updated
Enhanced analytics to track which specific page/slide users interact with for both project name reveals and downloads.
📊 Updated Analytics Events
1. Project Name Reveal (Enhanced)
Event: project_name_reveal
Properties:
project: Name of the project (e.g., "Prestige Shantiniketan")page: Page number where reveal happened (1-13) ⭐ NEW
Example:
{
project: "Brigade Valencia",
page: 2
}
Use Cases:
- Track which projects users are most curious about
- See which pages get the most reveals
- Identify if certain pages have more engagement
- Compare reveal rates across different pages
2. Single Page Download (Already had page tracking)
Event: download_single_page
Properties:
page: Page number downloaded (1-12)
Example:
{
page: 2
}
Use Cases:
- Track which pages users download most
- Identify most valuable content
- See download patterns by page
📈 New Dashboard Insights You Can Create
Page-Level Engagement
-
Project Reveals by Page
- Event:
project_name_reveal - Group by:
page - Visualization: Bar chart
- Shows: Which pages have highest reveal rates
- Event:
-
Most Revealed Projects
- Event:
project_name_reveal - Group by:
project - Order by: Count (descending)
- Shows: Which projects users are most curious about
- Event:
-
Page-Specific Reveal Rate
- Formula: (Reveals on page X / Total page views) × 100
- Shows: Engagement rate per page
-
Downloads by Page
- Event:
download_single_page - Group by:
page - Visualization: Bar chart
- Shows: Which pages users download most
- Event:
-
Page Engagement Heatmap
- Combine:
scroll_depth,project_name_reveal,download_single_page - Group by:
page - Shows: Overall engagement per page
- Combine:
🔍 Sample Queries
Get reveal count by page:
SELECT page, COUNT(*) as reveals
FROM events
WHERE event = 'project_name_reveal'
GROUP BY page
ORDER BY page
Get most revealed projects:
SELECT project, COUNT(*) as reveals
FROM events
WHERE event = 'project_name_reveal'
GROUP BY project
ORDER BY reveals DESC
LIMIT 10
Get page engagement score:
SELECT
page,
COUNT(DISTINCT CASE WHEN event = 'project_name_reveal' THEN timestamp END) as reveals,
COUNT(DISTINCT CASE WHEN event = 'download_single_page' THEN timestamp END) as downloads,
(reveals + downloads) as total_engagement
FROM events
WHERE page IS NOT NULL
GROUP BY page
ORDER BY total_engagement DESC
Compare reveal rates across pages:
SELECT
page,
COUNT(*) as reveals,
ROUND(COUNT(*) * 100.0 / SUM(COUNT(*)) OVER (), 2) as percentage
FROM events
WHERE event = 'project_name_reveal'
GROUP BY page
ORDER BY page
📊 Expected Insights
What You'll Learn:
-
Content Value
- Which pages have the most valuable content (high downloads)
- Which projects are most interesting (high reveals)
-
User Behavior
- Do users reveal names on early pages or later?
- Which pages drive the most downloads?
- Is there a correlation between reveals and downloads?
-
Engagement Patterns
- Do users engage more with certain types of data?
- Which visualizations are most effective?
- Where do users lose interest?
-
Optimization Opportunities
- Pages with low engagement might need better design
- High-reveal pages could be promoted more
- Most-downloaded pages show what users value
🎨 Dashboard Layout Suggestion
Page Performance Dashboard
Row 1: Overview
- Total Reveals (all pages)
- Total Downloads (all pages)
- Most Engaged Page
- Least Engaged Page
Row 2: Page Breakdown
- Bar Chart: Reveals by Page
- Bar Chart: Downloads by Page
- Line Chart: Engagement over time by page
Row 3: Project Insights
- Table: Top 10 Most Revealed Projects (with page number)
- Pie Chart: Reveal distribution by page
- Heatmap: Page × Action (reveal/download)
Row 4: User Journey
- Funnel: Page 1 → Reveal → Download
- Retention: Users who reveal on multiple pages
- Cohort: First reveal page vs total engagement
🚀 Implementation Details
Components Updated:
ButtonBar.tsx- AddedpageNumberprop- All 13 ButtonBar instances in
page.tsx- Added page numbers DownloadPageButton.tsx- Already had page tracking
Analytics Events:
- ✅
project_name_reveal- Now includes page number - ✅
download_single_page- Already had page number - ✅
download_single_page_success- Already had page number - ✅
download_single_page_error- Already had page number
Page Mapping:
- Page 1: Prestige Shantiniketan
- Page 2: Brigade Valencia
- Page 3: Embassy Lake Terraces
- Page 4: Brigade Exotica
- Page 5: Tata Promont
- Page 6: Sobha Crystal Meadows
- Page 7: Phoenix Kessaku
- Page 8: Sobha Royal Pavilion
- Page 9: Adarsh Palm Retreat
- Page 10: Pursuit of a Radical Rhapsody
- Page 11: Eden park @ The Prestige City
- Page 12: In That Quiet Earth
- Page 13: SNN Clermont
✅ Complete Event Reference
| Event | Properties | Example |
|---|---|---|
page_view | url, mobile, agent_name | - |
scroll_depth | percentage, mobile, agent_name | percentage: 50 |
rewind_completed | percentage, mobile, agent_name, url | percentage: 100 |
project_name_reveal | project, page | project: "Brigade Valencia", page: 2 |
download_all_initiated | - | - |
download_all_success | pages | pages: 12 |
download_all_error | error | error: "..." |
download_single_page | page | page: 2 |
download_single_page_success | page | page: 2 |
download_single_page_error | page, error | page: 2, error: "..." |
Status: ✅ Complete Last Updated: December 30, 2025 Version: 3.0
What's inside
7 sections: updated events, dashboard insights, 4 SQL queries, expected insights, dashboard layout, implementation details, complete event reference table
Change this for your project
- Replace the 13-page project mapping with your own page-to-content mapping
- Replace event names like
project_name_revealanddownload_single_pagewith your own event names - Replace the component names
ButtonBar.tsxandDownloadPageButton.tsxwith your own component files
Where it goes
Save in docs/ or the repository root. Gives agents and new contributors a map of the codebase.
Worth borrowing
- Adding a
pageproperty to existing events instead of creating separate page-specific events - Providing SQL queries and dashboard layout suggestions alongside the event schema to make the analytics immediately actionable
Related Documents
Design Document: BharatSeva AI
Describes a 10-agent AWS system that helps India's informal workers access government schemes via voice-first, serverless architecture.
OpenClaw Enterprise Transformation Plan
Transforms a single-user AI agent into a dual-mode platform supporting both viral open-source and Fortune 500 enterprise deployments through phased security, IAM, audit, multi-tenancy, and Kubernetes features.
Qwen Image and Edit: Open-sourcing and Local GGUF Generations with Lightning
Documents the Qwen-Image and Qwen-Image-Edit models, covering architecture, training, benchmarks, ComfyUI setup, and prompting techniques for local GGUF deployment.
Qwen3-TTS — Model Reference
Documents the architecture, weights, tokenizer, and inference algorithm for implementing Qwen3-TTS from scratch.