Microsoft Clarity Automation

Clarity Automation

Auto-detects your installed agents and installs the skill to each one.

What This Skill Does

This skill exports Microsoft Clarity user behavior analytics, including heatmaps, session metrics, and engagement insights, directly from code. It allows users to segment data by dimensions like browser, device, and location. This is useful for optimizing website design and user experience.

When to Use

Export Clarity data for the last 24 hours

Break down data by device and country

Analyze user behavior across device types

Optimize responsive design

Segment data by browser

Analyze traffic source performance

Key Features

Exports Clarity data via M

ICROSOFT_CLARITY_DATA_EXPORTSupports segmentation by multiple dimensions

Offers data for the last 1-3 days

Provides insights into user engagement

Analyzes device performance

Requires a connected Microsoft Clarity account

Manual Installation

Manual installation

View Full Skill Content

The complete markdown content that gets installed

Microsoft Clarity Automation

Export Microsoft Clarity user behavior analytics directly from Claude Code. Pull heatmap data, session metrics, and engagement insights segmented by multiple dimensions without leaving your terminal.

Toolkit docs: composio.dev/toolkits/microsoft_clarity

Setup

Add the Composio M

CP server to your configuration: https://rube.app/mcp Connect your Microsoft Clarity account when prompted. The agent will provide an authentication link. Ensure your Clarity project has sufficient data collection enabled for the dimensions you want to analyze.

Core Workflows

1. Export Recent Analytics Data

Export Clarity analytics data for the last 1-3 days, segmented by up to three dimensions simultaneously.

Tool: M

ICROSOFT_CLARITY_DATA_EXPORT

Key parameters: num

OfDays (required) -- number of days to export: 1 (last 24h), 2 (last 48h), or 3 (last 72h) dimension1 -- first breakdown dimension dimension2 -- second breakdown dimension (optional) dimension3 -- third breakdown dimension (optional)

Available dimensions: Browser -- Chrome, Firefox, Safari, Edge, etc. Device -- Desktop, Mobile, Tablet Country/Region -- geographic location of users OS -- Windows, mac

OS, i

OS, Android, etc. Medium -- traffic medium (organic, cpc, referral, etc.) Campaign -- marketing campaign name Channel -- traffic channel grouping U

RL -- specific page U

RLs

Example prompt: "Export Clarity data for the last 24 hours broken down by Device and Country/Region"

2. Device Performance Analysis

Analyze how user behavior differs across device types to optimize responsive design.

Tool: M

ICROSOFT_CLARITY_DATA_EXPORT

Configuration: num

OfDays: 3, dimension1: "Device", dimension2: "Browser"

Example prompt: "Show me Clarity metrics for the last 3 days by Device and Browser"

Understand which traffic sources drive the most engaged users.

Tool: M

ICROSOFT_CLARITY_DATA_EXPORT

4. Geographic User Behavior

Analyze user engagement patterns across different countries and regions.

Tool: M

ICROSOFT_CLARITY_DATA_EXPORT

Configuration: num

OfDays: 3, dimension1: "Country/Region", dimension2: "Device"

Example prompt: "Get Clarity data for the last 72 hours segmented by Country/Region and Device type"

5. Page-Level Performance

Examine which specific U

RLs have the highest or lowest engagement metrics.

Tool: M

ICROSOFT_CLARITY_DATA_EXPORT

Configuration: num

OfDays: 1, dimension1: "U

RL", dimension2: "Device"

Example prompt: "Export yesterday's Clarity data broken down by U

RL and Device"

6. Campaign Attribution Analysis

Evaluate marketing campaign effectiveness through user behavior metrics.

Tool: M

ICROSOFT_CLARITY_DATA_EXPORT

Configuration: num

OfDays: 3, dimension1: "Campaign", dimension2: "Channel", dimension3: "Device"

Example prompt: "Show Clarity engagement data for the last 3 days by Campaign, Channel, and Device"

Known Pitfalls

Limited time window: Data export is limited to the last 1, 2, or 3 days only. The num

OfDays parameter only accepts values of 1, 2, or 3. For longer historical analysis, you need to run exports periodically and aggregate them externally. Dimension name exact match: Dimension values must match exactly as listed (e.g., Country/Region not country or region). Case and slashes matter. Maximum three dimensions: You can segment by up to three dimensions per export. For more complex analysis, run multiple exports with different dimension combinations. Data availability lag: Clarity data may have a short processing delay. Very recent sessions (last few minutes) may not appear in exports. Single tool limitation: The Clarity integration currently offers only the data export tool. For heatmap visualizations and session recordings, use the Clarity web dashboard directly. Response size: Exports with high-cardinality dimensions like U

RL combined with other dimensions can produce large response payloads. Consider narrowing your time window or using fewer dimensions.

Quick Reference

ICROSOFT_CLARITY_DATA_EXPORT | Export analytics data with up to 3 dimensional breakdowns |

Available Dimensions:

RL | Specific page U

RL |

Export Microsoft Clarity user behavior analytics directly from Claude Code. Pull heatmap data, session metrics, and engagement insights segmented by multiple dimensions without leaving your terminal.

Toolkit docs: composio.dev/toolkits/microsoft_clarity

Setup

Add the Composio M

CP server to your configuration: https://rube.app/mcp Connect your Microsoft Clarity account when prompted. The agent will provide an authentication link. Ensure your Clarity project has sufficient data collection enabled for the dimensions you want to analyze.

Core Workflows

2. Device Performance Analysis

Analyze how user behavior differs across device types to optimize responsive design.

Tool: M

ICROSOFT_CLARITY_DATA_EXPORT

Configuration: num

OfDays: 3, dimension1: "Device", dimension2: "Browser"

Example prompt: "Show me Clarity metrics for the last 3 days by Device and Browser"

Understand which traffic sources drive the most engaged users.

Tool: M

ICROSOFT_CLARITY_DATA_EXPORT

4. Geographic User Behavior

Analyze user engagement patterns a