How to create a metrics to guage overall page performance? | Community
Skip to main content
S
suchindra
New Participant
June 23, 2025
Question

How to create a metrics to guage overall page performance?

  • June 23, 2025
  • 2 replies
  • 530 views

On any given page, I track the following interactions:

  • Video views
  • Asset downloads
  • Interaction with page navigation
  • Interaction with body components
  • Engagement with the chat bot
  • 50% and 75% page scroll

To evaluate the performance of any page, I want to create a single metric that incorporates all of these interactions. I am considering a straightforward approach as follows:

  1. Create a segment that includes visits (visit container) with video views, asset downloads, interactions, engagement with the chat bot, or a 50% page scroll. Let’s name this segment "Page Engagement."
  2. Create a calculated metric:
    1. (Page Views where Page Engagement Exists) / Total Page Views

Added screenshots for reference. 

I would appreciate any recommendations or alternative approaches and would welcome suggestions on how to improve or refine this setup.

2 replies

S
suchindraAuthor
New Participant
June 30, 2025
 

 @jennifer_dungan can you help with this issue?  

Jennifer_Dungan
Jennifer_Dungan
New Participant
July 5, 2025

Hi,

 

I am trying to figure out what your end result is... but I can see a few ways that I am thinking about going about this...

 

First, if you do the Segment route, I don't think you need to use Visit Scope... since you are pairing this with the Visits metric anyway, you could simply do a HIT based segment, something like:

 

HIT [

    Download exists

    OR

    Engaged with ChatBot exists

    OR

    User Starts a Video

    OR

    .....

]

 

Call this "Engagement Actions" or something like that, then use this with the Occurrences metric (I prefer this over "page events" because Page Events is only actions, whereas Occurrences will cover actions or page views where the "engagement" is tracked). 

 

The reason I am suggesting a HIT segment, is because a VISIT Segment, if any engagement action exists, will return ALL page views and actions from that visit... the HIT segment will only return those engagement events.

 

That said, you can do this without a segment... simply make a calculated metric where you add each of the events together into a single metric:

 

Download exists

+

Engaged with ChatBot

+

User Starts a Video

+

.....

 

 

^ This should match the segment method exactly.

 

 

 

 

Now, the other consideration is if you want to apply a "weight" to the engagement... by this I mean, some events are more important than others...  For instance, a 70% scroll is better than a 50% scroll... maybe engaging with a video is more important than engaging with a menu? This would be up to you... but with the calculated metric method, you can use containers to give increased weight to certain actions:

 

[

    Download exists

    *

    1

]

+

[

    Engaged with ChatBot

    *

    1.5

]

+

[

    User Starts a Video

    *

    2

]

+

.....

 

 

Basically, instead of treating each engagement equally, you are basically creating an engagement score....

bjoern__koth
bjoern__koth
New Participant
June 23, 2025

Hi @suchindra 

 

since your events are not page view events, you likely won't see any data in your calculated metric.

All the events are custom links and not page views. Hence, you should rather use "Page Events" instead, which is the new name for Custom Link instance i.e., non-page views.

 

The rest of the segment looks in general ok, maybe you are having too many containers though (hard to say from a high level, but as long as it works, I would keep it).

 

 

 

Cheers from Switzerland!
S
suchindraAuthor
New Participant
June 23, 2025

 

Hi,

Thank you for the detailed explanation. I do see the data on using the page views as well. I want to confirm that I can use the Visits container; however, when I apply this metric to a specific page, it does not account for engagement from other pages since it's a visit-level segment?

 

Thank you!

Terms & ConditionsAccessibility statement

Loading footer...