Home » Blog
Which of these user characteristics CANNOT be used to create a Custom Segment?
Users 25 to 34 years of age who have their browser set to Spanish
Users that engaged in your social media or email campaigns
Users who have children
Users that viewed a page on your website and then watched a video
Explanation:
The childen of users cannot be use in “Custon Segment”.
If a filter excludes data from a view, that data can never be recovered for that view.
False
True
Explanation:
Google Analytics recommend that you don’t delete or add filters to your original view. When you delete a view, that particular historical perspective of the data is gone. When you add filters to a view, the data you exclude is unavailable. To preserve all your original data and also control the specific perspectives of that data, create a copy of your original view or set up additional views and customize each one to meet your reporting goals.
Read more here: https://support.google.com/analytics/answer/2649553
A reporting view is the level in an Analytics account where you can access reports and analysis tools.
Analytics automatically creates one unfiltered view for every property in your account, but you can set up multiple views on a single property. Any data you send to an Analytics property automatically appears in all views associated with that property. For example, if you collect data from two websites and send it to one property, then data from both websites appears in all reporting views on that property. This is also true for web and app data. If you collect data from a mobile app and from a website, and both your SDK and your tracking code send data to one property in your Analytics account, all data (both web and app hits) appear in all reporting views associated with that property.
You can use filters to customize views and see only a subset of data in your reports. You might, for example, have one view to filter out all internal traffic, and another to include only activity from a specific website directory or subdomain. If you send web and app data to the same property, you might want want to use filters to exclude web or app data from specific views. Other Analytics reporting tools, like Goals, Segments, and Alerts are all applied to individual views. You can also restrict user access to specific views so you can control who sees what data.
We recommend that you don’t delete or add filters to your original view. When you delete a view, that particular historical perspective of the data is gone. When you add filters to a view, the data you exclude is unavailable. To preserve all your original data and also control the specific perspectives of that data, create a copy of your original view or set up additional views and customize each one to meet your reporting goals.
When you create a view, you can choose between an app view and a web view. These two view types give you a slightly different analysis experience, but are otherwise the same. For example, app views give you some reports that aren’t available in web views, like Crashes and Exceptions and the Google Play reports and web views give you Site Content reports.
Both types of views can display any data you send to your property, regardless of how you collect those hits. For example, you can see web data in your app views and app data in your web views.
If you’re only collecting and sending one type of data to Google, we recommend using views that will give you the best analysis experience. For example, if you only collect data from mobile apps, select app when you create a view and if you only collect data from websites, select web.
https://www.youtube.com/watch?v=KYL4MvvTASQ
Filters may be applied retroactively to any data that has been processed.
False
True
Explanation:
Is true, to any data that has been processed you can aplied filtes retroactively.
Segments are applied before sampling in reports.
False
True
Explanation:
Analytics applies segments after it samples the property-level data, and after it applies filters, which can also reduce the number of sessions included in a sample.
https://support.google.com/analytics/answer/2637192?hl=en
In data analysis, sampling is the practice of analysing a subset of all data in order to uncover the meaningful information in the larger data set. For example, if you wanted to estimate the number of trees in a 100-acre area where the distribution of trees was fairly uniform, you could count the number of trees in 1 acre and multiply by 100, or count the trees in a half acre and multiply by 200 to get an accurate representation of the entire 100 acres.
This article explains the circumstances under which Analytics applies session sampling to your data in order to give you accurate reports in a timely fashion.
Default reports are not subject to sampling.
Ad-hoc queries of your data are subject to the following general thresholds for sampling:
The following sections explain where you can expect session sampling in Analytics reports.
Analytics has a set of preconfigured, default reports listed in the left pane under Audience, Acquisition, Behavior, and Conversions.
Analytics stores one complete, unfiltered set of data for each property in each account. For each reporting view in a property, Analytics also creates tables of aggregated dimensions and metrics from the complete, unfiltered data. When you run a default report, Analytics queries the tables of aggregated data to quickly deliver unsampled results.
https://www.youtube.com/watch?v=TiT2gXBHRrg
What feature would you set up to collect company-specific data such as Member Status?
Custom Filter
Event Tracking
Custom Metric
Custom Dimension
Explanation:
In many cases, you’ll have the option to use events, screen views, and/or a custom metric to track your most important metrics. However, custom metrics can produce more flexible and more readable custom reports and as such are a convenient way to track your most important metrics
Read more here: https://support.google.com/analytics/answer/2709828
Custom dimensions and custom metrics are like default dimensions and metrics in your Analytics account, except you create them yourself. You can use them to collect and analyze data that Analytics doesn’t automatically track.
Custom dimensions and metrics allow you to combine Analytics data with non-Analytics data, e.g. CRM data. For example:
Custom dimensions can appear as primary dimensions in Custom Reports. You can also use them as Segments and secondary dimensions in standard reports.
Custom dimensions and metrics are only available for properties that have either been enabled for Universal Analytics or contain at least one app reporting view. Custom dimensions and metrics are supported by the Google Analytics SDKs for Android and iOS v2.x or higher, analytics.js, and the Measurement Protocol.
Custom dimensions and metrics require additional setup in your Analytics account and in your tracking code. Once you complete both steps of the setup, you can use them in your reports.
There are 20 indices available for different custom dimensions and 20 indices for custom metrics in each property. 360 accounts have 200 indices available for custom dimensions and 200 for custom metrics.
Custom dimensions cannot be deleted, but you can disable them. You should avoid trying to reuse custom dimensions. When you edit the name, scope, and value of a custom dimension, both the old and the new values can be paired with the either the old or the new dimension name. This conflates data in your reports in a way that cannot be accurately separated with a filter.
https://www.youtube.com/watch?v=mvzFkE4B2e0
Filters let you include, exclude, or modify the data you collect in a view.
Explanation:
Filters allow you to limit and modify the data that is included in a view. For example, you can use filters to exclude traffic from particular IP addresses, focus on a specific subdomain or directory, or convert dynamic page URLs into readable text strings.
Read more here: https://support.google.com/analytics/answer/1033162
