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).