Start Free trial

Articles in this section

Host Wingify JavaScript Files on Your Server

Jash Unadkat
  • Updated
Share:
close this to read article
Note: This tab covers self-hosting for Data Platform accounts. Data Platform accounts only need to self-host the global static file. No test-specific files are required. If you are on a Non-Data Platform account, switch to the Non-Data Platform Accounts tab.

This article covers the following:

Overview

With Wingify JavaScript files hosted on your server, your website doesn't need to contact a Wingify server for loading test variations.

Why Self-Host the Wingify JavaScript Files?

As a website owner, you may be skeptical about using external JavaScript from a third party. For your requirements, you may want to remove the dependency on Wingify servers and have all the test resources under your control. Using the self-hosting option, you can store the Wingify JavaScript files locally to ensure that the test settings, files, and code for your tests reside on your server.

For such self-hosting websites, the Wingify servers only register visits and conversions. Typically, self-hosting is more relevant if the Wingify Content Delivery Network (CDN) does not have a node in or near your country.

Note: Wingify does not have any control over the JavaScript files hosted on your local servers. You receive an email notification for any updates required to the files due to bug fixes and feature changes.

Few things to Consider:

  • The Geo-targeting functionality will not work if you have opted to self-host your Wingify JavaScript files. Self-hosted files do not interact with Wingify servers, and therefore geo-targeting the test will not be possible.
  • You cannot run a test across multiple domains if you have opted to self-host your Wingify JavaScript files.
  • The option to self-host Wingify JavaScript files is supported only for the Wingify Web Experimentation. Behavior Analytics functionalities are not supported.
  • You cannot set up or use a Custom URL when you are self-hosting the Wingify JavaScript files.
  • The live previews option does not work for tests where self-hosting is enabled.

How to Host Wingify JavaScript Files On Your Server

  1. Log in to your Wingify account.
  2. Hover on the profile menu in the top right corner of the dashboard and click Settings.
  3. From the left navigation menu, click Campaigns.
  4. Scroll down to Self-Host campaign JS.
  5. Click Download Script File to download the global static file.
  6. Add the downloaded global static file to your website, within the <head> tag.
Attention: The global static file must be uploaded to your server whenever campaign changes are made. This one file covers every campaign and test on the account. You do not need to download or upload anything separately per campaign. If you make any changes in your account such as starting or pausing a campaign, updating targeting rules, or adding goals, download the file again and replace it on your server.

Note: The filename shown on this page depends on when your account was created:

  • Before June 14, 2026: vwo_static.js
  • On or after June 14, 2026: wingify_static.js

Self-Hosting Option for an Existing Test

There is no separate option to enable or disable self-hosting for an individual test. If you self-host Wingify JavaScript files on your own server, note that the Adhere to Do Not Track feature does not apply.

Note: Self-hosting Wingify JavaScript files is not supported for Wingify Behavior Analytics.

Host JavaScript Files for Multiple Tests on a Single Page

If you are running multiple tests on a single page, you do not need to download or upload separate files. The single global static file (wingify_static.js) you downloaded in How to Host Wingify JavaScript Files On Your Server already contains everything required for all tests running on your account and automatically covers all tests on the page.

Need more help?

For further assistance or more information, contact Wingify Support.

Note: This tab covers self-hosting for Non-Data Platform accounts, which require both the global static file and test-specific files for each test. If you are on a Data Platform account, switch to the Data Platform Accounts tab.

This article covers the following:

Overview

With Wingify JavaScript files hosted on your server, your website doesn't need to contact a Wingify server for loading test variations.

Why Self-Host the Wingify JavaScript Files?

As a website owner, you may be skeptical about using external JavaScript from a third party. For your requirements, you may want to remove the dependency on Wingify servers and have all the test resources under your control. Using the self-hosting option, you can store the Wingify JavaScript files locally to ensure that the test settings, files, and code for your tests reside on your server.

For such self-hosting websites, the Wingify servers only register visits and conversions. Typically, self-hosting is more relevant if the Wingify Content Delivery Network (CDN) does not have a node in or near your country.

Note: Wingify does not have any control over the Wingify JavaScript files hosted on your local servers. You receive an email notification for any updates required to the files due to bug fixes and feature changes.

Few things to Consider:

  • The Geo-targeting functionality will not work if you have opted to self-host your Wingify JavaScript files. Self-hosted files do not interact with Wingify servers, and therefore geo-targeting the test will not be possible.
  • You cannot run a test across multiple domains if you have opted to self-host your Wingify JavaScript files.
  • The option to self-host Wingify JavaScript files is supported only for the Wingify Web Experimentation. Behavior Analytics functionalities are not supported.
  • You cannot set up or use a Custom URL when you are self-hosting the Wingify JavaScript files.
  • The live previews option does not work for tests where self-hosting is enabled.

How to Host Wingify JavaScript Files On Your Server

Non-Data Platform accounts need both a global static file and test-specific files.

Global static file (required for all campaigns):

  1. Log in to your Wingify account.
  2. Hover on the profile menu in the top right corner of the dashboard and click Settings.
  3. From the left navigation menu, click Campaigns.
  4. Scroll down to Self-Host campaign JS.
  5. Click Download Script File to download the global static file.
  6. Add the downloaded global static file to your website.
Attention: The global static file must be uploaded to your server each time a change is made.

Test-specific file (required in addition, per test):

  1. Open the test's details page and turn on the self-hosting option in the View/Edit Test Details section.
  2. Download the test-specific file, for example, vwo_test_123.js (accounts created before June 14, 2026) or wingify_test_123.js (accounts created on/after June 14, 2026).
  3. Upload the test-specific file to your server, followed by the global statis file (vwo_static.js/vwo_no_jquery.js or wingify_static.js/wingify_no_jquery.js, depending on when your account was created).
Note: If you are running multiple tests on the same page, upload one test-specific file for each test. Upload the global static file only once, because it works for all your tests. To know more about file names by account creation date, see Host JavaScript Files for Multiple Tests on a Single Page.

Self-Hosting Option for an Existing Test

If you self-host the Wingify JavaScript files on your own server, note that the Adhere to Do Not Track feature does not apply.

Note: Self-hosting Wingify JavaScript files is not supported for Wingify Behavior Analytics.

Host JavaScript Files for Multiple Tests on a Single Page

If you are running multiple tests on a single page, download the test-specific files (vwo_test_YourCampaignID.js) for each test and upload them to your server. However, you do not need to upload the global static file (vwo_static.js or vwo_no_jquery.js) for each test. This script works for all your tests.

Note: Upload the test-specific files (vwo_test_YourCampaignID.js) first, followed by the common VWO script files (vwo_static.js or vwo_no_jquery.js).

Need more help?

For further assistance or more information, contact Wingify Support.

Was this article helpful?

Return to top

Related articles