Page Engagement Rate at page-level

[ericnguyen021]

Hi Community,

We have implemented an event 1 that fire when user do certain behavior like clicking or scrolling the page. Where it is possible for us to have 1 page view and multiple engagement event 1. Our team want to create an engagement metric for page-level where HIT CONTAINER event 1 exist (Page views) / Page views, but it doesn't work. Could you advise?

The goal is to be able to use page URL as dimension and this metric for visualization so we can tell how engagement rate each page are performing.

A couple of solutions we have tried is using the visit container:

1. VISIT CONTAINER event 1 exist (Page views) / Page views. This rule pulls all page view from that visit not just the page where event 15 fire, so this possibly inflate the engagement number.

2. HIT CONTTAINER event 1 exist (visits) / Visits. This rule worked but it's also at the visit level and we are looking to get a page level metric.

3. Distinct Count Page URL (event 1 exist) / page views - issues with this rule is that it only counts 1 event15 per page URL.

Please advise on possible approach or solution. Please provide details on how should set up our segments if possible.

Thank you in advance!!

[ericnguyen021 · Accepted solution]

Issue resolved. We planned to limit event1 to fire only 1 time per page views.

[Jennifer_Dungan]

Lol, I was just about to start posting comments. Glad you figured it out... 

Yes, engagement events that can trigger multiple times can definitely cause some headaches.

The other thing you might want to consider is engagement weights... 

Like a scroll event is worth 1, hitting "Read More" to load additional content could be weighted to 5, signing up for a newsletter on an overlay could be 10, etc...

It wouldn't be just a simple engagement over page views type calculation... but could provide different types of understanding for your engaged users.

I would have a table with eventX, and segment:eventX exists stacked with Visits and stacked with Unique Visitors

Segment:

HIT [

     eventX exists

]

EventX is the raw number of engagements (PVs), the column with the segment and visits would show me the number of visits where people engaged, and the segment and UVs would show me the numbers of visitors who engaged...

Now, something like scrolling, it's probably going to be close to 100% visits and visitors... but a different type of engagement, like "expand element" or "view more" would be a lot more telling.

[Meghan_Powers]

And depending on your contract and number of server calls you want to use for this, we've also implemented something similar where we just have a binary 'scroll' event that only fires once per visit to separate out true bounces from people actively engaged on the page (like that might scroll down to read an article) but don't necessarily go to another page.