Average Page Depth in CJA

[brentrad]

Any recommendations for replicating Average Page Depth in CJA? This was an out-of-the-box metric in Adobe Analytics, and the I'm not having any luck using the new Depth derived field function. I've tried two derived fields:

• Option 1:
• Rule 1: Depth function with Page Name as the value
• Option 2:
• Rule 1: Depth function with Page Name as the value
• Rule 2: Rule 1 summarized by mean method with session scope

For each option, I configured two versions of a metric: one in which Behavior = count values and on in which Behavior = count instances. The underlying Page Name dimension shows similar session counts in Adobe Analytics and CJA.

[bjoern__koth]

Hi @brentrad 

maybe have a look at the new Event Depth.

https://experienceleague.adobe.com/en/docs/customer-journey-analytics-learn/tutorials/components/dim...

[brentrad]

We have already brought in the Event Depth dimension as a replacement for the Hit Depth dimension available in CJA. Average Page Depth is different, as it (essentially) takes the average of all the Event Depths (pageviews only) and divides it by the number of visits for a given dimension item. 

[DanIMS1]

Hi @brentrad,
Currently, there isn't an default page depth but it would be a good feature to have.

What I did to get around this was set up a counter in the session storage, that would increase by 1 when a page view event was triggered. This counter value is passed in all the Web SDK hit as the page depth. You can then set the value as a dimension to see the actual page depth a specific user got to and also set the value as a metric to then be able to generate a calculated metric to get the average value. The only downside to this is that you may need to change the way you deal with retrieving and storing the page depth value if you have cross domain tracking. 

I did a similar thing with the local storage for session count and hit depth before the new event depth metric was released.

Hope this helps,
Dan

[Vinay_Chauhan]

Hi @brentrad 

CJA doesn’t have an out-of-the-box “Average Page Depth” like AA, so you’ll need to build it with available fields. The closest approach is -

1. Use Event Depth (or a session counter passed via Web SDK) to capture depth per hit.

2. Build a calculated metric: Sum of Event Depths (pageviews only) ÷ Sessions.
   
   

That replicates the AA definition - average number of pages viewed per session. If you need more accuracy across domains or devices, you may need to pass your own page depth counter at collection time.

[Josh__Stephens]

Hi @brentrad I believe this is a perfect use case for the new derived field depth function.

In your derived field, first use a function such as Case When to filter for only events with Page Name. Then add a depth function to capture the results of those filtered events.

You can bring this derived field into the data view as either a dimension or metric. If you select metric, I believe you'll then need to use a calculated metric to divide the total result by sessions to get the average value.