Wingify Network Calls

Updated 2026-09-25View original on help.wingify.com ↗


This article covers the following: * Data Requests * Library Requests + Library Requests for Accounts Enabled With Wingify Data Platform + Library Requests for Non-Data Platform Accounts * Tracking Requests

During any campaign, multiple network calls are exchanged between your website and Wingify servers. Wingify typically exchanges the following calls:

#Data Requests

The following network requests fetch your account data, such as account settings, running campaigns, etc., to apply the campaign changes to the web pages while running your campaigns.

Request	Description
/tag/.js	Serves a combined response of account settings and required libraries. SmartCode 3.0 makes this request to fetch the running campaign settings. It includes data of all the changes that need to be applied to the page and rendered to the visitor.
/v2/dyn	Fetches per-visitor dynamic data (visitor UUID, geo, UA, timestamps, sampling, visitor tracking, related runtime values) that is kept out of the cached SmartCode/settings response. Used with SmartCode 3.0 flows.
j.php	Asynchronous SmartCode makes this request to fetch the running campaign settings based on the current URL. It includes data of all the changes that need to be applied to the page and rendered to the visitor. This is applicable for SmartCode 2.2 and below.
/info	Fetches third-party cookie (TPC) data and the server timestamp so SmartCode can sync cross-domain cookie state and create a session. Used with SmartCode 3.0 flows.
/lib/.js	Synchronous SmartCode makes this request to fetch all running test campaign settings along with web-critical JS library. This is applicable for SmartCode 2.2 and below.
/translations//<lang-code.js>	Fetches campaign changes in the language mentioned in the request's lang-code path. This is available with SmartCode 3.0.
/dcdn/settings.js	Fetches campaign settings for both testing and Behavior Analytics campaigns — including campaigns running on other pages on page load, and during SPA navigation. Primary settings path when Cloud CDN is enabled; falls back to /settings.js if needed.
/cdata/abm/data	Retrieves visitor firmographic and identity details, such as company name and confidence levels, when ABM is active for the account.
/dcdn/questions	Retrieves survey content and question-related data for specific account and survey identifiers to facilitate campaign rendering. This request also supports Link-based and Data Platform survey workflows.
js_visitor_settings.php (deprecated)	Synchronous SmartCode (legacy version) makes this request to fetch test campaign settings based on the current URL. This call performs the same function as j.php does for Asynchronous code.

#Library Requests

Library calls are a core component of Wingify that reads and applies the campaign settings. You can track goal conversions and attach different event listeners to the campaign pages. These calls are important to implement changes during a campaign. The following are the library calls used by Wingify:

Request	Description
//track-.js	JavaScript file to track visitor activities like key up, mouse move, and scroll.
analysis/latest/player.js	JavaScript file for playing session recordings on the Wingify dashboard.
/heatmap.helper-.js	JavaScript file to display the heatmap of a given webpage.
apmLib-.js	JavaScript file that helps showcase Wingify's impact on the website’s performance, setup nudges, etc., in the Websites and Apps section.
static/1.0/cross_store_inject-.js	JavaScript file to store survey data (how many times surveys are shown, current question ID, etc.) in local storage.
/static/1.0/proxy-.html	This file is used in local storage communication in survey campaigns.
/static/latest/styles/themes/cloudy_sea-.css	These files are used to display UI elements for Survey campaigns.
/static//survey/styles/themes/-.css
/static//survey/images/-.svg
/static//styles/wingify/themes/-.css
/static/1.0/images/-
/static//survey/images/image-.png
/theme/_.css
/analysis//opa-.js	JavaScript file that is responsible for running Behavior Analytics campaigns like Session Recordings, Heatmaps, and Funnels(variants: opajq.js, opanj.js).
/analysis//worker-.js	JavaScript file for Behavior Analytics CPU-intensive computation.
/cdn/static//survey/survey-.js	This file is responsible for survey campaign popup functionality.
/static/1.0/survey/survey-.html	This file loads the default HTML for the survey content.
/evad.js	This file is responsible for successfully running preview mode for the survey campaign.
//get_debugger_ui.js	This JavaScript file ensures the functionality of Preview Debugger logs on the UI.

#Library Requests for Accounts Enabled With Wingify Data Platform

Request	Description
/cdn/edrv/vanj-.js	Web Testing, Rollout, and Web Personalization (also supports Behavior Analytics). Served when “Use existing jQuery” is enabled in SmartCode, or jQuery is already on the page before SmartCode; otherwise, va_gq is served.
/cdn/edrv/va_gq-.js	Same core library as above, with Wingify’s jQuery variant when existing jQuery is not used.
/cdn/edrv/va-.js	Core library variant that includes jQuery (used when applicable for the account/SmartCode config).
/cdn/edrv/worker-.js	Runs tasks in a background worker thread to reduce SmartCode impact on page performance.
/cdn/edrv/nc-.js	Non-critical tasks (e.g. page unload metric handling).
/cdn/edrv/beta/nc-.js	Non-critical tasks for Smartcode 3.0 (e.g. page unload metric handling).
/cdn/static//va_survey-.js	This JavaScript file creates the required iFrame for survey campaigns.
/va_survey_debug_events-.js	This file is responsible for some functionalities in preview mode for the survey campaign.
lib/emotionsai-.js	Emotions library (only when Emotions is enabled for the account).
/analysis//opaEv-.js	JavaScript file that is responsible for running Behavior Analytics campaigns like Session Recordings, Heatmaps, and Funnels for Data Platform (variants: opaEv_ng, opaEv).

#Library Requests for Non-Data Platform Accounts

Request	Description
/tag-.js	JavaScript library to run test and Behavior Analytics campaigns, in one or two requests based on the account’s performance-related configuration.
/vis_opt.js (deprecated)	Web Testing, Rollout, and Web Personalization (also Behavior Analytics). Legacy SmartCode.
/vis_opt_no_jquery.js (deprecated)	Same as above, using the website’s jQuery. Legacy SmartCode.

#Tracking Requests

Pixel calls track visitor actions, goal conversions, visitor settings, timeouts, etc.

Request	Description
/l.gif	Tracks visitors who become part of the test.
/h.gif	Heatmap clicks — up to 10 (default, configurable) visitor clicks per session where the campaign is running.
/c.gif	Goal/metric conversion tracking for testing campaigns.
/v.gif	Unique visitors and timeouts for loading account settings data.
/t.gif	Visitor settings timeouts for non-Data Platform accounts.
/s.gif	Sent when a visitor gets sampled.
/ee.gif	Client-side error/failure tracking in Data Platform (e.g. library load failures).
/e.gif	Client-side error/failure tracking in non-Data Platform (e.g. library load failures).
/analyze	Records the visitor’s session.
/events/t	Event tracking (variation shown, metric/goal conversion, visitor attributes, clicks, etc.). Data Platform accounts only.
/events/t/u	Same event pipeline for unregistered/certain event types. Data Platform accounts only.
/events/survey	Survey-related event tracking for Data Platform accounts.
/events	Survey response tracking for non-Data Platform accounts.
/ping_tpc.php	Creates third-party cookies for cross-domain campaigns.
/cdc_exp	Creates third-party preview cookie (_vis_preview_) for cross-domain campaign preview.
/apm	Captures payload data for apmLib functionality.
/abm/identify	Transmits visitor profile information, including email addresses and organisational domains, to facilitate ABM identity resolution. This request is utilised when the ABM feature is active for the account.
/emotionsai/score	This endpoint collects data related to Emotions personality scoring.

Note: Safari-specific variants: These versions (for example, worker_safari-.js) deliver the same core functionality while addressing browser-specific technical requirements. SmartCode automatically serves these variants to visitors when applicable.

#Need more help?

For further assistance or more information, contact Wingify Support.