Uncategorized @en

 

To send data from a web-connected device like a point-of-sale system to Google Analytics, what would you use?

 

Data Import

 

The Networking Protocol

 

Browser cookies

 

The Measurement Protocol

 

Explanation:

The Measurement Protocol lets you send data to Analytics from any internet-connected device. It’s particularly useful when you want to send data to Analytics from a kiosk, a point of sale system, or anything that is not a website or mobile app
Read more here: https://support.google.com/analytics/answer/6086079

 

A standard set of rules for collecting and sending hits from any internet-connected device to Analytics.

The Measurement Protocol lets you send data to Analytics from any internet-connected device. It’s particularly useful when you want to send data to Analytics from a kiosk, a point of sale system, or anything that is not a website or mobile app. Because, while the Analytics JavaScript and mobile SDKs automatically build hits to send data to Analytics from websites and mobile apps, you must manually build data collection hits for other kinds of devices. The Measurement Protocol defines how to construct the hits and how to send them to Analytics.

Measurement Protocol Overview

Getting Started

Here are the resources you need to get started:

• Read the developer guide to learn how to send data to Google Analytics.
• Read the parameter reference guide to learn about the types of data you can send.
• Try out the Measurement Protocol Hit Builder, a tool that lets you interactively construct and validate Measurement Protocol hits.

 

https://www.youtube.com/watch?v=3fZUevMFz7U

 

What would you set up to collect how many comments users posted to a webpage on your site?

 

Custom Metric

 

Custom Dimension

 

Custom Channel Groupings

 

Calculated Metric

 

 

Explanation:

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?hl=en#example-metrics

 

Similar to custom dimensions, custom metrics can have different scopes. Hit-level custom metrics get associated with all the hit level dimensions with which it was sent. Similarly, product-level custom metrics are associated only with the product with which it was sent. The following examples illustrate these two types of custom metrics.

Hit-Scoped Custom Metric Example

In the examples above, the game developer has been tracking each play of a level as a screen view. In each of the reports generated, the screen view metric is used to represent a player’s attempt to complete a level.

However, the developer also wants to know the completion rate of each level.

To determine the rate of completion, the developer will use a new custom metric called Level Completions and compare it to screen views for each level.

 

https://www.youtube.com/watch?v=sfj81VmBJjw

 

By default, which of these is NOT considered a “source” in Google Analytics?

 

google

 

(direct)

 

email

 

googlemerchandisestore.com

 

 

Explanation:

In Google Analytics, Email comes under “Medium”, is not considered a “source”.

 

https://www.youtube.com/watch?v=21IGQYNiN7g

 

 

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.

Difference between web and app views

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.