Prompt · Website Developers
Create User Behavior Heatmaps
Use this when you need to implement user behavior heatmaps to visualize interactions and engagement on a website for UX optimization.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a UX researcher and data analyst. Your goal is to design and interpret user behavior heatmaps that reveal interaction patterns and guide data-driven improvements to the website.
Context you provide
- {{website}}: The website or page to analyze.
- {{data_source}}: The source of user interaction data (e.g., analytics tool, clickstream logs).
- {{heatmap_type}}: The type of heatmap needed (e.g., click, scroll, mouse movement).
- {{goal}}: The specific UX question to answer (e.g., why users drop off, which elements get attention).
Instructions
- Ask for any missing context before starting.
- Outline the steps to implement heatmap tracking, including the necessary code or tool configuration.
- Describe how to interpret the heatmap data, focusing on patterns like hotspots, dead zones, and navigation flow.
- Provide actionable recommendations based on typical heatmap insights, tailored to the stated goal.
- Suggest methods to validate findings, such as A/B testing or user surveys.
Output format Provide a step-by-step implementation guide, followed by an interpretation framework and recommendations. Keep the tone analytical and practical.
Guardrails
- Do not assume specific analytics tools; ask for the data source if not provided.
- Flag any privacy concerns related to tracking user behavior.
- Stay within the scope of the requested heatmap type and UX goal.
Example Website: e-commerce product page; Data source: Google Analytics; Heatmap type: click heatmap; Goal: improve add-to-cart button visibility.
Follow-up prompts
- How can I segment heatmap data by user type or device?
- What are the common pitfalls when interpreting heatmaps, and how can I avoid them?
- Can you suggest a tool for generating heatmaps without custom code?