WingifyGuides

Wingify Local Storage Keys

Updated 2026-09-18View original on help.wingify.com ↗
  • Accounts created before June 14, 2026
  • Accounts created on/after June 14, 2026
This article covers the following: * Overview * Wingify Dependencies on Local Storage Keys * Local Storage Keys Created by Wingify

#Overview

Local storage keys store data in the browser's local storage to save account configurations and visitor states. Unlike cookies, local storage keys are not sent with every HTTP request. They are used only by Wingify's client-side JavaScript libraries to persist information across sessions or page reloads.

Note: Local storage keys persist in the browser until they are deleted manually or programmatically.

#Wingify Dependencies on Local Storage Keys

Wingify relies on local storage keys to ensure the proper functioning of its features, such as tracking user behavior, preserving configurations, and managing experiment states. These keys help Wingify deliver a seamless and consistent user experience across pages and sessions.

#Local Storage Keys Created by Wingify
Key Purpose Applicable for Product(s)
_vwo_nlsCache Stores Behavior Analytics data unique to every session. Wingify Behavior Analytics
_vwo_nls_q_ Prevents data loss for Behavior Analytics campaigns during redirections. Wingify Behavior Analytics - Recordings
vwo_apm_sent Created when Wingify's monitoring JavaScript library is served after sampling to prevent duplicate sampling. NA
vwoSn Stores session information, including the first page of a session and its referrer URL. All
debug_vwoSn This is the same as vwoSn, which is created during the Live Preview of campaigns. All
_vis_opt_ls669061 Used in surveys to store their state. Wingify Behavior Analytics - Surveys
vwo__config Contains the account’s SmartCode config controlled from the app. Refer to Registering Your Website and Apps in Wingify for options. All
_vwo_cD Stores comma-separated visitor identities across domains for cross-domain-enabled campaigns to support Shopify standard events. All
vwo_w_ Stores the widget’s state to manage recurrence and dismissal behavior. Used to track display history and user interactions, enabling controlled widget visibility and preventing unnecessary reappearances. Wingify Web Experimentation, Rollout, and Web Personalization
_vwo_eventHist Stores visitors' relevant data to support historical targeting for personalized campaigns. Refer to Web Personalization With the Power of Historical Targeting in Wingify for more details. Wingify Web Personalization
_vwo_eventHistSession Same as _vwo_eventHist, but restricted to the ongoing session of the visitor.
_vwo_eventHistLastSession Same as _vwo_eventHist, but restricted to the last session of the visitor.
_vwo_syE This contains the event names to sync the client-side historical data to the Wingify backend for supporting server-side historical targeting.
_vwo_syV This contains the visitor attribute names to sync the client-side historical data to the Wingify backend for supporting server-side historical targeting.
_vwo_visProps Caches visitor attributes for immediate access, ensuring consistent targeting on the same site across sessions.

#Need more help?

For further assistance or more information, contact Wingify Support.
This article covers the following: * Overview * Wingify Dependencies on Local Storage Keys * Local Storage Keys Created by Wingify

#Overview

Local storage keys store data in the browser's local storage to save account configurations and visitor states. Unlike cookies, local storage keys are not sent with every HTTP request. They are used only by Wingify’s client-side JavaScript libraries to persist information across sessions or page reloads.

Note: Local storage keys persist in the browser until they are deleted manually or programmatically.

#Wingify Dependencies on Local Storage Keys

Wingify relies on local storage keys to ensure the proper functioning of its features, such as tracking user behavior, preserving configurations, and managing experiment states. These keys help Wingify deliver a seamless and consistent user experience across pages and sessions.

#Local Storage Keys Created by Wingify

Key Purpose Applicable for Product(s)
_wingify_nlsCache Stores Behavior Analytics data unique to every session. Wingify Behavior Analytics
_wingify_nls_q_ Prevents data loss for Behavior Analytics campaigns during redirections. Wingify Behavior Analytics - Recordings
wingify_apm_sent Created when Wingify’s monitoring JavaScript library is served after sampling to prevent duplicate sampling. NA
wingifySn Stores session information, including the first page of a session and its referrer URL. All
debug_wingifySn This is the same as wingifySn, which is created during the Live Preview of campaigns. All
_wingify_ls669061 Used in surveys to store their state. Wingify Behavior Analytics - Surveys
wingify__config Contains the account’s SmartCode config controlled from the app. Refer to Registering Your Website and Apps in Wingify for options. All
_wingify_cD Stores comma-separated visitor identities across domains for cross-domain-enabled campaigns to support Shopify standard events. All
wingify_w_ Stores the widget’s state to manage recurrence and dismissal behavior. Used to track display history and user interactions, enabling controlled widget visibility and preventing unnecessary reappearances. Wingify Web Experimentation, Rollout, and Web Personalization
_wingify_eventHist Stores visitors' relevant data to support historical targeting for personalized campaigns. Refer to Web Personalization With the Power of Historical Targeting in Wingify for more details. Wingify Web Personalization
_wingify_syE This contains the event names to sync the client-side historical data to the Wingify backend for supporting server-side historical targeting.
_wingify_syV This contains the visitor attribute names to sync the client-side historical data to the Wingify backend for supporting server-side historical targeting.

#Need more help?

For further assistance or more information, contact Wingify Support.