APEX-156: User tracking improvements #30
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
…order to prevent HTTP 422's in the Event Debugger when useCookie is set to false
sbellone
approved these changes
Apr 25, 2023
Merged
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.
Since SeachInsights v2 changed the default value of
useCookietofalse, a randomly-generated session-persistent userToken is no longer generated and saved to the_ALGOLIAcookie.This also means that a
userTokenneeds to be explicitly set in the code whenuseCookieis set tofalse, otherwise events without auserTokenwill not be forwarded and will raise an HTTP 422 error.Added a page-persistent randomized userToken to each call in order to prevent the HTTP 422 errors.