Basic Google Analytics Filters for Every Site



In Google Analytics, Filters are used by Views to segment the data into smaller groups. Filters can be used to include only specific subsets of traffic, exclude unwanted data, or to search and replace certain pieces of information.

Creating New Filters

Filters can be created at either the Account or the View level. It is a best practice to create all the filters at the Account level, then assign them to different views. You can also create a filter at the View level, which would make that filter be applied to that particular view only; however, you should never need to do so unless if you have to create a filter based on Custom Dimensions or Metrics.

To manage or edit your filters, navigate to All Filters menu. Through the All Filters menu you can manage or edit all the filters in the account. You can refer to Google Analytics documentation to learn more about creating and managing filters at different levels.

Filters in Account and View

Couple of Notes

A couple of notes before jumping into the basic filters tutorial:

Recommended Views

Unfiltered View – Always have a view called “Unfiltered View – Do Not Delete” defined to keep your raw data intact. This view is there to make sure if anything unexpected happens to the data at least you have a backup saved somewhere. You should never add any filters to this view.

Main View – This view would be the one you use for reporting on a regular basis. Call it whatever you like, but make sure it’s communicated to your team which view should be used for reporting.

Test View – Apply your filters to this “Test View” first. Since the effects of applying a filter cannot be undone, it is recommended that you apply your new filters to a Test View first and let them run for a couple of days, to have enough time to verify the credibility of the results. If you have not already created and defined a “Test View”, it is a good time to create one now; your Test View should use the same exact settings as your “Main View” that you would normally use for your reporting purposes. If everything looks good after a few days, then apply to your Main View.

Filter Processing

Filters cannot be applied to your previous historical data; they can only be applied to your data moving forward. Filters are processed in order, so make sure you arrange the filters in the correct order.

Naming Conventions for Views

If you have multiple websites, clients, companies, etc. you should use a naming convention for your views to make sure you can identify each view at a glance. This becomes handy especially when you are going through configuring your accounts, trying to figure out which views to apply a filter to.

Example: For the website, use “ – Main View”, “ – Test View” and “ – Unfiltered View – Do Not Delete”.

Basic Filters

In this blog, I am going to cover some of the basic (as opposed to more customized) filters everyone can use to segment their data. We use these filters to make sure our data is valid, to clean up the data, and to find out where the data is coming from.

Data Collection

Exclude Internal IP
Include Internal IP
Include Specific Hostname
Include Specific Subdomain
Exclude Dev Site Traffic

Data Consistency

Make your data more correct and more consistent. Use the following filters to make your data more consistent. Also, if you are suffering from having (other) in your reports, give these filters a try to consolidate more data.

Prepend Hostname to Request URI
Lowercase Hostname
Lowercase Request URI
Lowercase Search Term
Lowercase Campaign Dimensions
Remove Query String
Append Slash to Request URI
Search and Replace Filter

Data Sources

Segment your data for better analysis. The following filters would help you avoid Sampling. Since all the default reports are aggregated at the view level, it would be wise to define and use more views. If you find yourself often applying Advanced Segments, using a view/filter might be a better option for you.

Include a Traffic Medium
Include a Device Category
Include a Country

Filter Configurations

Exclude Internal IP

Use this filter to exclude yourself, i.e. your company’s internal visits, from the Main View. You may also exclude the traffic from all third party companies or agencies you work with. Multiple IP addresses can be excluded using this filter, so gather a list of all internal IPs and follow the steps below.

  • In Google Analytics interface, under Account, select All Filters.
  • Click on +ADD FILTER.
  • In the Filter Name field, enter “Exclude Internal IP”.
  • For the Filter Type, choose Custom.
  • In the Filter Field drop down menu, in the search box, type “ip”, then select IP Address.
  • IP Address Field

  • In the Filter Pattern field, use regular expression to enter all IP addresses you would like to exclude.
    • If you are excluding one or more distinct IP addresses, you should separate them by a pipe character, i.e. “|”. For example for the two addresses and you can enter 192\.168\.1\.1|255\.255\.255\.1
    • If you are excluding a range of IP addresses, use a regex pattern that covers the entire range in one statement.

regex IP

  • Select which Views you would like to apply this filter to, then add them to the Selected views list. Hold the Ctrl or Cmd button down to select multiple Views and add them all at once.
  • Click on Save to create the filter.
  • Select Views to Apply the Filter to

    Take a look at Jon’s blog for more information on filtering internal traffic and different ways to identify employees!

    Include Internal IP

    It is a good practice to define a View to only include the internal traffic. This view can be used as a way to understand how the internal teams use the website. The specific filter you need to apply to this view is similar to the one above, but this time choose the Include option as the Filter Type. Remember that you should only use one include filter for a dimension.

    • Filter Name: Include Internal IP
    • Filter Type: Custom > Include
    • Filter Field: IP Address
    • Filter Pattern: Use a regex pattern to include all your internal IP addresses
    • Select the views to apply this filter to

    Include Specific Hostname

    This is one of the best filters you can make. Hostname is the domain of the page a visitor is on when they send a hit to GA. Obviously, you should only include traffic from people visiting your site. This is going to strip out a whole bunch of ghost referral spam, or traffic that never actually hits your website via the measurement protocol.

    This filter is also especially useful when implementing cross-domain tracking. It would filter out data based on the hostname of the hits and record the data in their corresponding views.
    Example: Assume you are tracking two domains and Assume you have defined separate views for each site called “exampleUSA Only” and “exampleGlobal Only” to segregate the hits. You would now need to create the following filters:

    • Filter Name: Include Only
    • Filter Type: Custom > Include
    • Filter Field: Hostname
    • Filter Pattern: ^(www\.)?exampleUSA\.com$
    • Apply the filter to exampleUSA Only View

    Also, create a similar filter for

    • Filter Name: Include Only
    • Filter Type: Custom > Include
    • Filter Field: Hostname
    • Filter Pattern: ^(www\.)?exampleGlobal\.com$
    • Apply the filter to exampleGlobal Only View

    Include Hostname Filter

    Include Specific Subdomain

    Same as the above filter, just change the filter pattern to match the subdomain.
    Example: Assume you would like to add a filter to the “Blogs Only” View, to only include the traffic from the blogs on

    • Filter Name: Include Only
    • Filter Type: Custom > Include
    • Filter Field: Hostname
    • Filter Pattern: ^blogs\.exampleUSA\.com$
    • Apply the filter to exampleGlobal Only View

    Exclude Dev Site Traffic

    To exclude development and staging traffic data from your production view, a.k.a. Main View, create the following filter:

    • Filter Name: Exclude Dev Site Traffic
    • Filter Type: Custom > Exclude
    • Filter Field: Hostname
    • Filter Pattern: Enter a regex pattern of all development hostnames for your website. For example, if the development hostnames are,, and you would enter ^dev\.example\.com$|^backend\.example\.com$|^stage\.example\.com$ in this field (or some similar Regex).

    Exclude Dev Site Traffic

    Prepend Hostname to Request URI

    This filter is especially important if you are implementing a cross-domain tracking system. It would add the hostname to the beginning of the Request URI for every pageview hit, and then overwrite the Request URI with this new format. After applying this filter if you navigate to your Cross-Domain View, in All Pages report, you will have all pages with their corresponding hostnames.

    Example: Assume you are tracking two domains and Assume the Request URI to the homepages of both sites are index.html. After applying this filter, in your Cross-Domain View, in All Pages report you will see the following Pages:

    Hostname Homepage Address Resulting Page /index.html /index.html

    Create this filter as follows:

    • Filter Name: Prepend Hostname to Request URI
    • Filter Type: Custom > Advanced
    • Field A -> Extract A:
      • Select Hostname
      • Enter (.*)
    • Field B -> Extract B:
      • Select Request URI
      • Enter (.*)
    • Output To -> Constructor:
      • Select Request URI
      • Enter $A1$B1
    • Select Field A Required
    • Select Override Output Field
    • Apply this filter to the Cross-Domain View

    Add Hostname Filter

    Lowercase Hostname

    Your visitors might reach your website using different letter casings for the hostnames; e.g. and Create this filter to make the hostnames consistent.

    • Filter Name: Lowercase Hostname
    • Filter Type: Custom > Lowercase
    • Filter Field: Hostname

    Lowercase Hostname Filter

    Lowercase Request URI

    This filter greatly consolidates the Pages by making all URIs to be lowercase.

    • Filter Name: Lowercase Request URI
    • Filter Type: Custom > Lowercase
    • Filter Field: Request URI

    The site visitors sometimes use different letter casings for their search terms. Create this filter to enforce all these terms be recorded as lowercase.

    • Filter Name: Lowercase Search Term
    • Filter Type: Custom > Lowercase
    • Filter Field: Search Term

    Lowercase Campaign Dimensions

    Generally in a business, there are going to be various marketing campaigns initiated by different departments across an organization. In most cases, marketing teams use tools such as URL builder to generate a campaign URL. However, two campaign names which were meant to be the same can be named with different letter casings and that would make Google Analytics record the data for each campaign separately. To make your campaign names consistent, create the following filter:

    • Filter Name: Lowercase Campaign Name
    • Filter Type: Custom > Lowercase
    • Filter Field: Campaign Name

    Lowercase Campaign Name

    Just like lowercasing campaign names, it’s a good idea to make all campaign dimensions lowercase and consistent. Check with your marketing department before doing so! The following dimensions can be lowercase:

    • Campaign Source
    • Campaign Medium
    • Campaign Term
    • Campaign Content

    Remove Query String

    Sometimes, you may want a view that removes all query strings from your page URLs. You can accomplish this with an advanced filter.

    • Filter Name: Remove Query String
    • Filter Type: Custom > Advanced
    • Field A -> Extract A:
      • Select Request URI
      • Enter ^([^?]+)
    • Output To -> Constructor:
      • Select Request URI
      • Enter $A1
    • Select Field A Required
    • Select Override Output Field

    Remove Query String Filter

    Further Read: There are also other techniques for removing individual or all query strings from URLs. More detailed and advanced instruction can be found below:

    Append Slash to Request URI

    When visitors can access a page with or without using a trailing slash, Google Analytics would record a separate pageview for each case. If you see separate rows in your All Pages report for the same page paths with or without the trailing slash, you may want to create this filter.

    Note that this filter should be the last filter in the view as to not interfere with the other configurations.

    • Filter Name: Append Slash to Request URI
    • Filter Type: Custom > Advanced
    • Field A -> Extract A:
      • Select Request URI
      • Enter ^(/[a-zA-Z0-9/_\-]*[^/])$
    • Output To -> Constructor:
      • Select Request URI
      • Enter $A1/
    • Select Field A Required
    • Select Override Output Field

    Add Trailing Slash to URL

    Use this filter to look for information and modify it before it gets recorded in the aggregated tables.

    Example: Let’s consider if the site pages can be accessed with or without www. As a result, Google Analytics would create two rows to include both cases for each page. To avoid this, and to consolidate pageviews, create the following search and replace filter. This filter would look for “” as the hostname and replace that with “”.

    • Filter Name: Search and Replace www Filter
    • Filter Type: Custom > Search and Replace
    • Filter Field: Hostname
    • Search String: ^exampleUSA\.com$
    • Replace String:
    • Apply the filter to exampleUSA Only View

    Search and Replace Filter

    If you’re using the prepend hostname filter from above, make sure this filter comes first!

    Include a Traffic Medium

    Let’s start by Organic Traffic. To segregate organic traffic from the other means of reaching your website, define this filter and apply it to the Organic Only View.

    • Filter Name: Include Organic Only
    • Filter Type: Custom > Include
    • Filter Field: Campaign Medium
    • Filter Pattern: organic
    • Apply the filter to the Organic Only View

    You can define similar filters to only include the paid search traffic (filter pattern: cpc), email (filter pattern: email), etc.

    Include a Device Category

    First, create a filter for mobile devices. Add this following filter to the view that only contains traffic from mobile devices, i.e. Mobile Only View.

    • Filter Name: Include Mobile Only
    • Filter Type: Custom > Include
    • Filter Field: Device Category
    • Filter Pattern: Mobile
    • Apply the filter to the Mobile Only View

    You can create similar filters for Desktop Only and Tablet Only views.

    Include a Country

    To include traffic only from a particular country or region create a similar filter to this one.

    • Filter Name: Include US Traffic Only
    • Filter Type: Custom > Include
    • Filter Field: Country
    • Filter Pattern: United States
    • Apply the filter to the US Traffic Only View

    If there are multiple countries you are interested in including in a view, enter a pipe “|” separated list of them; e.g. United States|Canada|Mexico

    Filter by Country


    Well, there you have it! A grand list of simple filters that can add tremendous value to your analytics account.

    Let me know what you think and if you would recommend any other filters to be included in this list.


    Zee is a former LunaMetrician and contributor to our blog.

    • John Peterson

      Thanks for covering all the filters in details I have been using the IP filters for so long where I tend to block mine and my clients IPs so that traffic is filtered out in GA I will be adding domain based filters now to crape out traffic from sister site for one of my client and double check them using gostats. Thanks again!

      • Zee Drakhshandeh

        No problem! I’m glad you found it helpful.

      • Zee D

        Glad you found it helpful!

    • hi Zee, thank you for this insightful article. Above you have mentioned in the “Include Specific Hostname” the filter pattern for
      What about filter pattern for just Is that something GA going to contain automatically?
      Thanks for your time.

      • Thanks for the question. The filter pattern ^(www.)?$ would actually match both and The question mark “?” would match zero or one of the previous expression, which is (www.) in this case.

    • Diana

      Very good article, Zee.

      Here is my questions to you:

      I have created a filter to display the full page path in my reports – Mainly to include the domain name ( Now when creating a Goal funnel, do I need to include in the steps?

      Let me know what you think.



      • Hi Diana,

        In the Goal Funnel steps, you need to include /thank-you.

        Now normally, we think of a “thank-you” page as a Destination Goal. If this is the case, the goal should be set to “thank-you”, and you must have the page before thank-you as a step in your goal funnel.

        • Trevor Nicholls

          HI, when adding the prepend www. filter we see the desired effect in the behaviour>site content>all pages report, however, whilst the anchor text in the link appears correct, the actual url no longer works as it trys to send us to

          • That’s correct. Just copy paste the URL into a new tab – no way around that. The reason: The links used on those arrow buttons are set to href = “the hostname shown in the View Settings” + “whatever you see as the URL in that row”.
            So when you apply the filter to prepend the hostname to the request URIs, you are essentially updating the value of that row, but GA is not aware of it.

    • Murray Finlayson

      Awesome content, Zee. Thanks for providing so much useful information.
      Do you have any guidance on the ranking of the filters? For example, would you suggest putting the Spam Referrals filter #1?

      • Murray Finlayson

        Sorry, I meant that the Include Valid Hostname filter should be first. Is this correct?

        • Hi Murray,

          Thanks for the comment! And yes, I always keep my include/exclude filters on top of the list and the other filters on the bottom.

          • Murray Finlayson

            Thanks Zee, but does it matter the order of include/exclude filters?

            Specifically, I have:
            Include Valid Hostnames
            Exclude Spam Referrals
            Exclude Internal IP
            Exclude Dev/Staging

            Or does this not matter?


            • Your set up looks good.

              Filter ranking only matters when you are dealing with dependent filters, which happens when you are using the output of one filter as the input for another one. For example, you might have this filter set up:
              – Exclude Query Parameters
              – Append a Trailing Slash

              Here, it does matter when you are adding that slash (/) to the end of the Request URI; appending the trailing slash should come after you removed all the query parameters.

    • nagendra babu

      Hi its nice information, but i have a doubt ,we are adding so many filters ok .but i want to remove one filter how ?

      • If you think you are adding so many filters, well don’t do it! And there are buttons to either Remove or Delete filters in the interface. Navigate to Account > All filters > Delete or you can go to View > Filters > Remove.

    • nagendra babu

      can u plz explain me.

    • Amir

      Hi Zee,
      Awesome post!
      w.r.t. the filter “Include Specific Hostname”, is there any benefit in doing it the way you described (i.e. Customer filter type and using RegEx), vs. doing it with the Predefined filter type and using “Include only” -> “traffic to the hostname” -> “that contain” -> Hostname =
      (see image).

      • Hi,

        Using a Regex will give you more power in general. For example, what if you want to include traffic from two distinct domains, and I’d define a custom filter with Regex: example(USA|Global)?.com ,and this is not something you could do with a Predefined filter.

        I would always use the Custom filters.

        Thanks for asking!

        • Amir

          Got it about multiple domains, but if I have just one domain – is there anything wrong or not complete in using predefined?

          • No, there is nothing wrong with using predefined filters.

    • Alexandre Ayad

      Thank you for your helpful article.
      Is there a way to keep only the subdomain instead of full hostname to Request URI ?
      Event better if we can do it for any other subdomain than www.

      • Send me an example of how you want to see the data.

        • Alexandre

          Thank you for your quick answer, in fact I want to keep URI like they are usually, for example /page/ for main website and instead of having the whole hostname like just keep subdomain when it isn’t www to get URI like sub/page/

          I’ve try to change like Field A -> Extract A : Hostname : [^.]*
          but It didn’t work, then try Field A -> Extract A : Hostname : (.*(?
          It works but put www/ for existing property of main website.

          • Okay.

            There are a few steps involved, and you would need a filter for each step:

            1) Pull out the subdomain: Field A -> Extract A : Hostname : ([^.]*)
            Output To -> Constructor: custom field 1: $A1
            2) Now that you have the subdomain, create another filter to Search for www in custom field 1 and replace it with “”
            3) Finally, create yet another Advanced filter to put the result of step 2 in the beginning of the Request URI

            That should do it!

            • Alexandre

              Works great ! Thank you very much

            • Great! Glad to hear that.

    • Nikhil

      Hi Zee,
      Nice article and good explanation about GA filters. I have a question here! Is it possible to track events for multiple subdomains (say,,, using single view?
      I need tracking data(goals) to be generated for each subdomain separately on dashboard.
      Note: I said single view because we have n number of subdomians so we can not create a single view per subdomain.
      Thank you!

      • Yes. Send all the traffic to that roll-up property, then apply the “prepend hostname to request URI” filter followed by “include these subdomain only” filter. You can then define goals for the destination pages, and show them in dashboards.

    • Katherine Watier Ong

      Zee – does this Regex filter pattern still work? ^(www.)?$. I have a client whose include hostname domain filter isn’t working and I saw in a Moz article that you could instead use this pattern for the filter:||| Could the RegEx you provided be part of the reason why the include host domain filter isn’t working? Or do you have other ideas why their include host domain filter isn’t working if they’ve used your pattern above?

      • Katherine – these two patterns are entirely different. The first one is used to include the traffic from, but the second pattern, the one you saw on MOZ, is used for including traffic from several different websites. The pipe character in the second regex, “|”, is meant to work like an OR. Depending on what you are trying to do, you may use either one. They are both valid regex patterns.

    • Hi Zee,

      Thank you for your article, I was trying to create a variation of this which would only show the full host if it was a sub domain, which wouldn’t affect historical data of the main site.

      I wasn’t able to find anything on all the forums out there – so i managed to figure it out and thought i’d share.

      In the Field A -> Extract A
      Hostname > Enter (yoursubdomain.*)

      Field B -> Extract B
      Requets URl > (.*)

      Output To -> Constructor
      Requets URl > $A1$B1

      What this does:
      – Only shows the subdomain for those mentioned in field A
      – Does not affect any other data
      – Allows you to analyse data based on subdomain
      – Requires only 1 GA tracking code

      Its been working quite well for me so far, hopefully people reading this can also benefit.

      Lenny Manor

    • Extremely useful. Much needed. Thanks for sharing this list of analytics filters.

    • Jan

      Hi Zee,
      thank you for your article. I have one question about the “Remove Query String”-Filter. Maybe it’s stupid – but
      I was a little concerned, if this filter could not effect the traffic-source reporting. Having in mind that, the traffic-source information mainly comes from the query-string parameter – but personally not knowing, how this data will be processed, when it’s removed from our URI.
      But as I understood, the filter will ONLY effect data-field “request-URI”. Is that correct?
      Greetings from germany

    • kevinsprague

      Great article – can you give some advice? i have a client that is getting referral traffic from “chromecast / backdrop” – the traffic is caused by google art and culture pulling images from their site for chromecast slideshows. We want to filter out the traffic as it is skewing our visitor data but I can’t seem to be able to find a way to configure the filters so that it works.

      • Send me a screenshot of how the filter is currently set up, and I will take a look.

    • Jennifer McElligott

      Hi Zee,

      Great article. I was wondering if you could help me with the following query, I want to set up a filter and associated it to view to track sessions etc. resulting from users choosing a specific language on my site. There is a total 13 lanuages user’s can choose from.

      Will the ‘include a country’ filter work for me here, or do I need to set up a filter to track the subdomain e.g. /fr
      Any advice is appreciated 🙂

      • Hi,

        Yes, you would need to create one filter for each language and assign it to their corresponding view. Your filter will be based on subdirectories, so you would need to set it up to “include traffic from /fr/ subdirectory only”, then name your view something like “Traffic from French Pages Only”.

        Hope that answered your question.

        • Jennifer McElligott

          Hi Zee,
          Thanks for your help. When I am filling in the Subdirectory box, is the slug /fr/ enough? I don’t need to use regular expression?

          • Please send me a screenshot of how you are setting it up, and I will give you my feedback.

            • Jennifer McElligott

              When I checked the view, I was getting other languages and not just fr, so do I have it set up wrong?



            • Use a custom filter > include > Request URI > ^/fr/ >> meaning that the page path (request URI) should start with /fr/. If the last “/” is optional, then use ^/fr/? instead.

            • Jennifer McElligott

              Thanks Zee

            • Lisa

              Hi @disqus_MWLNs08RKH:disqus ,

              I also have a website based on language subdirectories and I set up a view for my French-Belgium pages. Just like Jennifer Kate, I used a Predefined filter-Include only-Traffic to Subdirectories- that contains: /fr-be/ .

              I think I shouldn’t have used the second slash, because the view doesn’t seem to be collecting views for the French-Belgium homepage…. What do you think?

              The filter that I applied seems to be perfect for filtering subdirectories, so why doesn’t it work properly? Is it necessary to apply the Custom > include > Request URI > ^/fr/ instead? What are the differences between these two solutions?

    • Jacob Berry

      This question is about the “include blog traffic only” part of your filter. My sites are all–blog instead of the as you showed in your example. How would I set up that filter?

      • I hope you have figured it out by now. For those who haven’t, configure the filter as below:

        Select ‘Custom’ filter tab
        Filter type is ‘Include’
        Filter field: Request URI
        Filter Pattern: /blog/


        • bharani

          its still showing homepage sessions with /

          • That worked every time for me. Or try this setting instead:

            Filter type: Predefined
            Include only
            Traffic to the subdirectories
            that contain
            Subdirectory: /blog

        • bharani

          i added filter seperately for blogs as u said /blogs/ but still its showing home page traffic sessions in this filter

    • Dr. Tech

      Being a newbie, perhaps this may be a trivial Q: Any detail explanation or pointer will be appreciated.

      As you create views and apply filters to it, since applied filters can’t be undone:
      Assume filter A is applied, does it filter the already collected data for the selected past days for GA view and continue to filter the incoming traffic to the target website based on this filter until changed to a different filter B?
      Or the filter stops filtration beyond the days it was viewed? Then, moving to another filter could undo or change the effect of filter A for the future incoming traffic from when this filterB is invoked– correct?

      • Filters start filtering the data moving forward – they are not retroactive. So on the day you apply filter A, it will start filtering the traffic, moving forward. When filter A is removed and filter B is added, filter B will start filtering the data. There is no looking back, and there is no change in the reports once the data is processed every day.

        • Dr. Tech

          But since multiple views are allowed for the same duration: view 1 (filter A) and view 2 (filter B) producing different analytics data over the same duration, Does the filter apply to the actual incoming traffic or to only the view perspective and the traffic is never filtered?

          • The traffic will actually be filtered in the view where you applied the filter. So if View 1 is using filter A, the data recorded in that view will be different from View 2 which is using a different filter.

    • Mahmoud A Zinji

      How to add a filter to fix this issue ?

      Property X is receiving data from redundant hostnames. Some of the redundant hostnames are:
      Redundant hostnames are counted as separate rows in reports, so hits that are going to the same page on your site from different hostnames will be split into multiple rows. With data split across multiple rows, traffic to specific pages will appear lower than it actually is.

    • Rebecca Wetherbee

      Hi Zee,
      In my Test View, I’ve set up a View-level setting to remove certain parameters, and I followed your instructions above for how to append trailing slashes.
      My Test View seems to be correctly consolidating all of my pageviews, and the # of pageviews reflected in my Test View matches the number in my un-consolidated Raw Data View — great.
      The problem is that my Test View shows fewer *unique* pageviews than my Raw Data does.

      Do you know why appending the trailing slash and/or excluding URL query parameters would lead to a reduction in the Unique Page View count?

      Screenshots below of my setup.

    • The Append Slash to Request URI filter doesn’t seem to be working. Any common reasons why this might occur?

    • alexk9

      I do cross domain tracking (dozens per property) and have implented the Prepend Hostname to Request URI filter (which is awesome)… But Im now noticing a difference in traffic between the filtered view and the default All Pages view… Why is this heppening?

    • Thanks for providing so much useful information. I have shared the same on my facebook page for my students to see.

    Contact Us.

    Follow Us



    We'll get back to you
    in ONE business day.
    Our Locations
    THE FOUNDRY [map] LunaMetrics

    24 S. 18th Street
    Suite 100

    Pittsburgh, PA 15203

    THE STUDIO [map]

    4115 N. Ravenswood
    Suite 101
    Chicago, IL 60613

    THE LODGE [map]

    2100 Manchester Rd.
    Building C, Suite 1750
    Wheaton, IL 60187