Expand my Community achievements bar.

Applications for the 2024-2025 Adobe Analytics Champion Program are open!
SOLVED

Log a filter dimension inside Page dimension

Avatar

Level 2

For my application, I want to log Page Name as well as Filter Name, Filter Name will be a sub set of a Page Name
For e.g., I have a Reports Page where a user can run different reports. When a user lands on the Reports page, I want to log Run Reports.
And when a user selects any Report to Run, I want to log the specific Report Name as filter.
So, when I view the page metric on dashboard, I can drag and drop the filter dimension to view what all Reports are run by the user.

 

To achieve the above behaviour, this is what I did so far,

1. When a user lands on Reports page, I am setting Run Reports as pageName in my local storage, and in Adobe Data Collection, I set up event as Core-Direct Call and then actions as Set Variables, where I am setting an eVar against a Data Element of pageName, and then Send Beacon(Custom Link). At this point I am setting Filter as NA in Data Collection.

2. When a user selects any Report, I am setting ReportName as filter in my local storage, and in Adobe Data Collection, I set up event as Core-Direct Call and then actions as Set Variables, where I am setting an eVar against a Data Element of filter, and then Send Beacon(Custom Link).

 

I tried debugging it via Adobe Experience Platform Debugger, and it looks like below.  

Screenshot 2023-04-22 at 11.26.50 AM.png

The debugger shows exactly what I need.

 

But when I view it in Analytics Dashboard under Occurrences Metric, I am seeing the page name correctly as Run Reports, but when I drag and drop the Filter dimension, it just gives me NA, and not Customer Maps - 5823, Metro Summary - 5823, Competition Summary - 5823 and Guzzler - 5823.

 

Screenshot 2023-04-22 at 11.39.24 AM.png

 

I am unable to understand why it's happening and how can I achieve my desired results. Could someone please help me out here? 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

The pageName dimension (despite being part of the action call) is stripped out of the actual tracking during processing of the hit.

 

pageName can only ever be on page view beacons....

 

Most people, to get around this, create an eVar (set at a Hit Level expiry), and set this eVar on all hits (page views s.t() and actions s.tl()) to the same value as their pageName... so that it is available for all correlations.

 

Using an eVar also has the added bonus of being able to support up to 255 characters, as opposed to pageName's 100 character limit.

 

This can be done in multiple ways...

 

  1. You can set your eVar in Adobe Launch to use the same Data Element (directly passing the value into the eVar)
  2. You can use "dynamic variable notation"... i.e. in your eVar value use D=pageName as the value... what this will do is duplicate the value of pageName into your eVar (don't worry, duplication happens before pageName is removed from the action calls)
  3. Use a Processing Rule to set the value of you eVar to the same as "Page Name" (this should happen before the Page Name is removed - but double check... but I am sure I have used this in the past when I wanted to get a change up quickly without waiting for a deployment window)

 

This is something a known annoyance.. but since Adobe tracks every hit that has a "Page" (pageName) value, or a "Page URL" (g) as a page view, you can't force these to have values without inflating your page view metrics....

 

Hence why it's a common trick to use eVars to set both pageName and URLs for use in all our reports.

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

The pageName dimension (despite being part of the action call) is stripped out of the actual tracking during processing of the hit.

 

pageName can only ever be on page view beacons....

 

Most people, to get around this, create an eVar (set at a Hit Level expiry), and set this eVar on all hits (page views s.t() and actions s.tl()) to the same value as their pageName... so that it is available for all correlations.

 

Using an eVar also has the added bonus of being able to support up to 255 characters, as opposed to pageName's 100 character limit.

 

This can be done in multiple ways...

 

  1. You can set your eVar in Adobe Launch to use the same Data Element (directly passing the value into the eVar)
  2. You can use "dynamic variable notation"... i.e. in your eVar value use D=pageName as the value... what this will do is duplicate the value of pageName into your eVar (don't worry, duplication happens before pageName is removed from the action calls)
  3. Use a Processing Rule to set the value of you eVar to the same as "Page Name" (this should happen before the Page Name is removed - but double check... but I am sure I have used this in the past when I wanted to get a change up quickly without waiting for a deployment window)

 

This is something a known annoyance.. but since Adobe tracks every hit that has a "Page" (pageName) value, or a "Page URL" (g) as a page view, you can't force these to have values without inflating your page view metrics....

 

Hence why it's a common trick to use eVars to set both pageName and URLs for use in all our reports.

Avatar

Level 2

@Jennifer_Dungan  Thanks for the reply, it's really helpful.

Avatar

Community Advisor

You're very welcome... this is something it took some of us years to realize... so if I can save anyone this pain, I am glad to do so