Customize your Wingify SmartCode

Overview

You can customize your Wingify SmartCode in the following ways:

Modify the Cookie Duration

Wingify uses cookies to identify visitors and keep track of the variation they accessed. The default duration of a Wingify cookie is 100 days. To change the duration, you can add the following JavaScript code snippet before the Wingify tracking code on your webpage.

In this example, the cookie will last for a day only. Change the value from 1 to the number of days you want the cookie to be stored. Once the cookies are created, the duration cannot be altered.

<script type = 'text/javascript' >
_vis_opt_cookieDays = 1,
</script>

You can also modify the cookie duration through the Customize SmartCode settings within the Wingify dashboard.

1. Navigate to Configurations > Websites and Apps.
2. Select the specific website for which you want to configure the cookie duration.
3. Navigate to Code > HTML.
4. From the SmartCode section, click the three-dot (⋮) menu and select Settings. This opens the Customize SmartCode dialog box.
5. Select the Cookie configuration checkbox.
6. In the Cookie duration field, specify how long Wingify cookies should persist in the visitor's browser, for example, 30 days, and click Save. 

Once you set the cookie duration, the cookie will persist in the user's browser for the specified duration.

Configure Timeout Interval

By default, the time-out values for the two parameters are 2000 and 2500 milliseconds, respectively. Using the following two parameters of the SmartCode, you can change the time-out interval to counter issues like slow Internet connections or incompatible IE browsers. You can set the time for which the asynchronous script will wait for the page settings to load, using the variable settings_tolerance. If the page settings load within this time interval, the code requests the Wingify library (va.js or vanj.js) from our CDN and waits for the file to load at the interval indicated by the variable library_tolerance.

<script type = 'text/javascript' >
settings_tolerance = 2000,
library_tolerance = 2500,
</script>

Hide an Element

You can customize the SmartCode to hide an element on your webpage. This can be done using the “hide_element” field of the SmartCode. The default functionality of the asynchronous SmartCode is to hide the body of the web page initially. This is to avoid any flash of the original content on the web page while Wingify applies any change.

If you wish to override the default functionality of the asynchronous SmartCode, you can replace the “body” with an empty string. The example code:

<script type = 'text/javascript' >
  hide_element = '', 
</script>

If you make this change, you might encounter issues like a flash of original content on the web page.

Set Domain for Wingify Cookies

In case Wingify cookies are not stored on your domain by default, use the following code to set the domain on which the cookies should be stored. This code snippet must be added before the Wingify tracking code on your webpage.

<script type='text/javascript'>
    var _vis_opt_domain = 'yourdomain.com',
</script>

You can also specify the exact domain for storing cookies by configuring it in the Customize SmartCode settings within your Wingify dashboard.

1. Navigate to Configurations > Websites and Apps.
2. Select the specific website for which you want to configure the cookie domain.
3. Navigate to Code > HTML.
4. From the SmartCode section, click the three-dot (⋮) menu and select Settings. This opens the Customize SmartCode dialog box.
5. Select the Cookie configuration checkbox.
6. In the Cookie domain field, specify the domain, for example, wingify.com.

Once the cookie domain is specified in the Customize SmartCode settings, Wingify cookies will be stored on that domain.

Set the Cookie Path

You can specify the URL path within your website’s domain where Wingify cookies will be active (for example, /sites/one/page). If the path is set to the default, which is just a forward slash (/), it means the cookie is active and used on every single page of the entire website. This is what most tracking tools, like Wingify, do to ensure they track the visitor regardless of the page they visit.

• Example: A cookie path configured as ‘/’ works across the website such as /pricing, /about, and the /homepage

  If you set a specific path, such as /checkout, the cookie will be used and sent to the server only when the visitor is on pages that start with that path (such as /checkout/billing).

• Example: A cookie path configured as /blog will not be used on the /pricing page or the /homepage.

To set the cookie path:

1. Navigate to Configurations > Websites and Apps.
2. Select the specific website for which you want to configure the cookie path.
3. Navigate to Code > HTML.
4. From the SmartCode section, click and select Settings. This opens the Customize SmartCode dialog box.
5. Select the Cookie configuration checkbox.
6. In the Cookie path field, specify the path, for example, /wingify.

Once you set the cookie path, the cookie will only be sent when the user visits URLs that begin with the specified path.

Custom URL Setup

When a campaign has to run on multiple pages with no common pattern in the URL’s or when a campaign needs to run on specific pages, and the URL pattern matches with a lot of pages that do not have to be included, then a Custom URL can be used to create a pattern that matches your requirements. Using custom URLs, you can assign virtual URLs to the pages so that a specific pattern can be generated. The example code:

• Accounts created before June 14, 2026
• Accounts created on/after June 14, 2026

//Replace NEW_VIRTUAL_PAGE_URL with your customized URL)
window.VWO = window.VWO || [];
window.VWO.push(['activate', {
  virtualPageUrl: 'NEW_VIRTUAL_PAGE_URL'
}]);

//Replace NEW_VIRTUAL_PAGE_URL with your customized URL)
window.Wingify = window.Wingify || [];
window.Wingify.push(['activate', {
virtualPageUrl: 'NEW_VIRTUAL_PAGE_URL'
}]);

Need more help?

For more information or further assistance, contact Wingify Support.