Visited URL

The filter is part of the Sessions Dashboard and can be saved as a segment.

Definition

“Visited URL” is a new segment filter that allows you to search for users by a specific URL. The event filter helps you to:

1. Build a more precise Segment for your user experience analysis
2. Save time watching irrelevant Sessions

---

Configuration

The filter can be configured with any of the fourth supported options: 'matching', 'contains', 'starts with', 'ends with'

To illustrate each option we will use the following URLs. Assume that each of the below-mentioned URLs has been visited at least by one user.

https://www.example.com/nuts/blog/structure-urls.html?q=s&q2=a+b;q3=sp%0Ace#top
https://www.example.com/bolts/blog/structure-urls.html?q=s&q2=a+b;q3=sp%0Ace#top
https://www.example.com/cakes/blog/strucutre-urls.html?q=s&q2=a+b;q3=sp%0Ace#top
https://www.testblog.com

---

Option 'Contains'

If you use the option ‘contains’ and define a value: blog, all users who have visited any of the four URLs will be listed.

Since each URL has been visited at least once, then in the results you will see users who have visited any of the listed URLs:
https://www.example.com/nuts/blog/structure-urls.html?q=s&q2=a+b;q3=sp%0Ace#top
https://www.example.com/bolts/blog/structure-urls.html?q=s&q2=a+b;q3=sp%0Ace#top
https://www.example.com/cakes/blog/structure-urls.html?q=s&q2=a+b;q3=sp%0Ace#top
https://www.testblog.com

---

Option 'Starts with'

If you select the option ‘starts with’ and define a value: www.example.com, then the result will include users who have visited any of the three next URLs:
https://www.example.com/nuts/blog/structure-urls.html?q=s&q2=a+b;q3=sp%0Ace#top
https://www.example.com/bolts/blog/structure-urls.html?q=s&q2=a+b;q3=sp%0Ace#top
https://www.example.com/cakes/blog/structure-urls.html?q=s&q2=a+b;q3=sp%0Ace#top

---

Option 'End with'

If you select the option ‘ends with’ and define a value: blog.com, then the result will be all users who have visited at least once the https://www.testblog.com.

---

Option 'matching'

Brief Overview of URL Structure

Before illustrating how to use the option ‘matching’, we will go briefly through the URL structure. Let’s take a look at the first URL:
https://www.example.com/nuts/blog/structure-urls.html?q=s&q2=a+b;q3=sp%0Ace#top

1. HTTPS stands for the protocol to be used between your website and your user’s browser

2. www stands for the subdomain. Can be omitted, and can be used in another subdomain instead.

3. Example.com stands for the domain which identifies the website.

4. .com - top-level domain (TLD). It comes after the name of your website. There are variations of this TLD:
   .com - top-level domain (TLD). It comes after the name of your website. There are variations of this TLD:

   1. .com
   2. .org
   3. .ai
   4. .edu
   5. .gov
   6. Or using country-code top-level domains such as .de (for Germany), .ca (for Canada), etc.

5. /nuts & /blog are subfolders. Subfolders are used to separate website content into logical sections.

6. Structure-URLs stands for the slug. It helps users to understand which page they are on. The example above defines that the users are on the page which describes the structure of the URLs.

7. After the symbol ‘?’ come all the URL parameters (also called query parameters)

---

Using option 'matching'

Going back to our ‘matching’ option, if you want to find the subset of users who have visited URLs containing the subfolder ‘blog’, you need to define: /blog.

In this case, you will see on the list of users who visited:
https://www.example.com/nuts/blog/structure-urls.html?q=s&q2=a+b;q3=sp%0Ace#top
https://www.example.com/bolts/blog/structure-urls.html?q=s&q2=a+b;q3=sp%0Ace#top
https://www.example.com/cakes/blog/structure-urls.html?q=s&q2=a+b;q3=sp%0Ace#top

If you want to find the subset of users who have visited URLs containing the subfolder ‘nuts’, you need to define: /nuts.

In this case, you will see on the list of users who visited:
https://www.example.com/nuts/blog/structure-urls.html?q=s&q2=a+b;q3=sp%0Ace#top

If you want to find the subset of users who have visited URLs containing specific parameters q and q2, then define the value for the ‘matching’ option as follows (NB: Parameters should be included with values if any of the query parameters is missing value, will be not executed search)
/structure-urls.html?q=s&q2=a+b

📘

Do take note! Both of our main dashboards, Segments, and Funnel, support the use of the event filter "Visited URL."