Why are sessions, bounce rate or other metrics not matching data in Google Analytics?

Listed below are some the causes as to why sessions, bounce rate and other metrics data on MPC does not match with the data as shown in Google Analytics:

• Segmenting of profiles not done right

The right segment has not been applied on MPC and traffic from certain IP addresses is not filtered. For example, Milestone employees IP addresses on the website to carry out tests.

• Multiple profiles share same base domain

For businesses that have modules such as Golf, wedding modules, etc., and language sites, the sub profiles are mapped to the sub path URLs (resort.com/dining) which are already mapped to the main URL (ex. resort.com). Now because the main profile is mapped to the base domain and sub path URLs are also mapped to the main domain profile, when data for the main domain and sub profiles are selected together, duplication of data occurs as the data of the sub path URLs are being counted separately as well as with their numbers under the main URL. To avoid duplication of numbers, select the main property separately (usually .1) from the other sub profiles and the numbers will be accurate.

• AMP property data hasn’t been included

If the website has an AMP property, then it will not be included automatically under the main domain on GA. It has to be manually included to fetch accurate data.

• One day delay in reflecting data

Data on MPC is reflected only a day later as we extract it from multiple channels and sources and give clients a collation of data.