Certification Answers

We help you to pass your exams

EN FR ES DE IT PT RU PL NL TR JA

Blog

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

By

 

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.

 

 

Which tags does Google Analytics recommend to accurately track campaigns?

By

 

Which tags does Google Analytics recommend to accurately track campaigns?

 

Source, Content, and Term

 

Medium, Source, and Content

 

Medium, Source, and Campaign

 

Campaign, Content, and Term

 

 

Explanation:

The URL Builder has six fields, but you generally need to use only Campaign Source, Campaign Medium, and Campaign Name.
Read more here: https://support.google.com/analytics/answer/1037445

 

1. Tag only what you need.

If your Analytics account is linked to an active Google AdWords account and you have auto-tagging enabled, you don’t need to tag your destination URLs in AdWords. Analytics automatically tracks all of your AdWords campaigns. However, if you run paid search campaigns on search engines other than Google, you’ll need to tag the destination URLs for those ads.

Referral sites are automatically detected and displayed in your reports. However, if you want to associate a campaign name or ad type (such as “banner_ad”) with referral traffic, you should tag links on referral sites.

There are certain links that you don’t need to tag, and many times are not able to tag. You should not attempt to tag organic (unpaid) keyword links from search engines. Search engine names are automatically detected and displayed in your reports. And again, you don’t need to tag AdWords URLs as long as you are using auto-tagging.

2. Create your links with the URL builder.

Campaign links consist of a URL address followed by a question mark (?), and then your campaign variables separated by ampersands (&), for example: http://www.example.com/?utm_source=adsite&utm_campaign=adcampaign.

However, you don’t need to worry about link syntax if you use the URL Builder to generate your URLs. You can then copy and paste the links in your ad. If you’re wondering which fields to fill in, you’re ready for step 3, below.

3. Use only the campaign variables you need.

The URL Builder has six fields, but you generally need to use only Campaign Source, Campaign Medium, and Campaign Name. Campaign Term allows you to specify the paid search keyword. You can use Campaign Content to indicate the specific ad, button, or link that was clicked. The table below shows how you might tag the two kinds of online campaigns: email campaigns, and paid keywords.

 

Email campaign Paid search campaign
Campaign Source newsletter1 yahoo
Campaign Medium email cpc
Campaign Term the search term associated with this traffic
Campaign Content call_to_action_2
Campaign Name productxyz productxyz

4. Don’t send personally identifiable information.

Note that the Analytics terms of service, which all Analytics customers must adhere to, prohibits sending personally identifiable information (PII) to Analytics, such as names, social security numbers, email addresses, or any similar data. Learn more about the Analytics privacy principles.

 

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

 

Custom Reports will NOT let you do what?

By

 

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?

By

 

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:

Figure A: User sends two hits (H1, H2). H2 has a CD1 value of A. That value is only applied to H2.
Figure B: User sends a third hit (H3). H3 has no CD value.
Figure C: User sends a fourth hit (H4). H4 has a CD1 value of B. That value is only applied to H4.

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:

Figure A: User sends a hit (H1) with no CD value.
Figure B: In the same session, user sends a second hit (H2) with CD1 value set to A. Session scope causes value A to also be applied to H1.
Figure C: User sends a third hit (H3). Although no CD1 value is sent with H3, session scope causes value A to be automatically applied to H3.
Figure D: User sends a fourth hit (H4) with a new CD1 value B. Session-scope applies value B to all the hits in the session, overwriting value A in the previous hits.

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:

Figure A: User shas a session with three hits (H1, H2, H3). No CD values are set.
Figure B: The same user returns and has another session, with three more hits. CD1 value is set to A on H3. CD1 value is then applied to all hits in session.
Figure C: User returns for a third session with three more hits. CD1’s user-level scope causes value A to be applied to all hits in session 3.

 

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

 

What four parameters can you include with an event hit for reporting?

By

What four parameters can you include with an event hit for reporting?

 

  • Category, Action, Label, Unique Events
  • Category, Action, Label, Total Events
  • Category, Action, Label, Value
  • Event, Category, Action, Label

 

or

 

Which parameters can be included with an event hit for reporting?

  • Category, Action, Label, Unique Events
  • Category, Action, Label, Total Events
  • Category, Action, Label, Value
  • Event, Category, Action, Label

 

Explanation:

Events are user interactions with content that can be tracked independently from a web page or a screen load.An Event has the following components. An Event hit includes a value for each component, and these values are displayed in your reports.

  • Category
  • Action
  • Label (optional, but recommended)
  • Value (optional)

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

 

Events are user interactions with content that can be tracked independently from a web page or a screen load. Downloads, mobile ad clicks, gadgets, Flash elements, AJAX embedded elements, and video plays are all examples of actions you might want to track as Events.

See Event data

You need to add Event tracking code to your site or app in order to see data in your Events reports. Read Set up Event Tracking.

To see Events reports:

  1. Sign in to Google Analytics.
  2. Navigate to your view.
  3. Open Reports.
  4. Select Behavior > Events.

Anatomy of Events

An Event has the following components. An Event hit includes a value for each component, and these values are displayed in your reports.

  • Category
  • Action
  • Label (optional, but recommended)
  • Value (optional)

For example, you might set up a video “play” button on your site so that it sends an Event hit with the following values:

  • Category: “Videos”
  • Action: “Play”
  • Label: “Baby’s First Birthday”

Category

A category is a name that you supply as a way to group objects that you want to track. Typically, you will use the same category name multiple times over related UI elements that you want to group under a given category.

Suppose you also want to track how many times the video is downloaded. You could use:

  • Category: “Videos”
  • Action: “Downloaded”
  • Label: “Gone With the Wind”

In this case, there would be only one category—Videos—in your reports, and you could see aggregate metrics for user interaction with the total set of elements for that single video object.

However, it’s likely that you will have more than one single object that you want to track using Event Tracking, and it’s worth considering how you want to categorize your reporting before you implement the call. For instance, you might want to track all separate movies under the main category of “Videos” so that you get aggregate numbers for all video interaction, regardless of which one users interact with.

On the other hand, you might create separate categories based on the type of video—one for movie videos and one for music videos. You might also want a separate category for video downloads:

  • Videos – Movies
  • Videos – Music
  • Downloads

In this scenario, you could see the total combined event count for all three categories in your reports. The Total Eventsmetric displays all event counts for all categories that you have supplied in your Event Tracking implementation. However, you will not be able to view combined metrics for all Videos separately from Downloads, because detailed event metrics are combined under their respective categories.

While the Event Tracking object model is entirely flexible, you should first plan your desired reporting structure before deciding upon your category names. If you plan to use the same category name in multiple locations, be careful to correctly reference the desired category by name. For example, if you plan to call your video tracking category “Video” and later forget and use the plural “Videos,” you will have two separate categories for video tracking. Additionally, if you decide to change the category name of an object that has already been tracked under a different name, the historical data for the original category will not be re-processed, so you will have metrics for the same web page element listed under two categories in the reporting interface.

 

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