All Collections
Troubleshooting & FAQ (Frequently Asked Questions)
Advanced Topics
Cookies & Local Storage Fera May Save for Shoppers
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 week ago

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 langauge, 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.Cart:

  • Type: Cache (mostly)

  • Description: Fera has the ability to customize the appearance of widgets depending on the cart contents. Cart contents aren't always available so it would require a query to the server to get them, however this storage allows us to cache

  • Required: No

  • Effect of Removing: Slower loading of Fera for some stores (~1%)

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.

Local Storage Customer Experience Keys

These local storage keys exist to optimize and improve the customer's experience based on their preferences:

Key: Fera.Skill.*:

  • Type: Customer experience optimization

  • Description: Legacy Fera widget memory that saves current shopper preferences

  • Required? No

  • Effect of Removing: Legacy (no reviews) widgets may not work properly

Key: Fera.AbTests:

  • Type: Customer experience optimization

  • Description: Tracks which bucket the current shopper is in for an A/B test, if any are running. This tells Fera which variation of the A/B test to show the shopper.

  • Required? No

  • Effect of Removing: Shopper many see flip-flopping content if a merchant is running an A/B test since Fera won't be able to remember which A/B test variation it showed the customer the first time.

Key: Fera.EventHistory:

  • Type: Customer experience optimization

  • Description: When Fera requests widget content (like reviews list displays or customer photo galleries) it sends view history to ensure that A/B test buckets are set to the right variation.

  • Required: No

  • Effect of Removing: Shopper may see the same widget content more than once.

Key: Fera.SocialProof.seenTracker :

  • Type: Customer experience optimization

  • Description: Reduces duplicate displays of social proof event feeds (like reviews submitted by other shoppers)

  • Required: No

  • Effect of Removing: Shopper may see the same widget content more than once.

Key: Fera.Fera.EngagementRegistry.historicalEngagements:

  • Type: Customer experience optimization

  • Description: Reduces duplicate displays of social proof event feeds (like reviews submitted by other shoppers)

  • Required: No

  • Effect of Removing: Shopper may see widgets/reviews that are less relevant to them.

Key: Fera.TimeTracker.*:

  • Type: Customer experience optimization

  • Description: Some content does not show immediately depending on some merchants' advanced widget configurations. This timer tells Fera when to show the widget content, even if the shopper navigates to another page (must be on site)

  • Required: No

  • Effect of Removing: Content that would normally show after a certain amount of time (like for returning shoppers) may not show.

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.

  • 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.

Did this answer your question?