Docs: Person profiles updates #8271
Merged
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 ↗︎
|
11 tasks
robbie-c
reviewed
Apr 16, 2024
robbie-c
reviewed
Apr 16, 2024
robbie-c
reviewed
Apr 16, 2024
|
Ok, this is in a pretty good spot at the moment. Will wait for the meeting tomorrow morning before opening up to proper reviews. |
ivanagas
changed the title
| @@ -1,3 +1,3 @@ | |||
| You'll notice that one of the parameters in the `identify` method is a `properties` object. This enables you to set [user properties](/docs/getting-started/user-properties). Whenever possible, we recommend passing in all user properties you have available each time you call identify, as this ensures their user profile on PostHog is up to date. | |||
| You'll notice that one of the parameters in the `identify` method is a `properties` object. If you are capturing person profiles, this enables you to set [user properties](/docs/getting-started/user-properties). Whenever possible, we recommend passing in all user properties you have available each time you call identify, as this ensures their person profile on PostHog is up to date. | |||
There was a problem hiding this comment.
I do feel that, with this change, we should try to standardise person properties or user properties as one term. Otherwise it's going to be confusing to users.
I don't have a strong feeling here as to which one.
There was a problem hiding this comment.
Yes, my plan is to standardize on person properties after we merge this PR.
Co-authored-by: Joe Martin <84011561+joethreepwood@users.noreply.github.com>
Co-authored-by: Raquel Smith <raquelmsmith@users.noreply.github.com>
andyvan-ph
approved these changes
May 22, 2024
joethreepwood
approved these changes
May 22, 2024
Co-authored-by: Andy Vandervell <92976667+andyvan-ph@users.noreply.github.com>
tiina303
approved these changes
May 30, 2024
| @@ -188,6 +188,21 @@ You can view whether a user can be merged into another user using `alias` when [ | |||
|
|
|||
| > Note that when calling `alias` in the frontend SDKs, if you have set any properties onto the anonymous user, they will be merged into the user with `distinct_id`. For more details, see the FAQ on [how properties are managed when identifying anonymous users](/docs/data/identify#how-are-properties-managed-when-identifying-anonymous-users). | |||
|
|
|||
| ## Processing person profiles | |||
There was a problem hiding this comment.
Longer term it would be nice if all person related content would be in person.mdx or similar so it's easy to know where to go and change things and other places include relevant snippets.
ivanagas
commented
May 30, 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
To support the launch of events with person profiles, updating relevant docs. Closes #8265
Notes
As is being discussed, it feels like the case of events with person profiles relatively weak. A lot of functionality seems to work the exact same, which helps limit the amount of docs updates needed. For example, identify and funnels don't really need updates if usage remains consistent.Checklist
vercel.jsonArticle checklist
Useful resources