From 13363cf2592a95a249d7baa695cae19982a0bf0e Mon Sep 17 00:00:00 2001 From: Abigail <51999607+abigailbramble@users.noreply.github.com> Date: Fri, 20 Dec 2024 16:27:18 +0000 Subject: [PATCH] Update contents/docs/data/anonymous-vs-identified-events.mdx Co-authored-by: Lior539 --- contents/docs/data/anonymous-vs-identified-events.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contents/docs/data/anonymous-vs-identified-events.mdx b/contents/docs/data/anonymous-vs-identified-events.mdx index a5c901a18924..9cf370274dc2 100644 --- a/contents/docs/data/anonymous-vs-identified-events.mdx +++ b/contents/docs/data/anonymous-vs-identified-events.mdx @@ -168,7 +168,7 @@ Note that the above initial parameters will only work across subdomains if you'r Any other initial [person properties](product-analytics/person-properties#default-person-properties), including initial [GeoIP properties](https://posthog.com/docs/product-analytics/person-properties#geoip-properties) will be set from the values in the event at the time that the person profile was created i.e. when the events became identified. -### If we change our `person_profiles` config to `'always'` away from `'identify-only'`? Will we get all the person data from the previously captured anonymous events? +### If we change our `person_profiles` config from `identified_only'`to `always`, will we get all the person data from the previously captured anonymous events? No, anonymous events only capture the event data and none of the person data. If that person is identified at a later date – either by identifying them or changing your configuration settings – there isn't a way to retrieve the person properties from the previously captured anonymous events.