Google Analytics Individual Qualification Exam Answers

Which report helps identify which browsers may have had problems with your website?

The new vs Returning report

The active Users report

The Source/Medium report

The Browser & OS report

Explanation:

If conversion rates are lower than average for particular browsers or platforms, browse the site with those browsers and platforms. Pay particularly close attention to landing pages, checkout forms and any pages that users must navigate in order to convert. Correct any usability issues you find with these pages.

Read more here: https://support.google.com/analytics/answer/2659291

Compare your conversion rates by Browser, Operating System, Screen Resolution, Screen Colors, and other technology dimensions. If the conversion rates are lower for any technology or platform, you may have identified a design problem that, once fixed, will help you make money.

Investigation

1. Navigate to Audience > Technology > Browser & OS.
2. Select Goal Set or Ecommerce (under the Explorer tab, upper left of report).
3. Select the Data view (at top right of table) if not already selected.
4. Look for low and lower than usual Conversion Rates for your individual micro goals (or the Ecommerce Conversion Rate on the Ecommerce tab).

Repeat this investigation for each of the following dimensions: Operating System, Screen Resolution, Screen Colors, Flash Version, and Java Support. (Select each of these as a primary dimension above the table.)

Which of these represents the hierarchical structure of a Google Analytics account?

View > Account > Property

Account > View > Property

Account > Property > View

Property > Account > View

Explanation:

Read more here: https://support.google.com/analytics/answer/1009618

 Accounts

An account is your access point for Analytics, and the top-most level of organization.

You need at least one account so you can have access to Analytics, and so you can identify the properties you want to track. How you manage the relationship between accounts and properties is up to you. You can use a one-to-one relationship of one account/one property, or you can use a one-to-many relationship of one account/many properties. You can have multiple Analytics accounts. If you do not have an account, sign up for one at www.google.com/analytics.

 Properties

A property is a website, mobile application, or device (e.g. a kiosk or point-of-sale device.) An account can contain one or more properties.

Within an Analytics account, you add the properties from which you want to collect data. When you add a property to an account, Analytics generates the tracking code that you use to collect data from that property. The tracking code contains a unique ID that identifies the data from that property, and makes it easily identifiable in your reports. Analytics also creates one unfiltered view for each property you add.

Learn more about adding properties to your Analytics account.

 Views

A view is your access point for reports; a defined view of data from a property. You give users access to a view so they can see the reports based on that view’s data. A property can contain one or more views.

For example, within a property you might have:

• one view of all the data for www.example.com
• one view of only AdWords traffic to www.example.com
• one view of only traffic to a subdomain like www.sales.example.com

When you add a property to an account, Analytics creates the first view for that property. That first view has no filters, and so includes all the data for that property. You should leave this original view unfiltered, so that you always have a view in which you can see all the data. You can create additional views and apply filters to them so that they each include the specific subset of data in which you’re interested.

Once you create a view, the reports for that view will show data from the creation date of the view forward. For example, if you create a view on June 1, that view will show data from June 1 forward, but will not show any data collected prior to June 1.

If you delete a view, that specific perspective of the data is gone forever. Don’t delete a view if you think you might ever want to report on that particular perspective of the data.

Learn more about adding views to your Analytics properties.

 Users and   permissions

You add users to an Analytics account. You can add those users at the account, property, or view level; and you can restrict their access at each level. When you add a user, you identify that person by an email address that is registered in Google accounts, and you assign the appropriate permissions. Depending on the permissions you assign, that user can manage other users, perform administrative tasks like creating additional views and filters, and see the report data.

Custom Reports will NOT let you do what?

Use multiple dimensions together in the same report

Create a report with Custom Metrics

Pair metrics and dimensions of different scopes

Use a Custom Dimension as a primary dimension

Explanation:

Pairing metrics and dimensions of different scopes is not possible in any report.

Which of these is a scope for Custom Metrics?

Session

Event

Hit

User

Explanation:

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.

Read more here: https://support.google.com/analytics/answer/2709828#scope

Scope determines which hits will be associated with a particular custom dimension value. There are four levels of scope: product, hit, session, and user:

• Product – value is applied to the product for which it has been set (Enhanced Ecommerce only).
• Hit – value is applied to the single hit for which it has been set.
• Session – value is applied to all hits in a single session.
• User – value is applied to all hits in current and future sessions, until value changes or custom dimension is made inactive.

Product-level scope

When a custom dimension has product-level scope, the value is only applied to the product with which the value is set. Because multiple products can be sent in a single hit, multiple product-level scoped custom dimensions can be sent in a single hit.

Hit-level scope

When a custom dimension has hit-level scope, the value is only applied to the hit with which the value was set. This is demonstrated in Figure A, Figure B, and Figure C below:

Session-level scope

When two values with session scope are set at the same index in a session, the last value set gets precedence and is applied to all hits in that session. In Figure D below, the latest value set overwrites any previous values for that index:

User-level scope

Lastly, if two user-scoped custom dimension values are set within the same session, the last value set gets precedence for the current session, and is applied to future sessions for that user.

In Figure B below, CD value A is applied to all hits in session 2, just like a session-level CD. However in Figure C, unlike with session-level scope, the CD value A continues to be applied to hits in the third session due to CD1 having user-level scope:

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