LimeSpot mainly uses script-writable browser storage (localStorage and sessionStorage) and uses browser cookies as a backup mechanism for storing values in the user's browser if there's no access to script-writable storage.
We do not rely on sending cookies in the traditional way back to our servers. In other words, these values are only used by our scripts on your website to facilitate authentication and creation of a session, either anonymous or logged-in, and not directly consumed on our servers.
Here's a list of all the Cookies and script-writable browser storage items LimeSpot uses for delivering personalization.
Cookies:
Name | Domain | Description |
lsContextID | Website | Authentication information of current browsing session. Expires immediately. |
lsSema-* | Website | Semaphore cookies. Values written are immediately removed. Expires immediately. |
Local Storage:
Name | Domain | Description |
lsUserID | Website, personalizer.io | Identifier assigned to the user. |
lsEncUserID | Website, personalizer.io | Encrypted version of userID. |
lsAuthParams | Website | Parameters used to authenticate a session to obtain rendering settings. |
lsAuthResult | Website | Results of a session authentication that includes rendering settings. |
lsContext | Website | Information about current session. (e.g.: currency code, e-commerce provider, etc) |
lsContextExpires | Website | Expiry date of the session context. Set for 2 hours after the last visit. |
lsRecentViews | Website | Recently viewed items of the user. |
lsActivities | Website | User activities queue |
Note: Cookies placed by LimeSpot are accessible from our scripts on edge.personalizer.io. (storefront.js). This file is loaded asynchronously via Shopify script tags on page load. It's not added to a store's codebase as asset files and is hosted on our servers. This code cannot be changed and is minified.
Note: To stop LimeSpot from loading (which leads to placing the storage items and cookies and tracking the user), you can add LimeSpot.DisableAutoInitialize = true; inside the Code section of the LimeSpot Designer tool. This is specially useful for scenarios where you need user's consent before enabling the tracking (e.g. GDPR, CCPA). You can then call LimeSpot.Storefront.Initialize(); once the user has consented.
Note: The changing restrictions on 1st and 3rd party cookies (introduced early 2021) do not generally affect the way LimeSpot works. The only change affecting LimeSpot functionality is the way Apple Safari purges all script-writable storage on behalf of the user if they don't interact with a certain website for 7 days. This means that if an anonymous user doesn't visit your website or any other LimeSpot-powered store for 7 days or more, they'll be categorized as a new user upon the revisit until they log in (e.g. placing an order) after which their most recent shopping behavior is merged back. Other browsers do not purge the browser's storage unless manually initiated by the user.