Dimension not getting logged in Dashboard

[vivek091195]

Hi, I am trying to log a metric via local storage, it gets logged properly when checked in Adobe Analytics Platform Debugger, but it is getting logged with default value in Analytics dashboard.

Here is what I am doing,

• Setting a variable page_name in Local Storage.
• Set up a Rule in Adobe Data Collection, with event as Core-Direct Call and then actions as Set Variables, where I am setting an eVar against a Data Element of page name, and then Send Beacon.
• Then in Analytics dashboard, under Admin Tools -> Report Suites, I have set an eVar for consuming the page name.

When I am seeing in Debugger, the values are flowing in fine against page name, but in Dashboard, it is always logged as default value. Could you please help where I might be going wrong?

[yuhuisg · Accepted solution]

I suspect that your report is using a mismatched combination of the eVar and metric(s).

You didn't mention which metric you're using when running your report.

You also didn't mention the beacon type that you're tracking your eVar with: page view, custom link, download link, or exit link. The beacon type determines the hit-level metric that you can report with: Page Views, Custom Link Instances, Download Link Instances, Exit Link Instances respectively.

[vivek091195]

Hi, I am using Occurrences metric, and the beacon type is Custom Link.

[Jennifer_Dungan]

Bear with me.. I am going to try to understand what is happening by re-writing your steps with more details, and can you confirm if I am correct?

1. 1. You have a rule to set Local Storage variable - I assume trigger by DOM Ready or Window Loaded
   • This rule sets a value into the local storage the current page name?
2. Then you have another rule, this one sets your Dimensions and Metrics and sends the Beacon
   • You mentioned that you are setting an eVar (let's say eVar1 for example) here to a Data Element - I am assuming this is a data element that is reading the Local Storage value?
   • When you test in debugger, you said Page Name is flowing fine? As in the pageName value? or eVar1? 
   • Is the intention that eVar1 should match pageName? (current page, current pageName value?)

Since this is an action, which does not have pageName, you are using eVar1 for your click data, and when you go into your report, you are not seeing proper page names?

Can you confirm in your debugger that eVar1 (or rather your eVar) is in fact being set? I wasn't sure if you just meant that pageName was set in your description.