User login
Link user sessions to persistent user identifiers to support personalization after login.
Last updated
Was this helpful?
Link user sessions to persistent user identifiers to support personalization after login.
If you use the Personalization module, FactFinder needs to know which session belongs to which user. To do that, send a login event whenever a user logs in to your shop.
sid
essential
Use this to pass the user’s session identifier. It is only needed to link the session to the user and must be anonymized.
userId
essential
Use this to pass a user identifier. Like the session ID, it must be anonymized. Unlike sid, it stays the same when users return. This parameter is required for this event.
If your shop does not use permanent user accounts, provide another identifier with a longer lifespan than a session, such as a cookie ID. That allows personalization to reuse what it learned in the user’s next shopping session. You can also first assign the session to the cookie through the login event and later reassign it to the actual user ID once it becomes known.
The REST API documentation is part of the search application and is available at [your NG server]/fact-finder/swagger-ui.html. You can also access it here:
Swagger Link: https://ng-demo.fact-finder.de/fact-finder/swagger-ui.html
In addition to the parameter documentation, you can test requests and inspect the results directly. Because the documentation is built with Swagger, you can also use Swagger Codegen to generate a client.
Login event documentation is available through the login method in the tracking resource.
Last updated
Was this helpful?
Was this helpful?

