Heatmap & Conversion Analyzer

What it does

Reviews heatmap tool metrics (scroll depth, rage clicks, dead clicks, engagement) by funnel, variant, or device, and turns them into a structured report with conversion optimization recommendations and prioritized A/B test hypotheses.

When to use it

• When a page has traffic but you don't know why it's not converting.
• When you need visual evidence before proposing a design change.
• When you want to prioritize which A/B tests to run first by expected impact.

Steps

1. Connect or export data from your heatmap tool.
2. The assistant filters by funnel, variant, or device as requested.
3. It identifies scroll patterns, rage clicks, and dead zones.
4. A structured report with prioritized findings is generated.
5. A/B test hypotheses are proposed with an impact/effort score.
6. You decide which hypothesis moves to execution; nothing on the site changes automatically.

The skill

---
name: heatmap-conversion-analyzer
description: Analyzes scroll, rage-click, and session-recording signals to produce conversion optimization and A/B test recommendations.
---

# Heatmap & Conversion Analyzer

## 1. What it does

- Reviews heatmap tool metrics (scroll depth, rage clicks, dead clicks, engagement) by funnel, variant, or device, and turns them into a structured report with conversion optimization recommendations and prioritized A/B test hypotheses.

## 2. When to use it

- When a page has traffic but you don't know why it's not converting.
- When you need visual evidence before proposing a design change.
- When you want to prioritize which A/B tests to run first by expected impact.

## 3. Step by step

- Connect or export data from your heatmap tool.
- The assistant filters by funnel, variant, or device as requested.
- It identifies scroll patterns, rage clicks, and dead zones.
- A structured report with prioritized findings is generated.
- A/B test hypotheses are proposed with an impact/effort score.
- You decide which hypothesis moves to execution; nothing on the site changes automatically.

## 4. Safety rules

- Safety rules: everything ships as a draft first; nothing is sent, published, or paid for without your explicit approval; no data, numbers, or results are ever invented; no credentials or secrets are typed into chat.

## 5. Best practices

- Always review the full draft before approving any send, publish, or payment.
- If real information (data, numbers, results) is missing, ask for it to be flagged as pending instead of invented.
- Keep credentials and keys out of chat; set them in environment variables or your secrets manager.

## 6. GoHighLevel integration

- Where relevant, results can be saved as contacts, tags, tasks, or notes inside your GoHighLevel sub-account.
- No automation inside GHL (workflow, campaign, trigger) activates without your review first.

For Claude Code, save it as ~/.claude/skills/heatmap-conversion-analyzer/SKILL.md. In Cursor, ChatGPT or another assistant, paste it as project instructions.