Segmentation Conditions Reference
How to read this reference
Most parameters below support the same set of conditions - Is, Contains, Starts with, Ends with, and RegEx for text values, or Is, Lower than, Greater than for numeric values. Rather than repeat all conditions for every parameter, each entry below gives one representative example; assume the same condition options apply unless noted otherwise.
Some parameters listed here only work for logged-in / identified users, or require additional integration on your website - these are flagged individually.
Traffic Source
Referrer type - segments by traffic type: Direct (typed URL directly), Paid (ads like Google/Facebook Ads), Organic (search engine), or Referral (recommendation link).
Referrer URL - segments by the page a visitor was on before arriving at yours.
Example: Include → Referrer URL → Starts with → https://www.google.com
Geolocation
Country - segments by visitor country. Type the first 3 letters and select from the list shown.
Region - segments by region (including US states). Same lookup method as Country.
City - segments by city. Same lookup method as Country.
Visitors from EU - segments visitors accessing your site from an EU member country.
Conversions
Count goal conversions - segments by how many times a visitor completed a specific goal.
Example: Include → Count goal conversions → [GoalName] → Greater than → 10 (visitors who converted more than 10 times)
Days since last conversion - segments by how many days since a visitor last converted on a specific goal.
Example: Include → Days since last conversion → [GoalName] → Lower than → 2
Average revenue - segments by the average revenue a visitor has generated. Works with Sale or any custom goal that reports a value.
Example: Include → Average revenue → Sale → Greater than → 245
Total revenue - segments by the total revenue a visitor has generated. Works with Sale or any custom goal that reports a value.
Example: Include → Total revenue → Sale → Is → 300
Behavior
Returning visitor - visitors who've been to your site before at least once. Only counts visits since the tracking code was installed - a visit before installation doesn't count as a prior visit.
New visitor - the inverse: visitors on their first visit since the tracking code was installed.
Days since first visit - segments by days since a visitor's first tracked visit.
Example: Include → Days since first visit → Greater than → 2
Days since previous visit - segments by days since a visitor's last (not first) visit.
Example: Include → Days since previous visit → Lower than → 10
Count visits - segments by total number of visits.
Example: Include → Count visits → Greater than → 2
Count pageviews in current session - segments by how many pages a visitor has viewed in their current session.
Example: Include → Count pageviews in current session → Greater than → 2 (applies from the 3rd page onward)
URL visited in current session - segments by whether a visitor viewed a specific URL during their current session.
Example: Include → URL visited in current session → Contains → case-studies
Time on site in current session - segments by seconds spent in the current session.
Example: Include → Time on site in current session → Greater than → 10
Landing page in current session - segments by the first page a visitor landed on this session.
Example: Include → Landing page in current session → Is → https://www.example.com/case-studies
Viewed variation - segments by whether a visitor saw a specific Variation from a past or active A/B test. Select the experiment, then the specific Variation. Use AND to require multiple Variations, or Exclude the Variation to target visitors who saw the Control instead.
Online visitors on the current page - segments by how many people are currently on the same page in real time.
Example: Include → Online visitors on the current page → Greater than → 3
UTM Parameters
All five support Is / Contains / Starts with / Ends with / RegEx, matched against the campaign URL's UTM tags.
-
utm_source - the traffic source (e.g.
Google Adwords, a newsletter name). -
utm_medium - the marketing medium (e.g.
banner,CPC,email). -
utm_term - the paid keyword being targeted (e.g.
seo_services). -
utm_content - the specific ad element clicked, useful for A/B testing ad creative (e.g.
video_advstext_ad). -
utm_campaign - the overall campaign name (e.g.
K00z_launch).
Example: Include → utm_source → Contains → Google
Custom
Cookies - segments by a cookie value you've set for the visitor. Value can be numeric or text.
Example: Include → Cookie → [cookie name] → Is → 1254
Custom attribute - segments by data pushed from your own database via Customer Attributes.
Example: Include → Custom attribute → [attribute name] → Greater than → 19
onPage Variable - segments by an On-Page Variable you've defined.
Example: Include → onPage Variable → [variable name] → Greater than → 200
GTM dataLayer variable - segments by a variable pushed via Google Tag Manager's dataLayer.
Example: Include → GTM dataLayer variable → [variable name] → Is → 20
The dataLayer must be populated with the values you need for segmentation before the Explore tracking code loads.
GTM dataLayer event - segments by whether a specific event was pushed to the dataLayer.
Example: Include → GTM dataLayer event → Is → new_subscriber
Technology
IP address - segments by visitor IP.
Example: Include → IP address → Starts with → 19.
Device type - Desktop, Phone, or Tablet.
Operating system - Windows, macOS, Linux, iOS, or Android.
Browser name - Chrome, Firefox, Opera, Safari, Internet Explorer, or Edge.
Browser version - segments by browser version number.
Example: Include → Browser version → Greater than → 11.5
Browser language - segments by the browser's configured language.
Page Loaded In Iframe - segments by whether your site was loaded inside an iframe. Useful when your content is embedded elsewhere.
Screen width / Screen height - segments by device screen dimensions in pixels.
Example: Include → Screen width → Greater than → 600
JavaScript variable - segments by the value of a JS variable defined in your site's source code.
Example: Include → JavaScript variable → [variable name] → Greater than → 200
JavaScript variables must return a string or number. If your variable returns a boolean, append .toString() to it.
JavaScript callback - segments visitors using fully custom JavaScript logic. Define an evalSegment function that returns true or false to determine whether the segment matches. Press Edit callback code to write it.
See Build Custom JavaScript Segments for real examples.
Internet Service Provider - segments by ISP.
Example: Include → Internet Service Provider → Starts with → VODA
You can narrow ISP results by adding the 2-letter country prefix (e.g. US: AT&T).
Previous Surveys
Segments visitors by how they answered a specific question in a Survey that is or was active. Select the Survey, then the question, then match the answer using Is / Contains / Starts with / Ends with / RegEx.
External Data
Woopra Label - segments based on a visitor's Woopra label, if Woopra is installed alongside the Explore tracking code. The match is case-sensitive.