heatmap-metrics-literacy

Compute and interpret RPS, RPC, AOV, and conversion metrics from Heatmap MCP analytics data.

Updated May 6, 2026
One-click install
npx skills add https://github.com/Heatmap-com-Inc/heatmap-claude-skills --skill heatmap-metrics-literacy-heatmap-com-inc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: heatmap-metrics-literacy
Source: https://github.com/Heatmap-com-Inc/heatmap-claude-skills/tree/main/skills/heatmap-metrics-literacy
Command: npx skills add https://github.com/Heatmap-com-Inc/heatmap-claude-skills --skill heatmap-metrics-literacy-heatmap-com-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web analytics tools return raw numbers, but without a consistent metric framework teams misread conversion rate as a percentage, compare dissimilar elements incorrectly, and optimize for vanity metrics instead of revenue. This Skill gives Claude exact definitions, formulas, API field mappings, and decision rules for every metric in the Heatmap methodology. ## Core Features & Use Cases - Metric Definitions with API Mappings: Precise formulas and exact Heatmap MCP field names for RPS, RPC, AOV, CR, LPS, sessions, pageviews, scroll depth, and time on page. - Four MCP Recipes: Ready-to-use query patterns for sitewide North Star metrics, page-level RPS ranking, element-level RPC computation for Conversion Killer detection, and scroll-depth engagement diagnosis. - Decision Rules and Gotchas: Enforces RPS as the tiebreaker metric, the 50-click RPC reliability threshold, decimal-to-percentage conversion for CR, and mandatory traffic segmentation before reporting. - Use Case: Ask which homepage elements are Conversion Killers, and Claude queries get_raw_event_analytics, computes RPC per selector, and flags elements with over 50 clicks but near-zero attributed revenue. ## Quick Start Ask Claude to pull last month's RPS, conversion rate, and AOV for your site and identify which high-traffic pages are underperforming on revenue per session.

Frequently Asked Questions about heatmap-metrics-literacy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I calculate revenue per session from analytics data?▼

Revenue per session equals total revenue divided by sessions, where a session is one distinct visitId. In the Heatmap API, request the REVENUE_PER_SESSION metric from get_session_analytics or read revenue_per_session from get_raw_pageview_analytics rows.

What is the difference between RPS and RPC metrics?▼

RPS measures revenue per session for pages or same-type elements, while RPC measures revenue per click on a specific element. Use RPC to compare dissimilar elements like nav links versus CTAs, and RPS for page comparisons and split-test decisions.

Why does my conversion rate show as 0.025 instead of 2.5%?▼

The Heatmap API returns conversion_rate as a decimal ratio, not a percentage. Multiply the value by 100 before displaying it, so 0.025 becomes 2.5%.

When is RPC unreliable for element analysis?▼

RPC is noise below 50 clicks on an element, since a single purchase can wildly skew the ratio. For low-click elements, use RPS instead or report RPC with an explicit caveat about insufficient volume.

Should I use conversion rate or RPS as my primary optimization metric?▼

Use RPS as the primary metric because it combines conversion rate and AOV into one revenue-focused number. Sitewide conversion rate is considered a vanity metric, valid mainly for step-by-step funnel leak diagnosis using completed_rate per step.

How do I adapt RPS analysis for lead generation sites?▼

Replace RPS with LPS (leads per session) by dividing lead conversions from get_conversions by sessions from get_session_analytics. All RPS-based decision rules apply identically to LPS for SaaS, B2B, and service businesses.