From ce02bcfe3ef0efbde9adc1409923346537cc1a83 Mon Sep 17 00:00:00 2001 From: "inkeep[bot]" <257615677+inkeep[bot]@users.noreply.github.com> Date: Thu, 4 Jun 2026 20:14:55 +0000 Subject: [PATCH] docs: add caution callout for 100% sampling with ANY matching misconfiguration Reflects the warning banner added in PostHog/posthog#61718 that alerts users when 100% sampling combined with "any" matching and other conditions causes all sessions to be recorded. --- .../how-to-control-which-sessions-you-record.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/contents/docs/session-replay/how-to-control-which-sessions-you-record.mdx b/contents/docs/session-replay/how-to-control-which-sessions-you-record.mdx index d511578bfc70..8ed6ee76200e 100644 --- a/contents/docs/session-replay/how-to-control-which-sessions-you-record.mdx +++ b/contents/docs/session-replay/how-to-control-which-sessions-you-record.mdx @@ -171,6 +171,14 @@ You'll capture 20% of every session, and any session that has an exception event You'll capture 20% of any session on the checkout page that has an exception event. + + +If you use "any" matching with 100% sampling and other conditions (URL triggers, event triggers, or feature flags), the 100% sampling causes every session to be recorded. Your other conditions become ineffective because the sampling condition alone matches every session. + +To fix this, either lower your sample rate or switch to "all" matching. + + + ## Trigger groups Trigger groups are a more flexible way to configure recording triggers. Each trigger group can have its own combination of URL triggers, event triggers, feature flags, sample rate, minimum duration, and match type (ANY/ALL).