> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Replays Containing Rage Clicks, PostHog

> Replays Containing Rage Clicks for PostHog stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained)  •  **Category:** [Analytics](/nerve-centre/connectors#connectors-by-type)

## At a glance

> **Replays Containing Rage Clicks** is a session-replay metric tracked from PostHog data. It counts the session recordings flagged with rage-click activity, the rapid, repeated clicking on the same spot that signals a frustrated user. PostHog detects rage clicks automatically, so this card is a ready-made queue of the exact sessions where someone hit something that did not work. It is the fastest route from "conversion is down" to watching the friction happen.

|                       |                                                                                                                                                   |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**    | The number of session replays flagged as containing rage-click events in the period.                                                              |
| **Sample type**       | Backend API data from PostHog session-replay frustration signals, refreshed on the standard data refresh.                                         |
| **Why it matters**    | Rage clicks are a direct, behavioural signal of broken or confusing UX. This card hands you the sessions to watch, no guessing required.          |
| **Reading the value** | A rising count, or rage clicks exceeding 10% of replays, means frustration is spreading. Open the flagged replays to see what users are fighting. |
| **Currency**          | count                                                                                                                                             |
| **Time window**       | `7D`                                                                                                                                              |
| **Alert trigger**     | `>10% of replays`                                                                                                                                 |
| **Sentiment key**     | `ph_replays_with_rage_clicks`                                                                                                                     |
| **Roles**             | owner, marketing                                                                                                                                  |

## Calculation

Calculated automatically from your PostHog data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

## Worked example

*A representative reading of **Replays Containing Rage Clicks** for a typical merchant on PostHog.* Suppose 4% of replays usually carry rage clicks. After a checkout button change on 22 Apr 26, that share jumps to 13%, crossing the 10% alert. Watching a few of the flagged replays shows users clicking a "Place order" button that no longer responds on the first tap. The card turned a vague conversion dip into a specific, reproducible bug. Cross-reference Session Quality vs Cart Abandonment to size the revenue impact. For deeper investigation, use Vortex Mind to trace upstream causes; for natural-language exploration, ask Ask Viq.

## Sibling cards merchants should reference together

| Card                                                                                                               | Why merchants reach for it                         |
| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------- |
| [`ph_replay_avg_duration`](/nerve-centre/kpi-cards/posthog/avg-replay-duration)                                    | Session Replay sibling: average replay length.     |
| [`ph_session_replay_count`](/nerve-centre/kpi-cards/posthog/session-replays-captured)                              | Session Replay sibling: total replays captured.    |
| [`ph_xc_session_quality_vs_cart_abandonment`](/nerve-centre/kpi-cards/posthog/session-quality-vs-cart-abandonment) | Cross-channel sibling: frustration vs abandonment. |
| [`ph_funnel_dropoff`](/nerve-centre/kpi-cards/posthog/biggest-funnel-step-drop-off)                                | Funnels sibling: where users abandon.              |
| [`pos_bounce_rate`](/nerve-centre/kpi-cards/posthog/bounce-rate)                                                   | Engagement sibling: bounce rate.                   |

## Reconciling against the vendor's own dashboard

**Where to look in PostHog's own dashboard:**

In PostHog Session Replay, filter recordings by the rage-click event. The count of matching recordings should align with this card. PostHog flags rage clicks based on rapid repeated clicks in a small area, so its detection sensitivity affects the count.

**Why the Vortex IQ value may legitimately differ:**

| Reason                                                                                               | Direction | What to do                      |
| ---------------------------------------------------------------------------------------------------- | --------- | ------------------------------- |
| **Detection sensitivity.** What counts as a rage click depends on click-count and timing thresholds. | Variable  | Confirm the detection settings. |
| **Replay sampling.** If only a sample of sessions is recorded, the count reflects that sample.       | Variable  | Check the sampling rate.        |
| **Period boundary.** A 7-day window versus a different range shifts the count.                       | Variable  | Match the period.               |

**Cross-connector reconciliation:** complement with sibling cards in the same category for the full diagnostic picture. For divergence investigations, use Vortex Mind.

## Known limitations / merchant FAQs

**Q: How often does Replays Containing Rage Clicks update?**
The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). For real-time signals, force a manual refresh from the dashboard.

**Q: What exactly is a rage click?**
A burst of rapid clicks on the same element in a short window, the classic sign of a user repeatedly hitting something that is not responding. PostHog detects it automatically and tags the replay.

**Q: A high rage-click share appeared but conversion looks fine. Why?**
Frustration can precede the revenue impact, or the rage clicks may be on a non-critical element. Watch a sample of the flagged replays to judge severity before raising the alarm.

**Q: Can I customise the alert threshold?**
Yes, sensitivity thresholds are configurable per profile in the Sensitivity tab. Adjust to match your business baseline rather than relying on the generic default.

***

### Tracked live in Vortex IQ Nerve Centre

*Replays Containing Rage Clicks* is one of hundreds of KPI pulses Vortex IQ tracks across PostHog and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

[Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.
