Defining index page = discrepancies in unique pageviews
We created a test view to test defining the index page for our website as index.html. We wanted to create a test view to ensure nothing happened to the data once we made this change. It has been implemented for a few months, and it seems as though it is mostly tracking correctly - pageviews, avg. time on page, bounce rate, and % exit all match up versus the view that does not have the index page defined. However, there is always a discrepancy in the UNIQUE pageviews column. It's never a huge discrepancy, just a few visits. I am guessing this might just be a bug, but I wasn't sure if there was some sort of explanation. I can't find a reason for it.
Re: Defining index page = discrepancies in unique pageviews[ Edited ]
August 2016 - last edited August 2016
Did you use 'default page' field in Google Analytics in order summarize 2 pageviews in a single line item?
Technically, it should not have an impact on the total number of pageviews but if you're analyzing a single page, you might see a difference.
Are you sure that you haven't forgotten to configure any filters to one of the views? (Do both views have exactly the same configuration except the 'default page' value?)
Here you can read more about the default page field: