Introduction to Audience Analysis in Google Analytics?
Introduction to audience analysis
The Audience reports provide insight into
- the demographics of your audiences. Go to Audience > Demographics.
- your mix of new and return users and the level of engagement of your users. Go to Audience > Behavior.
- the browsers and networks being used to access your site/app. Go to Audience > Technology.
- the mobile devices being used to access your site/app. Go to Audience > Mobile.
Compare mobile conversion rates:
Use the Mobile reports to compare conversion rates for mobile as a whole, and for each mobile platform, with conversion rates for desktop.
I.Navigate to Audience > Mobile > Overview.
II.Select Goal Set or Ecommerce (under the Explorer tab, upper left of report).
To repeat this investigation for each mobile device, navigate to Audience > Mobile > Devices.
Target Profitable Geographic Areas
You can use the Location report to identify regions and cities with higher than average performance metrics. You can then target campaigns to these areas.
I.Navigate to Audience > Geo > Location.
II.Use Segments to apply the Search Traffic Default Segment.
III.Click the map to drill down to a relevant country/territory, such as the United States. Alternatively, use the advanced filter in the table to exclude local areas and keep an international view.
IV.In the table, change the primary dimension to either Region (e.g., state) or City.
V.You can now compare how regions/cities compare with respect to each metric in the table. To identify high and low converting locations, choose a Goal Set or Ecommerce under the Explorer tab.
Encoded URLs in Reports
If you Previously matched encoded URLs in features like Filters and Segments.
This information is specifically for users who configured Analytics features to match encoded URLs (e.g., /%D0%B7%… rather than /home).
Languages that don’t fit in 7-bit ASCII (e.g., Cyrillic) sometimes display encoded URLs in reports (e.g., you might see /%D0%B7%… instead of /home).
Analytics has created a fix for the 7-bit ASCII issue so that URLs in those languages are no longer displayed as encoded.
If you have previously configured any of the following features to target encoded URLs, then you need to reconfigure those features to instead target the actual URL (e.g., /home):
- Remarketing Lists
- Content Grouping
- Big Query
- Any custom configurations that you have set up in your internal systems that might use encoded URIs