This is an automated email from the ASF dual-hosted git repository.

sergehuber pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/unomi-tracker.git


The following commit(s) were added to refs/heads/main by this push:
     new 760fb97  UNOMI-1019: Document which deployments keep the visitor 
profile (#38)
760fb97 is described below

commit 760fb975c973da185bea48caf6f55018de92933a
Author: Serge Huber <[email protected]>
AuthorDate: Tue Nov 3 12:26:39 2026 +0100

    UNOMI-1019: Document which deployments keep the visitor profile (#38)
    
    The profile cookie is set by Unomi on its own host. Behind a reverse
    proxy or on the same domain, browsers keep it; on another domain it is
    a third-party cookie, which Safari blocks. The tracker does not send its
    own copy of the profile ID yet (UNOMI-733).
    
    Co-authored-by: Claude Opus 5.5 <[email protected]>
---
 README.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/README.md b/README.md
index c75b761..a0dd185 100644
--- a/README.md
+++ b/README.md
@@ -106,6 +106,18 @@ If the site does not need to recognise visitors, set 
`sendCredentials: false`. R
 
 See the [web tracker 
reference](https://unomi.apache.org/manual/latest/#_unomi_web_tracker_reference)
 in the Unomi manual for details.
 
+Deploying the website and Unomi
+-------------------------------
+Unomi recognises a returning visitor by its profile cookie 
(`context-profile-id`), which it sets on its own host. Whether browsers keep 
that cookie depends on where Unomi is, compared with the website:
+
+| Setup | Example | Profile cookie |
+|---|---|---|
+| Same host, Unomi behind a reverse proxy | `contextServerUrl: 
'https://www.example.com/unomi'` | First-party: kept by all browsers. 
Recommended |
+| Another host on the same domain | `www.example.com` and `cdp.example.com` | 
Same site: kept by all browsers. Unomi 4 must list the website origin, see 
above |
+| Another domain | `www.example.com` and `unomi.example.net` | Third-party: 
blocked by Safari, and by Chrome in private windows or when the user blocks 
third-party cookies. Firefox keeps a separate one for each website |
+
+When the browser blocks the profile cookie, Unomi sees the visitor as with 
`sendCredentials: false` (see above): a new profile on each request with Unomi 
4, a profile for the session only with Unomi 2.x and 3.x. The tracker cannot 
keep the profile itself yet: it copies the profile ID into its own cookie 
(`trackerProfileIdCookieName`), on the website's host, but does not send it to 
Unomi (UNOMI-733).
+
 Configuration options
 ---------------------
 Options in `wemInitConfig`:

Reply via email to