Important: This feature is currently being tested. If you would like to opt out from the test, please submit a support ticket or speak to your Client Success Manager.
Local storage works similarly to cookies, as it stores data on the user’s device by creating a local identifier. As opposed to cookies, local storage provides you with a channel resilient against browsers blocking trackers and it also complies with cookie regulations.
Web Extend cookies fall into two categories:
- First-party cookies: these store identifiers that are used within the context of a website. Cookie regulations that come into effect in 2023 will not affect first-party cookies, as they are essential to operate a website. They have a 7-day expiration date.
- Third-party cookies: these store cross-site identifiers. Third-party cookies are affected by cookie regulations because they are not essential to operate a website.
Please keep in mind that a site cannot store more than 50 cookies.
For more information, see The Web Extend cookies.
Compared to first-party cookies, Local storage offers you more flexibility as it works without expiration dates, while it provides you with the same tracking capabilities concerning data used within a website’s context.
Please note that cleaning the cache manually will also remove data stored in the local storage.
Local storage-based tracking relies on your Web Extend cookie integration. Emarsys handles local storage-based tracking the same way as it handles cookies. If you were already GDPR compliant, you don't need to take any further actions. For more information, see GDPR and Web Extend - all you need to know.
Known issues and limitations
- Please note that you cannot use Local storage for cross-site identification.
- Emarsys stores pseudonymous identifiers on the client side.