Update person-properties.mdx to reference new default #10023
+3
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ivanagas
reviewed
Nov 29, 2024
| @@ -15,7 +15,9 @@ import UserPropertiesSetVsSetOnce from "./\_snippets/user-properties-set-vs-set- | |||
|
|
|||
| For example, you can create [filters](/docs/product-analytics/trends#filtering-events-based-on-properties) or [cohorts](/docs/data/cohorts) based on person properties, which can then be used to [create insights](/docs/product-analytics/insights), [feature flags](/docs/feature-flags), and more. | |||
|
|
|||
| For backward compatibility, PostHog captures [identified events](/docs/data/anonymous-vs-identified-events) that create a [person profile](/docs/data/persons) by default. You can change this by setting your snippet or frontend SDK initialization's `person_profiles` value to `identified_only` or a server-side SDK or API event's `$process_person_profile` property to `false`. | |||
| By default, PostHog's client-side SDKs will send [anonymous events](/docs/data/anonymous-vs-identified-events), meaning that your users will not have a [person profile](/docs/data/persons), unless you call `.identify()`, `.set()`, or another method that uses person profiles. You can change this by setting your snippet or frontend SDK initialization's `person_profiles` value to `always` | |||
There was a problem hiding this comment.
I've been dragging my feet on updating all of these because the default hasn't changed. We are inconsistent here.
Source: https://posthog.slack.com/archives/C06R39WNY5B/p1732255387985419
There was a problem hiding this comment.
Oh my bad, I was basing this off https://posthog.slack.com/archives/C02E3BKC78F/p1732646741093759?thread_ts=1732640114.562429&cid=C02E3BKC78F
There was a problem hiding this comment.
Hmm, that one is newer so we can merge this then.
There was a problem hiding this comment.
Tbh I'd rather leave it at this point, we can get clarity on monday when people are back from thanksgiving
ivanagas
approved these changes
Nov 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
The default has changed, we should update the docs
Checklist
vercel.jsonArticle checklist
n/a
Useful resources