Skip to content

docs(replay-vision): document scanner impact tracking and cohort creation#18625

Open
inkeep[bot] wants to merge 6 commits into
masterfrom
docs-writer-ai-update-2026-07-17T09-28-39-359Z-6gzksc
Open

docs(replay-vision): document scanner impact tracking and cohort creation#18625
inkeep[bot] wants to merge 6 commits into
masterfrom
docs-writer-ai-update-2026-07-17T09-28-39-359Z-6gzksc

Conversation

@inkeep

@inkeep inkeep Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Summary

Documents the new scanner impact tracking and cohort creation features added in PostHog/posthog#70059.

Changes

Scanner types (contents/docs/replay-vision/scanner-types.mdx)

  • Added "Impact and cohorts" subsection to Monitor explaining that monitors track verdict-yes sessions/users over a trailing window, with one-click cohort creation
  • Added "Impact and cohorts" subsection to Classifier explaining per-tag impact tracking and per-tag cohort buttons
  • Added note to Scorer that impact tracking is not yet available in the UI (API supports min_score/max_score)
  • Added note to Summarizer clarifying impact tracking isn't supported for narrative outputs

Observations (contents/docs/replay-vision/observations.mdx)

  • Added new "Scanner impact and cohorts" section with:
    • Table explaining what counts as "affected" for each scanner type
    • Instructions for creating cohorts from scanner results
    • Note about 10,000 user cap per cohort creation

MCP (contents/docs/replay-vision/mcp.mdx)

  • Added "Impact and cohorts" tool group documenting:
    • vision-scanners-impact-retrieve with scanner-type-specific qualifiers
    • vision-scanners-affected-cohort-create for saving affected users as static cohorts
  • Added example prompts for impact queries and cohort creation

Cohorts (contents/docs/data/cohorts.mdx)

  • Added "Method 4: Create a cohort from Replay Vision scanner results" to the cohort creation methods
  • Updated static cohorts section to mention Replay Vision as a source

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.

inkeep Bot added 6 commits July 17, 2026 09:30
Documents the two new MCP tools added in PR #70059:
- vision-scanners-impact-retrieve
- vision-scanners-affected-cohort-create

Adds corresponding example prompts.
…canner results

Reflects PR #70059 which adds impact counts and one-click cohort creation
to Replay Vision scanners. Monitors support verdict-yes cohorts, classifiers
support per-tag cohorts, scorers require a score threshold, and summarizers
are not supported.
@inkeep
inkeep Bot requested a review from fasyy612 July 17, 2026 09:37
@github-actions

github-actions Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Jul 17, 2026 09:50AM

@github-actions

Copy link
Copy Markdown
Contributor

Vale prose linter → found 0 errors, 27 warnings, 15 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/data/cohorts.mdx — 0 errors, 21 warnings, 2 suggestions
Line Severity Message Rule
26:54 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
28:54 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
32:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
34:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
38:23 warning Avoid trivializing words. 'easily' can sound dismissive to the reader. PostHogDocs.Trivializers
58:22 warning Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. PostHogBase.ProductNames
59:13 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
59:28 warning Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. PostHogBase.ProductNames
59:50 warning Capitalize 'Surveys' for PostHog's product. Use 'surveys' for the general industry concept. PostHogBase.ProductNames
60:17 warning Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept. PostHogBase.ProductNames
65:167 warning 'inlined' is a possible misspelling. PostHogBase.Spelling
135:5 warning 'Method 4: Create a cohort from Replay Vision scanner results' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
137:172 warning Capitalize 'Surveys' for PostHog's product. Use 'surveys' for the general industry concept. PostHogBase.ProductNames
137:230 warning Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. PostHogBase.ProductNames
194:69 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
225:46 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
225:133 warning Avoid trivializing words. 'easy to' can sound dismissive to the reader. PostHogDocs.Trivializers
268:87 warning Use 'Gmail' instead of 'gmail'. Vale.Terms
268:105 warning 'hotmail' is a possible misspelling. PostHogBase.Spelling
269:95 warning Use 'UK' instead of 'uk'. Vale.Terms
291:200 warning Use the Oxford comma before 'and' or 'or' in a list of three or more items. PostHogBase.OxfordComma
297:73 warning Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. PostHogBase.ProductNames
299:4 warning 'FAQ' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
contents/docs/replay-vision/observations.mdx — 0 errors, 6 warnings, 4 suggestions
Line Severity Message Rule
47:38 suggestion Address the reader directly. Use 'you' instead of 'The user'. PostHogDocs.DirectAddress
58:81 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
67:5 warning 'Monitor: count flagged sessions over time' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
84:5 warning 'Monitor: true rate (flagged / total)' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
101:5 warning 'Classifier: top tags' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
146:5 warning 'Summarizer: recent summaries' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
163:5 warning 'Summarizer: top friction points' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
165:101 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
165:115 warning 'Unnesting' is a possible misspelling. PostHogBase.Spelling
232:206 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
contents/docs/replay-vision/scanner-types.mdx — 0 errors, 0 warnings, 9 suggestions
Line Severity Message Rule
47:8 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
48:8 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
49:8 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
53:18 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
93:26 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
137:50 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
157:35 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
159:54 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
175:19 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress

@github-actions

Copy link
Copy Markdown
Contributor

Bundle report

Total JS (gzip)

6.73 MiB (+0.3 KiB / +0.0%)

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

Entrypoint Eager size Budget Modules
app 16.10 MiB (+2.8 KiB / +0.0%) report-only 1956
Largest modules in the app closure
Module Size
./src/data/mcp-tools.json 833.6 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 737.9 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 271.8 KiB
./gatsby-browser.tsx + 45 modules 247.7 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 @fasyy612! 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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants