Skip to content

docs(replay-vision): add group properties to scanner filter options#18836

Open
inkeep[bot] wants to merge 1 commit into
masterfrom
docs-writer-ai-update-2026-07-22T23-05-56-820Z-l2az2f
Open

docs(replay-vision): add group properties to scanner filter options#18836
inkeep[bot] wants to merge 1 commit into
masterfrom
docs-writer-ai-update-2026-07-22T23-05-56-820Z-l2az2f

Conversation

@inkeep

@inkeep inkeep Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Changes

This PR updates the Replay Vision scanner documentation to reflect that group properties are now available as filter options when configuring scanner recording filters.

What changed

Added Group properties to the list of available filter types in the "Filters: scoping the scanner" section of contents/docs/replay-vision/creating-scanners.mdx.

The updated filter list now includes:

  • Person properties (e.g. plan tier, signup date)
  • Group properties (e.g. company name, account tier) – requires group analytics ← NEW
  • Session properties (duration, page count, country)
  • Cohorts
  • Events the session contains

Why

PR PostHog/posthog#73019 adds group properties to the scanner filter taxonomy by appending groupsTaxonomicTypes from groupsModel to the scanner's filter type array. This allows group analytics users to filter which sessions a scanner watches by group properties (e.g., company name, account tier).

Previously, this filter option was available in the recordings playlist and the scanner's "Run" tab, but was missing from the scanner setup's "Recording filters" step. The documentation should reflect this new capability.


This PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.

Reflects PR #73019, which adds group property filter support to
the scanner setup's recording filters step.
@inkeep
inkeep Bot requested a review from ksvat July 22, 2026 23:07
@github-actions github-actions Bot added the docs Improvements or additions to product documentation, "Docs" label Jul 22, 2026
@github-actions

github-actions Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Jul 22, 2026 11:19PM

@github-actions

Copy link
Copy Markdown
Contributor

Vale prose linter → found 2 errors, 3 warnings, 5 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/docs/replay-vision/creating-scanners.mdx — 2 errors, 3 warnings, 5 suggestions
Line Severity Message Rule
35:62 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
36:66 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
38:75 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
52:18 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
54:18 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
68:54 warning 'auditable' is a possible misspelling. PostHogBase.Spelling
77:102 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
141:20 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
165:4 warning 'Handing off to Responder agents' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
167:208 warning Use the Oxford comma before 'and' or 'or' in a list of three or more items. PostHogBase.OxfordComma

@github-actions

Copy link
Copy Markdown
Contributor

Bundle report

Total JS (gzip)

6.75 MiB (no change)

Eager graph (modules shipped in each entrypoint's initial chunks)

Entrypoint Eager size Budget Modules
app 16.23 MiB (no change) report-only 1982
Largest modules in the app closure
Module Size
./src/data/mcp-tools.json 897.2 KiB
css ./node_modules/.pnpm/css-loader@5.2.7_webpack@5.101.3/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[1]!./node_modules/.pnpm/postcss-loader@4.3.0_postcss@8.5.6_webpack@5.101.3/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[2]!./src/styles/global.css 747.0 KiB
./src/components/Stickers/Stickers.tsx 696.4 KiB
./node_modules/.pnpm/@radix-ui+react-icons@1.3.2_react@18.3.1/node_modules/@radix-ui/react-icons/dist/react-icons.esm.js 481.4 KiB
./node_modules/.pnpm/rehype-raw@7.0.0/node_modules/rehype-raw/lib/index.js + 29 modules 395.1 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.cjs.js 364.8 KiB
./src/hooks/useCustomers.tsx + 54 modules 355.1 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.es.js 354.8 KiB
./node_modules/.pnpm/react-markdown@8.0.7_@types+react@16.14.66_react@18.3.1/node_modules/react-markdown/lib/react-markdown.js + 88 modules 351.4 KiB
./node_modules/.pnpm/cloudinary-core@2.14.0_lodash@4.17.21/node_modules/cloudinary-core/cloudinary-core.js 281.9 KiB
./src/components/ProductComparisonTable/index.tsx + 120 modules 278.6 KiB
./src/components/SearchUI/index.tsx + 87 modules 272.1 KiB
./node_modules/.pnpm/framer-motion@10.18.0_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/framer-motion/dist/es/render/dom/motion.mjs + 109 modules 253.9 KiB
./node_modules/.pnpm/d3@7.9.0/node_modules/d3/src/index.js + 208 modules 247.4 KiB
./src/components/Pricing/PricingSlider/Slider.tsx + 87 modules 239.9 KiB

Eager-graph budgets are report-only until a baseline is established. Sizes are gzip of public/**/*.js; eager size is webpack module source bytes for the modules actually shipped in the entrypoint's initial chunks (post-tree-shake).

@github-actions

Copy link
Copy Markdown
Contributor

Hey @ksvat! This docs PR was generated for you by an agent. You're responsible for reviewing and merging it into production.

  1. Review and approve the PR
  2. Merge the PR
    a. Check the preview env and CI build and merge it yourself
    b. Enable auto-merge if you're confident in the changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Improvements or additions to product documentation, "Docs"

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

0 participants