Skip to main content
Cookies & Local Storage Fera May Save for Shoppers

Here is a list of all the cookies and local storage data that Fera saves for each shopper on their browser.

Jay El-Kaake avatar
Written by Jay El-Kaake
Updated over a year ago

Basically Fera stores in local storage and cookies for 2 reasons:

  1. Cache - speed optimization

  2. Review submission memory - in case the user is anonymously submitting a review

Local Storage Cache Keys

This data is stored in local storage attributes on the shopper's browser to assist with page load speed times:

Key: Fera.Geo.geolocateIp.*:

  • Type: Cache

  • Description: Caching of IP-based geolocation result that allows reviews to be shown more relevant to the current shopper (in their language, country, etc) even if the shopper is not logged-into the store)

  • Required? No

  • Effect of Removing: Slower customer experience.

Key: Fera.Cache.*:

  • Type: Cache

  • Description: Caches servers-side responses to improve load speed of widgets and things.

  • Required: No

  • Effect of Removing: Slower customer experience (particularly widget displays and on-site review submission modal).

Key: Fera.AssetCache:

  • Type: Cache

  • Description: Caches servers-side CDN assets to improve load speed of widgets and things.

  • Required: No

  • Effect of Removing: Slower customer experience.

Key: Fera.storeSettings:

  • Type: Cache

  • Description: Caches servers-side store settings config to improve load speed of widgets and things.

  • Required: No (however, removing this value after page load and trying to submit a review may give an error)

  • Effect of Removing: Slower customer experience.

Key: Fera.Api.ServerNum

  • Type: Cache

  • Description: Fera maximizes performance by distributing several API servers across the world. This variable saves the API server used.

  • Required? No

  • Effect of Removing: Slower customer experience.

Key: Fera.DevGreeting.*

  • Type: Developer experience optimization

  • Description: We provide some links to developers in the console, but don't want to annoy developers so instead of showing the tips and links after each page load, we remember the last time we showed the tip and don't show it again for a little while.

  • Required? No

  • Effect of Removing: More frequent developer tips/notice in the developer console.

Cookies

There is only 1 cookie that we really have in Fera that is (almost) required:

Key: banana_stand_visitor_id

  • Type: Functionality (Session)

  • Description: Unique, secure session token generated for each shopper so that when they submit a review we have a way to link the review to the current person who is shopping even if they don't log-in. This also allows customers to edit their reviews right after they've submitted them, or resume a session managing their reviews/profile.

  • Duration: 1 year

  • Required?

    • YES if submitting reviews,

    • NO otherwise. That is, anonymous shoppers can delete this cookie.

  • Effect of Removing: Customer won't be able to submit or edit their own reviews - only view them.

If you're using Fera's legacy non-reviews functionality that was removed prior to 2021, then you may want to see this article too.

Did this answer your question?