Skip to content

docs: Document person properties synced from data warehouse - #18476

Merged
Gilbert09 merged 2 commits into
masterfrom
docs-writer-ai-update-2026-07-14T16-43-36-772Z-i6609j
Jul 15, 2026
Merged

docs: Document person properties synced from data warehouse#18476
Gilbert09 merged 2 commits into
masterfrom
docs-writer-ai-update-2026-07-14T16-43-36-772Z-i6609j

Conversation

@inkeep

@inkeep inkeep Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Summary

Documents the new ability to create person properties that sync from data warehouse tables, added in PostHog/posthog#70090.

Changes

contents/docs/product-analytics/person-properties.mdx

  • Added new section "Syncing person properties from the data warehouse" explaining:
    • How to create person properties from warehouse tables via Customer Analytics configuration
    • Setup steps: selecting Person target, choosing warehouse table, setting distinct ID column, mapping columns
    • Note that warehouse binding and column mappings are immutable after creation
    • Warehouse provenance indicator shown on synced properties
    • These properties work in feature flags, cohorts, insights, and filters

contents/docs/data-warehouse/join.mdx

  • Added subsection "Syncing warehouse data to person properties" under Person joins to:
    • Differentiate between person joins (query-time) and property syncing (persistent)
    • Explain that synced properties are first-class person properties usable everywhere
    • Provide guidance on when to use each approach
    • Link to person properties documentation for setup details

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 2 commits July 14, 2026 16:45
…m data warehouse

Documents the new person-target custom property editor from PR #70090,
which allows creating person properties that sync from warehouse tables.
Also fixes us.posthog.com URLs to app.posthog.com per style guide.
@inkeep
inkeep Bot requested a review from Gilbert09 July 14, 2026 16:47
@github-actions

github-actions Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Jul 14, 2026 04:59PM

@github-actions

Copy link
Copy Markdown
Contributor

Vale prose linter → found 1 errors, 20 warnings, 8 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-warehouse/join.mdx — 0 errors, 3 warnings, 0 suggestions
Line Severity Message Rule
11:23 warning Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. PostHogBase.ProductNames
49:262 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
49:331 warning Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. PostHogBase.ProductNames
contents/docs/product-analytics/person-properties.mdx — 1 errors, 17 warnings, 8 suggestions
Line Severity Message Rule
5:53 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
6:34 warning Use 'MDX' instead of 'mdx'. Vale.Terms
14:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
16:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
18:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
20:66 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
22:303 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
22:341 warning Capitalize 'Surveys' for PostHog's product. Use 'surveys' for the general industry concept. PostHogBase.ProductNames
103:4 warning 'Syncing person properties from the data warehouse' heading should be in sentence case, and product names should be capitalized. PostHogBase.SentenceCase
103:39 warning Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. PostHogBase.ProductNames
105:64 warning Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. PostHogBase.ProductNames
105:137 warning Capitalize 'Customer Analytics' for PostHog's product. Use 'customer analytics' for the general industry concept. PostHogBase.ProductNames
117:157 warning Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. PostHogBase.ProductNames
168:60 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
220:80 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
222:80 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
223:80 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
224:74 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
226:86 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
228:73 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
229:200 warning Use 'Facebook' instead of 'facebook'. Vale.Terms
235:73 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
236:76 suggestion Address the reader directly. Use 'you' instead of 'the user'. PostHogDocs.DirectAddress
236:200 warning Use 'Facebook' instead of 'facebook'. Vale.Terms
253:207 warning 'Nadu' is a possible misspelling. PostHogBase.Spelling
266:207 warning 'Nadu' is a possible misspelling. PostHogBase.Spelling

@github-actions

Copy link
Copy Markdown
Contributor

Bundle report

Total JS (gzip)

6.30 MiB (+0.2 KiB / +0.0%)

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

Entrypoint Eager size Budget Modules
app 15.57 MiB (+0.8 KiB / +0.0%) report-only 1941
Largest modules in the app closure
Module Size
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 709.8 KiB
./src/components/Stickers/Stickers.tsx 696.4 KiB
./.cache/caches/gatsby-plugin-mdx/mdx-scopes-dir/31a094f140f119e73085d847ae81b99b.js + 2 modules 615.0 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.5 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
./gatsby-browser.tsx + 41 modules 239.8 KiB
./src/components/SearchUI/index.tsx + 73 modules 223.4 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 @Gilbert09! 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

@Gilbert09
Gilbert09 merged commit aef6844 into master Jul 15, 2026
19 checks passed
@Gilbert09
Gilbert09 deleted the docs-writer-ai-update-2026-07-14T16-43-36-772Z-i6609j branch July 15, 2026 11:08
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.

1 participant