close this to read article
This article covers the following:
- Data Requests
- Library Requests
- Library Requests for Accounts Enabled With Wingify Data360
- Library Requests for Non-Data360 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 |
|---|---|
| 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 |
| <account-id>.js | Synchronous SmartCode makes this request to fetch all running test campaign settings along with web-critical JS library |
| settings.js | This request fetches test campaign settings for the campaigns running on other pages on page load and insights campaigns during SPA navigation |
| 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 |
|---|---|
| /<version>/track-<hash>.js | This is a Javascript file to track visitor activities like key up, mouse move, and scroll |
| analysis/latest/player.js | This is a Javascript file for playing the session recordings on the Wingify dashboard |
| <version>/heatmap.helper.js | This is a Javascript file to display the heatmap of a given webpage |
| apmLib-<hash>.js | This is a Javascript file that helps showcase Wingify's impact on the website’s performance, setup nudges, etc., in the Websites and Apps section |
| static/cross_store_inject-<hash>.js | This is a Javascript file to store survey data like how many times surveys are shown, the current question ID, etc., in the local storage |
| /static/latest/styles/themes/cloudy_sea-<hash>.css | These files are used to display UI elements for Surveys campaigns |
| /static/<version>/survey/styles/themes/<style-file-name>-<hash>.css | |
| /static/<version>/survey/images/image-<hash>.svg | |
| /static/<version>/survey/images/image-<hash>.png | |
| /theme/<accid>_<hash>.css | |
| /analysis/<version>/opa-<hash>.js | This Javascript file is responsible for the functioning of Session Recordings, Heatmaps, and Funnel campaigns. NOTE: This has variants like opajq.js and opanj.js |
| /analysis/<version>/worker-<hash>.js | This Javascript file is loaded in the worker thread used for performing insights campaign-related CPU-intensive computation |
| /<version>/track-<hash>.js | This is the Javascript file responsible for the functionality of Insights Goal campaigns to track visitor activities like key up, mouse move, and scroll |
| /survey-<hash>.js | This is the Javascript file responsible for the functionality of the survey campaigns to showcase the popup |
| /evad.js | This is the Javascript file responsible for the display of the campaign preview |
| /<version>/get_debugger_ui.js | This is the Javascript file responsible for the display of the logs in the preview debugger when previewing a campaign |
Library Requests for Accounts Enabled With Wingify Data360
| Request | Description |
|---|---|
| /cdn/edrv/vanj-<hash>.js | These are the Javascript files responsible for the functionality of the Web Testing, Rollout, and Personalize campaigns primarily while also supporting Web Insights functionality. NOTE: vanj file is served when the Use existing jQuery option is enabled in the SmartCode (Refer to this section to learn more about this option), or it’s already present on the website before SmartCode; otherwise va_gq is served. |
| /cdn/edrv/va_gq-<hash>.js | |
| /cdn/worker-<hash>.js | This JavaScript file minimizes the impact of Wingify SmartCode on your website’s performance by running tasks in the background (worker thread) |
| /cdn/edrv/nc-<hash>.js | This JavaScript file handles non-critical tasks like page unloading metric handling |
| /va_survey.js | This is the Javascript file responsible for the functionality of the survey campaigns by creating the required iFrame. |
| /survey-<hash>.js | This JavaScript file manages the logic and behavior of survey campaigns, controlling when and how the survey popup is displayed to visitors. It also captures the responses and tracks visitor behavior during the survey interaction |
| /va_survey_debug_events-<hash>.js | This Javascript file is sent as a request to fetch a survey preview |
Library Requests for Non-Data360 Accounts
| Request | Description |
|---|---|
| /tag-<encoded string>.js | This Javascript file contains the Javascript library code run test and insights campaigns on your website either in one request or two based on the account’s performance-related configuration |
| /vis_opt.js (deprecated) | This Javascript file is responsible for the functionality of the Web Testing, Rollout, and Personalize campaigns primarily, while also supporting Web Insights functionality. NOTE: These libraries are served for legacy Wingify SmartCode. |
| /vis_opt_no_jquery.js (deprecated) | This Javascript file uses the website’s jQuery and is responsible for the functionality of the Web Testing, Rollout, and Personalize campaigns primarily, while also supporting Web Insights functionality. NOTE: These libraries are served for legacy Wingify SmartCode. |
Tracking Requests
Pixel calls track visitor actions, goal conversions, visitor settings, timeouts, etc.
| Request | Description |
|---|---|
| /l.gif | This is for tracking visitors who become a part of the test. |
| /h.gif | This call is used to create a heatmap based on the maximum of 10 (by default, otherwise configurable) visitor clicks in a session anywhere on the website limited where the campaign is running. By default, in a single session, this call can be fired 10 times at the most |
| /c.gif | This tracks the goal conversion of metrics in the testing campaign |
| /v.gif | This tracks unique visitors and timeouts for loading account settings data |
| /t.gif | This tracks visitor settings timeouts for non-Data360 accounts |
| /s.gif | This is sent when a visitor gets sampled |
| /analyze.js | This records the visitor’s session |
| /events/t | This tracks event-related information like variation shown, metric/goal conversion, visitor attributes, clicks, conversions, etc. sent to the Wingify servers NOTE: This is exclusive to Data360 accounts |
| /ping_tpc.php | This creates third-party cookies for cross-domain campaigns |
| /cdc_exp | This request creates third-party cookies of the Wingify preview (_vis_preview_<account-id>) cookie for the campaign preview to work cross-domain for cross-domain campaigns |
| /apm | This captures the data in its payload for supporting apmLib functionality |
| /events | This request tracks survey responses. NOTE: This is only for non-Data360 accounts. |
Need more help?
For further assistance or more information, contact Wingify Support.