sergehuber opened a new pull request, #925: URL: https://github.com/apache/unomi/pull/925
## Summary - The web tracker reference has a new section, "Configuring the tracker for your Unomi server": which `apiKey` to set for Unomi 2.x, 3.x, 4.x in single-tenant compatibility mode and 4.x multi-tenant, with an example. It replaces the note saying the tracker cannot send the key. - Only the tenant's public key goes in the page; no tenant ID is needed; the header triggers a CORS preflight, which 2.x and 3.x servers accept. - The tutorial snippets include `apiKey`, and its warning explains when to remove it. - The 3.0 to 4.0 migration guide (client notes, checklist, "Option 1"), the configuration page and the JavaScript tracker guide link to the new section. - `apiKey` and `sendCredentials` need tracker 2.0.0 or later (https://github.com/apache/unomi-tracker/pull/27). The tracker bundled in `extensions/web-tracker` is still 1.4.0; updating it is a follow-up once 2.0.0 is released. - Without cookies, Unomi 2.x and 3.x keep the profile through the session (Unomi 4 creates a new one per request, as documented). - The tracker profile cookie is `wem-profile-id`, not `web-profile-id`. Behaviour described here was checked with the new tracker browser tests (`yarn test:servers` in apache/unomi-tracker) against 2.7.0, 3.0.0 and 4.0.0-SNAPSHOT. ## Test plan - [x] Every `<<_web_tracker_server_versions>>` link has a matching anchor - [ ] Manual build - [ ] CI 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
