Last Updated 6/4/2018.

Filters, attributes, activities, oh my! There are a lot of new options and configurations when building segments, and they can be a little confusing. Below, we'll review how to use the most common filter options correctly when building segments to ensure you create exactly the kind of segment you want to build.

Using Filters and Predicates Correctly

When creating a Segment, there are a few default options, including whether to use an Activity or an Attribute, which Activity or Attribute you are filtering by, and how to compare it (also called a predicate). The first two options are pretty simple; you can either choose to filter by an Activity or Attribute. Be sure to review the Glossary of Attributes and Activities article to see all of the available options. But the second half of building the segment is where it gets a little tricky.

For this example, let's start with something simple. We're going to track the Activity when someone lands on a particular URL. 

Building a Single/Exact Page URL Segment using 'Equals'

  1. Navigate to the 'Explore' section in the left side panel of Feathr.
  2. Click '+Change Filters' on the right side of the page to bring up the segment editor.
  3. Select 'Filter on Audience Activity'.
  4.  The activity will be 'URL'. In the next section (the comparison), select 'Equals'.
  5. Then, you'll paste the exact URL you want to track. So, to track Feathr's homepage, I would use 'https://feathr.co/'.

Using the 'Equals' option is pretty straightforward -- the segment will only pull in those who landed exactly on the selected page. That segment looks like this: 

Note: For more information on how to use the lookback window when creating a segment, check out our article How to Create New Segments.

Great, but how do I track when someone lands on any page of my website? While most people typically start on the home page and click around to other pages, it's possible that other visitors are going directly to a specific link (perhaps they received it in an email) without going to the homepage first. In that case, they wouldn't be added to this particular segment. 

To build a segment that captures all the pages of your website, we'll use the 'Starts With' comparison. 

Building a Full Site URL Segment Using 'Starts With'

  1. Navigate to the 'Explore' section in the left side panel of Feathr.
  2. Click '+Change Filters' on the right side of the page to bring up the segment editor.
  3. Select 'Filter by Audience Activity', then URL. In the next section (the comparison), select 'Starts With'
  4. Next, place your homepage URL. It may end with a forward slash. 
  5. Click 'Ok' to save the filter. 
  6. Select '+Create a Segment', name the Segment, and hit 'Create'.

For example, the correct segment shown above would track someone who lands on https://feathr.co/site/products/ , https://feathr.co/views/lead-form , and https://feathr.co/  because they all begin with https://feathr.co/ .

Using 'Starts With' for Name or Email Segments

'Starts with' will make your search for Persons who match the Segment rules happen faster. 'Starts with' assumes there will be a Wildcard at the end of the field, so there is no need to include one. Let's use Name in this example:

  1. Navigate to the 'Explore' section in the left side panel of Feathr.
  2. Click '+Change Filters' on the right side of the page to bring up the segment editor.
  3. Select 'Filter on Audience Attribute', 'Name', and 'Starts with'. Here, I typed "dia" so I could find my First Name. 

   4. Click 'Ok' to build the segment. The results will pull in anyone whose name starts with "dia". 

*Note: When using Name and 'Starts with', the results will pull in both first and/or last name, if the conditions are met.

  1. For example, click '+Change Filters' on the right side of the page to bring up the segment editor.
  2. Select 'Filter Audience by Attribute', 'Name', and 'Starts with'. Here, I typed "tw" to search for my Last Name, and again, my Person appeared because it met the conditions of the filter.

Using a Wildcard in Conversion Segments

Wildcards (*) are often commonly used in conversion segments when each registrant is given a unique ID while completing registration. In this case, each registration might have a unique section of the URL, but it would otherwise be the same. 

For example, your confirmation URL from your reg vendor may look like this:

https://www.reg-vendor.com/showname/registrant/4487365/confirmed/

The string of numbers before the "confirmed" part of the URL are the unique ID given to each registrant. However, we can't predict every single unique ID and include them in our Conversion Segment, so that's when we'll use a Wildcard. Our Conversion Segment would look like this:

https://www.reg-vendor.com/showname/registrant/*/confirmed/ 

Using the Wildcard here will include any unique ID that's used to identify each registration.

Quick Recap: 

  1. When using "Equals," you cannot use a Wildcard (*).
  2. When using "Starts With," you cannot use a Wildcard (*), because it's already assumed by the segment filter. 
  3. "Starts with" will pull in results that match any part of the field (i.e. First Name and/or Last Name, if either one meet the conditions). 

Check with your Customer Success Manager or sign up for our newsletter to be notified of any segment updates! 

Common Questions

Should I use a wildcard for capturing HTTP vs HTTPS?
Great question! You can use a wildcard to allow both HTTP and HTTPS, and that would look something like:

 Activity > URL > Contains> http*://feathr.co/*  

However, we don't necessarily recommend doing that, as it can slow down the time it takes for your Segment to populate. There's an article you can read about here, which gives you more insight.

Related Articles

When to Use Update vs. Sprinkle Functions
How to Use Specific Attribute Filters
Using Different URL Variations to Capture all Site Visitors

Did this answer your question?