You need to provide an anonymous or pseudonymous user identifier for each userToken when tracking Insights events. To identify users consistently, you should provide your own user IDs.
The search-insights library can also generate anonymous user IDs that it stores in a cookie.
This cookie is named _ALGOLIA and identifies users for your Search Analytics and Personalization. You can find more details in this article.
If you’d like to store cookies by setting the useCookie:true, you will need to obtain user consent based on your legal requirements before storing cookies on a customers device.
For a full list of common userToken issues, troubleshooting topics and best practices, see our summary article here.