Available Options for Configuring Custom Segments in Wingify

Overview

The Custom Segments section allows you to create your own segmentation conditions fitting your needs. It provides a set of predefined attributes and events with which you can construct your own segments. 

You can use various properties to create a custom segment. When you click on the first dropdown in the Custom Segments section, a list of properties is displayed; you can either search for the one you need or scan through the list of options. Alternatively, you can use the Category and Source filters to narrow down your search. Furthermore, if you wish to reuse your segment conditions in the future, you can save them using the Save Segment option. You can then reuse saved segments to create new custom segments without recreating existing conditions.

Fundamentally, you just need to select an attribute or an event and define it to set up the segmentation criteria. You can also choose to save the custom segments to be used later in other campaigns.

Available Options for Configuring Custom Segments

Source

• Landing Page URL: This is the page that the user is currently on. This would be helpful in case you are running tests on multiple pages and wish to include the user in a test only when they visit a specific page. Select this option to track visitors who land first on a specific URL before landing on the test page. For example, you can select this option to track only the visitors who first land on the homepage of your site. For running a site-wide test using a URL pattern, you can specify the landing page URL as the home page URL in a segment condition to collect data of visitors who first land on the home page.

  NOTE: This URL must be part of the Campaign URL pattern.
• Referring URL: Referral traffic comprises the visitors who land on the test page through referral websites, and in this case, document.referrer has a value. In the context of an A/B test, this is the previous page URL.  

• Search Keywords: Select this option for visitors who use certain search keywords to land on the test page. The Search Keywords condition applies to both organic and paid search traffic from search engines.

  Note: Segmentation does not work for the search engines that are on HTTPS because the search engines on HTTPS encrypt the search keywords.
• Traffic Source: Use this option to segment the report based on the source that the visitor has come from. The following traffic source options are available in Wingify: 
  • Direct: This option refers to the traffic that directly lands on the test page and when document.referrer in visitor information is empty. 
  • Email: This type contains utm_medium=email as the query parameter. 
  • Referral: This option refers to the paid ad traffic when document.referrer in visitor information has a value. It contains utm_medium query parameters such as cpc, ppc, cpa, cpm, cpv, or cpp.
  • Social: It comprises the visitors who come from social media platforms like Facebook, Quora, Reddit, Imgur, Disqus, 9gag, Tumblr, Google Plus, Stumbleupon, Twitter, Linkedin, Technorati, Digg, Hootsuite, Myspace, Tinyurl, Youtube, Flickr, Pinterest, and so on. 
  • Non-paid Search Traffic: This option refers to the unpaid ad traffic when document.referrer in visitor information has a value. It includes organic traffic from a search medium but does not contain utm_medium query parameters such as cpc, ppc, cap, cpm, cpv, or cop. 
  • Paid Search Traffic: This option refers to the paid traffic. It refers to users who enter your website through paid Internet advertising. Google AdWords is the most used paid advertising network. 

  • Query Parameter: Select this option if segments are based on the value of the query parameter in the URL (used for test variables). For example, http://example.com?_utm_campaign=brandNew. The query parameter in the example is _utm_campaign, and the value is brandNew.

    Note: By default, Wingify considers all query parameters.
• UTM Parameter: Select this option if you want to segment visitors based on specific UTM parameters. These parameters are used to track the visitors who arrive at your website from a given paid advertisement campaign. The following options are available for defining the UTM parameter: 
  • Campaign - This is to specify the ad campaign name from which the visitor has arrived on the campaign URL. E.g.: utm_campaign=email_adCampaign. 
  • Content - This is to specify the type of content that shares a common source from which the visitor has arrived on the campaign URL. E.g.: utm_content=footerlink. 
  • Medium - This is to specify the channel from which the visitor has arrived on the campaign URL. This may include email, social media, etc. E.g.: utm_medium=email. 
  • Source - This is to specify the website from which the visitor has arrived on the campaign URL. This could be any social media (such as Facebook and Youtube) or any blogging platform. E.g.: utm_source=twitter. 
  • Term - This is to specify any keyword that you have used for the advertisement, such as in Google Ads.

• Session Landing Page URL: Select this option to target visitors based on the specific URL they landed on at the start of their session. This is useful for multi-page tests to include visitors who enter your site via a particular URL. The specified URL should follow the campaign URL pattern.

  Note: The Session Landing Page URL option is available only in accounts created on/after June 14, 2026.

Behavior

Adding in-session behavior to activate a segment allows you to define visitor action on the website for which the targeting conditions are evaluated. For example, you can add the targeting condition as “visitors landing on your website through Facebook + US Region + iOS users + Click Buy Now CTA button”. Here, the visitor is included in the segment only after the visitor clicks the Buy Now button.

After the click event, Wingify checks all the target conditions and includes or excludes visitors into segments accordingly. Please note that behavior targeting options are not available for split URL test and form analysis.

When you select Behavior as a target condition, the elements on which changes have been applied in the test are not hidden. If an element is visible to the visitor, they can see a flicker effect. It is advisable to take this into consideration while using behavior. To change this option, click Configure the Segment Settings in Wingify.

• Number of Pages in a Session: Displays the changes when visitors navigate through the set number of pages on the website during a session. For example, if you define this option to be equal to 3, changes appear whenever visitors traverse through three pages during a session.

  Info: The page count will get incremented only when a visitor navigates through a given page, on which Wingify settings are available. If the visitor traverses through a webpage, where no campaign is running, then the page count will not get incremented. 
  Note: This option is available only for Pro and Enterprise plans.

• Mousedown: Use this to segment visitors who mousedown (press the mouse button down) on a specific element of the page, defined by CSS selector. Mousedown triggers as soon as the (left) mouse button is pressed, before it's released. This is useful for testing interactions like drag-start, sliders, or press-and-hold elements. For example, specify .add-to-cart-btn as the CSS selector to segment visitors who press down on the Add to Cart button.
  This differs from Click on Element, which fires only on a full click (mousedown + mouseup).

  Note: The Mousedown option is available only in accounts created on/after June 14, 2026.

• Click on Element: Displays the changes when visitors click a predefined element on a page. That is, when the mouse button is both pressed and released (mousedown + mouseup) on that element. If the element happens to be a hyperlink that redirects to another page, make sure that the redirected-to page is also a part of the test. You can use this option when trying to test items that appear on the page after any user action. 

  Note: For interactions that should trigger as soon as the mouse button is pressed (without waiting for release) use Mousedown instead.
• Time Spent on Page: Selecting this option triggers the changes when a visitor spends “x” seconds on a single page. For example, if you have defined the time for the trigger as 10 seconds, the changes initialize when the visitor spends 10 seconds or more on a page. 
• User Is Trying to Close the Page: Displays the segment changes when visitors attempt to close the test page. So when the cursor moves outside the browser viewport, Wingify executes this trigger. You can use this option if you are trying different designs/content on the exit-intent popup on your website. 
• Page Scroll Is More Than: Displays the changes when a visitor has scrolled the page for more than the defined percentage or pixels in this section. This option is helpful if you are trying to test changes on elements that are placed at the bottom of the page or only want to include the visitors that scroll to a certain section of the page. 
• Custom Trigger: Displays the changes when the executeTrigger() function is executed. Users can add their own custom code, and then call the executeTrigger() function. This way, the custom trigger condition is fulfilled and the campaign is displayed. For example, When a visitor hovers over a section of the webpage / When a certain element is available on the webpage / After a visitor performs some action that closes a pop-up that appears on page load, etc.

Technology

• Operating System: Create segments based on the operating systems used by visitors. The example includes segmenting only for Mac OS users. 
• Browser: Create segments based on the browsers used by visitors to access the test page. 
• User Agent: Assign User Agent (UA) as a string to identify the browser or device used by a visitor to access the test page. 

• Device Type: Create segments based on the devices used by visitors to access the test page like Desktop, mobile phones, and tablets.

  Note: Wingify uses an open-source UA-parser library to detect visitor devices. The parser library categorizes the devices based on their types, and the library is regularly updated for new devices. The same library is used in the segmentation feature to target visitors based on their operating systems. You can access the source code here, and then use this regex to locate the code.
• Screen Resolution: [For Reports Segmentation only] Segment reports based on the screen resolution used by the visitors to access your website. Example: 1280 x 768. 
• Document Encoding: [For Reports Segmentation only] Filter visitor data based on the character encoding technology used by the visitor’s system. Examples include US-ASCII, UTF-8, and so on. 
• Screen Width: Pre-segment your visitors based on the width of the screen on which the visitors load your campaign URL. For example, you can use this option to launch a test when the screen width is less than 600 pixels. 
• Screen Height: Pre-segment your visitors based on the height of the screen on which the visitors load your website. For example, you can use this option to launch a test when the screen height is at least 1920 pixels.

Time

• Day of Week: Run your test for visitors who access your test page on specific days. 
• Hour of the Day: Run your test for visitors who access your test page within specific hours. Wingify considers the visitor’s local time zone and runs the test accordingly. If you set Hour of the Day is equal to 10, the test will run from 10:00–10:59 a.m.
• Minute of the Hour: Use this to segment visitors who arrive on your test page during specific minutes of an hour (00–59). In addition to selecting the minute, you must define the timezone Wingify should use to evaluate this condition:
  • Visitor Level: Considers each visitor's own local time zone.
  • Account Level: Considers the time zone configured at the account level, regardless of the visitor's location.
    
    For example, set Minute of the Hour is equal to 15 with timezone set to Visitor Level to segment visitors who land on your page between the 15th and 16th minute of any hour, based on their local time.
• Average Time Spent per Page in a Session: Use this to segment visitors based on the average time (in seconds) they spend on a page during their current session. Define the condition using Is greater than or Is less than operators, followed by the number of seconds.
  
  For example, set Average Time Spent per Page in a Session is greater than 30 to segment visitors who spend an average of more than 30 seconds per page in their session.

• Time spent in a Session: Use this to segment visitors based on the total time (in seconds) they spend on your website during their current session. Define the condition using Is greater than or Is less than operators, followed by the number of seconds. 
  
  For example, set Time Spent in a Session is greater than 120 to segment visitors who have spent more than 2 minutes on your website in their current session. 

  Note: The Minute of the Hour, Average Time Spent per Page in a Session, and Time spent in a Session options are available only in accounts created on/after June 14, 2026.

Visitors

• Visitor Type: Select this option to create different segments for returning visitors and new visitors. Wingify places a tracking cookie to determine if a visitor is new or returning.

• New vs. Returning Visitor: A new visitor is one who visits your website for the very first time. This means if it is the visitor’s first session on your website, he/she is considered a new visitor. If the same visitor visits your website from the same browser in another session, he/she is considered a returning visitor.

  Note: In Wingify, a new session is created on browser restart after 30 minutes of inactivity or continuous activity of no more than 24 hours. Post this; a visitor is considered a returning visitor.
• Location: Create segments based on visitor geography. The location of visitors is identified by using Maxmind to track their IP addresses. 
• Visitor Language: [For Reports Segmentation only] Filter visitor data based on the language used by the visitors in their browser settings. 
• Visitor ID: [For Reports Segmentation only] Filter visitor data based on their unique ID.
• Days Since last Visit: Use this to segment visitors based on the number of days elapsed since their previous visit. Define the condition using Is equal to, Is not equal to, Is greater than, or Is less than operators, followed by the number of days.
  
  For example, set Days Since Last Visit is greater than 7 to segment visitors who last visited your site more than a week ago.
• Adblocker: Use this to segment visitors who have an ad blocker installed on their browser. Define the condition using exists (visitor has an ad blocker) or does not exist (visitor does not have an ad blocker).
• Same-day visit: Use this to segment visitors who visit again within 24 hours of their last visit. Define the condition using happen (visitor returned within 24 hours) or does not happen.
• Days Since First Session: Use this to segment visitors by the number of days since their first session. Define the condition using Is equal to, Is greater than, or Is less than, followed by the number of days.
  
  For example, set Days Since First Session is greater than 30 to segment visitors whose first session on your site was more than 30 days ago.
• Number of Sessions of the Visitor: Use this to segment visitors based on the total number of sessions created in Wingify for that visitor on your website in the past. Define the condition using Is equal to, Is greater than, or Is less than, followed by the number of sessions.
  
  For example, set Number of Sessions of the Visitor is greater than 3 to segment visitors who have had more than 3 sessions on your website to date. 
• Temperature: Use this to segment visitors based on the temperature set in their location. Define the condition using Is equal to, Is not equal to, Is greater than, or Is less than, followed by the temperature value in Fahrenheit.

• Weather: Use this to segment visitors based on the weather in their current physical location. Select one or more weather conditions from the list that includes options such as Clear, Clouds, Drizzle, Dust, Fog, Mist, Rain, Smoke, Snow, Thunderstorm.
  
  For example, select Clear to segment visitors experiencing clear weather at the time of their visit. 

  Note: The Days Since last Visit, Adblocker, Same-day visit, Days Since First Session, Number of Sessions of the Visitor, Temperature, and Weather options are available only in accounts created on/after June 14, 2026.

Account-Based Marketing

These options allow you to target high-value B2B audiences using firmographic and contact-level data managed in Wingify Data Studio. You can leverage firmographic data (company details) and contact-level data (individual attributes) imported from your CRM or uploaded via CSV to create precise campaign segments.

You can target accounts or contacts in two primary ways:

Properties: Filter visitors based on specific attributes available in their data profile, such as Industry, Revenue, Job Title, or Lifecycle Stage. For example, you can target visitors where the Account Industry is Banking to show them a relevant financial services case study. Or, you can target visitors where the Contact Job Title attribute contains Director, VP, or CXO to offer them a special executive demo.

Lists: Target pre-defined groups of visitors by selecting saved lists (Static or Dynamic) that you have created and managed within Data Studio. For example, you can target a saved list named Churn Risk Accounts (synced from your CRM) with a special discount or retention message.

Scenario 1: Data picked from an integrated CRM (for example, Salesforce or HubSpot)

If a visitor belongs to a company record in your CRM, Wingify Data Studio automatically ingests the associated account and contact attributes during the scheduled sync. For example, your CRM stores the Account Industry as Healthcare, Employee Count as 1,200, and Annual Revenue as $50M. It also stores Contact Job Title as Director of Product and Lifecycle Stage as Opportunity. When this visitor lands on your website, Wingify resolves them to the corresponding CRM record and makes these attributes available for targeting in your custom segment builder.

Scenario 2: Data picked from a third-party enrichment tool (for example, 6sense or Clearbit)

If a visitor is identified using a company/visitor intelligence tool, Wingify Data Studio captures the enriched firmographic details provided by that tool. For example, Clearbit identifies the visitor’s company as Acme Corp and provides enriched firmographic details such as Industry = SaaS, Employee Count = 250–500, and Technologies Used = Segment, Marketo, Snowflake. These attributes are synced into Data Studio and become available as segmentation conditions, even if the visitor does not exist in your CRM.

Others

• Cookie value: Create segments based on whether or not a user has a cookie from your website. Select this condition and then type the cookie value. Wingify determines if a user qualifies for the test based on the cookie value you have set. Please note that this condition works only if the cookie is accessible using JavaScript. Wingify can read server-side cookies, too, provided they are not restricted to be read by JS. 

• JavaScript Variable: Create your own custom Javascript condition to define a visitor segment. The test runs only if a user passes through the JavaScript condition while loading the pages.

  Tip: When you define targeting criteria with a JavaScript variable or a cookie value, Wingify by default, uses the DOM Ready polling setting to check segment conditions for the specified variable or cookie. If you wish to modify the polling criteria in Wingify, refer to Configuring the Segment Settings in Wingify.

• IP Address: This option allows you to target visitors based on their IP addresses. IP address targeting supports both IPv4 and IPv6 addresses and is available across AB, Split, Multivariate, Rollout, Personalize, Pulse, and Insights campaigns.

  Use the following operators to define this condition:

  • Is equal to: Includes visitors whose IP address matches the defined value.
  • Is not equal to: Includes visitors whose IP address does not match the defined value.
  • Matches Regex (case insens.): Includes visitors whose IP address matches the defined regular expression.
  • Contains: Includes visitors whose IP address contains the defined value.
  • Does not contain: Includes visitors whose IP address does not contain the defined value.
  • Range: Includes visitors whose IP address falls within a defined range (for example, 124.1.124.250 to 124.1.124.255).
  • In list: Includes visitors whose IP address matches a value in a selected attributes list.
  • Not in list: Excludes visitors whose IP address matches a value in a selected attributes list. 
• Test Campaign Served: This option allows you to pre-segment your campaign based on the visitors who were either served a campaign earlier or never. You can choose from the following options to configure this filter: 
  • Any - Allows you to filter the visitors who were part of any of your current and previous campaigns. 
  • None - Allows you to filter the visitors who weren’t part of any of your Wingify campaigns. 
  • Is equal to - Allows you to filter the visitors that were part of a given campaign that is currently either running or paused. 
  • Test Metric: This option allows you to pre-segment your campaign based on the visitors who have either got converted or not for a certain metric that you have already used in your test campaigns. To apply this, you need to specify the conversion status, campaign, and the corresponding metric.
• Browser Language: Use this to segment visitors based on the primary language set in their browser. Define the condition using Is equal to, Is not equal to, In list, or Not in list, followed by one or more languages selected from the list, for example, Bulgarian, Chinese, Croatian, and so on.
  
  For example, set Browser Language In list and select Chinese, Japanese to segment visitors whose browser language is set to either Chinese or Japanese.
• Survey Campaign Served: Use this segment to segment users based on the Wingify survey campaigns they are a part of. Configure this condition as follows:
  • Survey: Select the operator (Is equal to, Is not equal to, or Any), followed by the specific survey.
  • any time: Define the time window in which the survey should have been served, using one of the following:
    • in current session
    • in the last (Enter number of days. For example, set this to 3 to segment visitors who were served the survey in the last 3 days.)
    • in last session, or 
    • between (Enter a start day and an end day to define a range. For example, set this to between 3 and 7 to segment visitors who were served the survey between 3 and 7 days ago.)
• EmotionsAI Segment: Use this to segment visitors based on the visitor need identified by EmotionsAI (an AI model that classifies visitors into one of 10 psychological need categories based on how they interact with your website). These needs fall into two groups:
  • Intuitive Needs: Attention, Comfort, Community, Competition, Safety

  • Rational Needs: Change, Immediacy, Notoriety, Quality, Understanding
    
    Select one or more of these categories to segment visitors accordingly. For example, select Safety to segment visitors whose on-site behavior indicates a preference for trust signals like security badges, guarantees, or clear return policies.

    Info: EmotionsAI provides audience segmentation built by training an algorithm to identify links between user behaviors and the types of online experiences they prefer. The AI has identified 10 visitor groups with very different UX preferences and can predict them based on observed visitor behaviors. As a result, online experiences can be tailored to visitors' preferences, enabling websites to demonstrate emotional intelligence.
    Note: The Browser Language, Survey Campaign Served, and EmotionsAI Segment options are available only in accounts created on/after June 14, 2026.

Integrations

The following attributes can be availed when you have enabled the respective integrations from the main menu > Configurations > Integrations:

• Albacross Data: You can use Albacross data as a targeting condition in Wingify. For more information, see Integrating Wingify with Albacross. 
• Amplitude Cohorts: Create targeted experiences for specific user segments identified in Amplitude. For more information, see Importing Amplitude Cohorts to Target Wingify Campaigns. 
• BigQuery: Integrating your Wingify account with BigQuery (BQ) allows you to leverage data stored in your BigQuery tables for pre-segmentation targeting in Wingify campaigns. By importing specific lists of user identifiers (like UUIDs, etc.) from BigQuery into Wingify, you can precisely target your Wingify Testing or Personalization campaigns to visitors whose identifiers are present in those lists. Integrate Wingify with BigQuery for Targeting Campaigns.
• 6sense Attribute: Avail the ability to target your visitors using 6sense attributes via the Wingify <> 6sense integration. To do so, perform the steps mentioned here.  
• 6sense Segment: When your Wingify account is integrated with 6sense, you can target your visitors using the segments that you have imported from your 6sense account. This requires configuring the Wingify <> 6sense integration with the 6sense API key. Click here to learn how to do these. 
• Clearbit Company Attributes: By integrating your Wingify account with Clearbit, you can effectively leverage Clearbit’s company attributes to target your visitors. Click here to learn how to do it. 
• Demandbase Attribute: By integrating your Wingify account with Demandbase, you can target your visitors using Demandbase attributes. Click here to learn how to use this attribute for targeting your visitors. 
• GA4 Audience List: Integrate your Wingify account with GA4 to target your visitors using the audiences that you have imported from your GA4 account. Click here to learn more. 
• GTM Data Layer: If you have integrated your Wingify account with Google Tag Manager (GTM), you can utilize the data layer variables and events created in GTM to create segments for targeting your visitors. Learn how to harness this feature by following the steps mentioned here.
• Heap: Integrating Wingify with Heap lets you import the segment data from your Heap account to target visitors for your Wingify campaigns. For more information, see Enable Use of Heap Segment for Visitor Targeting. 
• HubSpot Visitor Lists: You can import visitor data from HubSpot for visitor targeting in your Wingify campaign. For more information, see Target Your Wingify Campaign Using HubSpot Visitor Lists.
• Lytics Audience: You can target the visitors in your Wingify campaigns using the audiences that you have imported from Lytics. Learn more about it here. 
• Marketo Smart List: Marketo’s smart lists can be imported into Wingify if you have enabled the Wingify <> Marketo integration. Learn more from the steps mentioned here. 
• Mixpanel: You can import Mixpanel cohorts into Wingify and use them for targeting visitors in your Wingify campaigns. For more information, see Enable Use of Mixpanel Audience for Visitor Targeting. 
• Quin Audiences: Once you've enabled and configured the Quin integration, you can start targeting Quin audiences in your Wingify campaigns. For more information, see Integrating Wingify with Quin. 
• Salesforce Object List: The Wingify-Salesforce integration enables you to import Salesforce object lists into your Wingify account and segment visitors based on valuable customer data, leading to more relevant and effective campaigns. For more information, see Using Salesforce Object List to Target Your Wingify Campaigns. 
• Segment Audience: When your Wingify account is connected with Segment, you can employ your Segment audience to establish targeting criteria in Wingify. Explore the instructions here to understand how to execute this. 
• Tealium Audience: Integrating Wingify with Tealium enables you to use the audiences imported from your Tealium account for visitor targeting. Follow the steps mentioned here to use this attribute for creating a targeting condition. 
• Tealium Badge: If you have your Wingify account integrated with Tealium, you can utilize your Tealium badges to set up targeting conditions in Wingify. Click here to learn how to perform it. 
• Triblio Attribute: If you have integrated your Wingify account with Triblio, you can use Triblio attributes to target your visitors in Wingify. Click here for more information. 
• ZoomInfo Attributes: Integrating Wingify with ZoomInfo enables you to utilize the company attributes provided by ZoomInfo to deliver personalized content. For more information, see Integrating Wingify with ZoomInfo.

Condition Match Type for the Segment

To define an attribute or an event, you need to specify the match criteria to relate the attribute to the value you would like to specify. Refer to the example highlighted in the following image.

To create a complex visitor segment, you can add multiple conditions using Add another condition, group them using brackets, and merge the groups with and and or operators to define your segmentation criteria. To use the brackets, simply click on the bracket at the start and the end of a condition group that you want to create.