revenue-heatmap-playbooks

Optimizes ecommerce page elements using revenue-per-click heatmap analytics from the Heatmap MCP.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Click-only heatmaps show engagement but hide which page elements actually drive revenue, so teams reorder nav items, carousels, and product tiles based on opinion or raw click counts. This Skill turns Heatmap MCP data into ten concrete, threshold-driven element optimizations that identify Conversion Killers and rank elements by revenue impact. ## Core Features & Use Cases - Ten Element Playbooks: Covers mobile navigation, dropdown menus, PDP carousels, collections tiles, default tabs, outbound links, content buckets, FAQs, UVPs, and on-page upsells, each with a trigger signal, decision threshold, and MCP query recipe. - RPS vs RPC Decision Rules: Applies Revenue Per Session for same-type element comparisons and Revenue Per Click for cross-type comparisons and FAQs, with explicit formulas computed from get_raw_event_analytics output. - Conversion Killer Detection: Flags elements with 20 or more clicks and zero attributed revenue, then routes them to screen-recording review before removal or relocation. - Use Case: A merchant asks why their mobile nav underperforms. The Skill queries get_raw_event_analytics filtered to device MOBILE, computes RPC per nav selector, and recommends reordering items with RPC above 2x average to the top while removing zero-revenue social icons. ## Quick Start Ask Claude to analyze your homepage navigation with Heatmap data and tell you which elements to reorder or remove based on revenue per click.

Frequently Asked Questions about revenue-heatmap-playbooks

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

FAQPage Schema
How do I find conversion killers on my ecommerce site with heatmap data?▼

Query get_raw_event_analytics ordered by revenue ascending and look for elements with 20 or more clicks but zero attributed revenue. Common offenders are social media icons, blog links, and share buttons. Cross-reference with screen recordings before removing them.

When should I use RPS versus RPC for element analysis?▼

Use Revenue Per Session to compare elements of the same type on the same page, like nav items or carousel images. Use Revenue Per Click for comparing different element types and always for FAQs, since all FAQ items share one viewport and have equal RPS by definition.

How do I optimize product carousel image order on a PDP?▼

Pull get_raw_event_analytics for the product page, filter rows to carousel image selectors, and sort by RPC (revenue divided by clicks). Move the highest-RPC image to position one and remove or demote any image below 0.25x the top performer's RPC.

Should I analyze mobile and desktop navigation separately?▼

Yes. Mobile nav is a hamburger menu while desktop is a horizontal bar, and their RPS profiles often differ completely. Filter queries with device MOBILE first, since roughly 80 percent of traffic is mobile, then run a separate desktop analysis.

Why is sorting collections tiles by bestseller rank a mistake?▼

Bestseller rank reflects position bias: items sell more because they have always been at the top. Sorting tiles by RPS strips out position bias and reveals which products actually convert most efficiently per session.

What are the limitations of click-only heatmaps for CRO?▼

Click-only heatmaps show engagement but cannot reveal Conversion Killers, since an element can attract heavy clicks while driving zero revenue. Revenue-attributed heatmap data is required to distinguish business impact from mere popularity.