Debugger data layer values vs Report suite | Community
Skip to main content
Advance_Analyti
Advance_Analyti
June 29, 2020
Solved

Debugger data layer values vs Report suite

  • June 29, 2020
  • 2 replies
  • 2985 views

Hello,

 

We have created few js data elements based on data layers. The data layer naming conventions comprises of both upper case and lower case values. We have selected the option of 'force lower case' in DTM data element settings. Now, the issue is that while, the debugger shows lower case values (the way we want), the values in report suite(staging in this case) are coming as same as actual data layer values.

Can someone please help on what might be going on here and ways to fix it?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by ForgotPassword4Times

Per eVar documentation (as a sample):

Case Sensitivity
eVars are case insensitive, but they are displayed in the capitalization of the first occurrence. For example, if the first instance of eVar1 is set to "Logged In," but all subsequent instances are passed as "logged in," reports always show "Logged In" as the value of the eVar.

https://docs.adobe.com/content/help/en/analytics/admin/admin-tools/conversion-variables/conversion-var-admin.html
The docs don't specify this, but if you only pass lower case value on July 1 and use July as your reporting window it might shift (have seen this happen before).

If its just for the staging report suit you could also reset the expiration.  That might work. 

2 replies

F
ForgotPassword4TimesAccepted solution
June 29, 2020

Per eVar documentation (as a sample):

Case Sensitivity
eVars are case insensitive, but they are displayed in the capitalization of the first occurrence. For example, if the first instance of eVar1 is set to "Logged In," but all subsequent instances are passed as "logged in," reports always show "Logged In" as the value of the eVar.

https://docs.adobe.com/content/help/en/analytics/admin/admin-tools/conversion-variables/conversion-var-admin.html
The docs don't specify this, but if you only pass lower case value on July 1 and use July as your reporting window it might shift (have seen this happen before).

If its just for the staging report suit you could also reset the expiration.  That might work. 
Advance_Analyti
Advance_AnalytiAuthor
June 30, 2020
Thank you. Your account name made me laugh. Coming back to your answer, i am not sure if it will work as both props and evars are showing up discrepancy. I have same value getting captured as an evar as well as a prop.
raj_mandalapu
raj_mandalapu
June 30, 2020

Just for troubleshooting, can you please check in the .js script what configurations are loading for your data elements.

For below configuration all three are enabled - Case insensitive match, Force lowercase value, Scrub whitespace and linebreaks using cleanText

{queryParam:"utm_campaign",storeLength:"pageview",forceLowerCase:!0,cleanText:!0,ignoreCase:1},"UTM_Content":

 I feel, if the debugger shows lower case values, then the same should go to the Analytics also.

 It is good that instead of handling at report suite side, while passing value to the Analytics, you can use the .toLowerCase() method to avoid this kind of issue.

If the data is already available in the report suite, then you can use classifications to get proper count.

 

 

 

Advance_Analyti
Advance_AnalytiAuthor
June 30, 2020
Thank you. We did use .toLowerCase() but not in the beginning. We are still in testing stage and no data has gone to our prod report suites and that is why i am trying to understand, how i can fix it before it reaches my prod.
Terms & ConditionsAccessibility statement

Loading footer...