Certification Answers

We help you to pass your exams

EN FR ES DE IT PT RU PL NL TR JA

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

 

 

Google Analytics Individual Qualification Exam Answers

 

 

Related content

Related posts: