Adobe Analytics

VirginieRe2 · 6/4/25

Is there a list of compatible Adobe analytics dimensions and metrics?

For example page name can OR can not be used with conversion rate etc...

MandyGeorge · 6/4/25

For the most part, you can use any dimension with any metric. The only exceptions really are the bot page dimensions and some of the advertising analytics ones. But while you can use pretty much any dimension and metric together, whether or not they make sense is a different story.

The other thing to keep in mind for is that based on your evars persistence, or if you're using a prop, your success metric might not be returning any results, because it happens in a different hit. For example, with page and conversion rate. Your order success page is where all of the orders actually happen, so it's going to get credit for the orders. If you're trying to look at conversion rate based on something like home page or a search page, you might be getting all 0s. What you can do is use non-default attribution models and this will allow you to give credit beyond last touch so that you can see how other pages impacted your conversion rate.

So in short, n there isn't a list of compatible dimensions and metrics, because essentially any of them can be used together, it just depends on how you have them set up what type of results you will get.

Jennifer_Dungan · 6/4/25

In addition to this... Page Name cannot be used with Click / Action calls...

Interestingly, Adobe doesn't actually have a reserved metric for "Page View"... this metric is calculated based on the existence of "pageName" and/or "pageURL" in the data... anything with either or both of these values will be counted as a page view.

Now, you might be saying, but I see both of these on my tracking calls when I have click tracking... and you're right... these are sent to Adobe on your clicks and actions.. however, Adobe removes them during processing (based on their being specific click/action dimensions like "Page Event Variables")

It's for this reason that many people create a custom prop or eVar (with a hit expiry) to store their pageName values in for all hits (page views and clicks/actions), and also for URLs (which are typically only available in Data Warehouse and raw data exports). This allows you to correlate your clicks and actions back to the page on which those clicks were made.

Other than that and Bot specific tracking, as Mandy said, most things can be correlated with one another... provided it make sense within your own implementation.

VirginieRe2 · 6/4/25

Jennifer,

Page name can not be used with actions, but can Page be used with actions/clicks?

Jennifer_Dungan · 6/4/25

Page and Page Name are the same thing.... s.pageName is "Page" in workspace...

If you want to have the page / page name available on your clicks/actions, you need to track it as a custom dimension.

I call my custom dimension "Page Name", and I use an eVar so that I can have longer names than the standard dimension will hold.

Page (s.pageName) has a character limit of 100 characters, eVars have a character limit of 255.

VirginieRe2 · 6/5/25

Jennifer,

We are using an evar to collect pagename.

Its settings are :

* allocation (most recent (last)
* reset : do not reset
* expire after: visit

So, given the persistence of evars, and the configurations above, can i build a report with pagename (Evar) as a dimension and click/actions as metrics to understand which actions took place on the pages?

Jennifer_Dungan · 6/5/25

Yes, but I would be a little concerned about that Visit attribution...

On one hand, this means that you don't have to set the value explicitly on your clicks and actions (the value will persist)... on the other hand, clicks and actions that occur before the page view, or pages that fail for some reason to set a value will now have an incorrect value being collected as it will persist the name of an earlier page in the implementation....

If you aren't using attribution (i.e. set a value on Step X and making use of it on Step Z), then why configure it for attribution... The default Page Name (s.pageName) is hit based for a reason... I mean, it's probably fine... it's just that if there ends up being an issue on the site where the page name is not being set, this will mask the issue from being seen and provide incorrect data.

However, attribution concerns aside, yes, you can use this custom eVar to get Page Name information against your pages, clicks, actions, etc.

MandyGeorge · 6/5/25

That's a good point about page name. We pass our page name into an evar, and that's all I ever use, so I wasn't thinking about the original page name limitation.