When`disableClientPersistence` is set to`true`, Analytics.js won't store any pending events into`localStorage`.

To access or assign a value to a cookie outside of the standard Segment methods (track/identify/page/group), you can use the following methods. To access the cookie's value, pass an empty`()` at the end of the method. To assign the value, include the string value inside those parenthesis, for example,`('123-abc')`. To clear or remove the value for a specific field, pass in an empty value of its type. For example, for string`('')`, or for object`({})`.

By default, Analytics.js uses`localStorage` as its preferred storage location, with Cookies as a fallback when`localStorage` is not available or not populated. An in-memory storage is used as a last fallback if all the previous ones are disabled.

Default Storage Priority:

LocalStorage -> Cookie -> InMemory

Some scenarios might require a switch in the storage systems priority:

- Apps that move the user across different subdomains

- Apps where the server needs control over the user data

- User Consent

- Availability

You can configure the storage priority in the Analytics.js client using the`storage` property, either globally or only for user or group data.

The`storage` property accepts an array of supported storage names (`localStorage`,`cookie`,`memory`) to be used in the priority order of the array.

analytics.load('writeKey', {

storage: ['cookie','localStorage','memory']

user: {

storage: ['cookie','localStorage','memory']

},

group: {

storage: ['cookie','localStorage','memory']

},

}