Why is key:value pair displaying as [object Object] in the debugger? | Community
Skip to main content
E
earl5273
Level 2
August 5, 2022
Solved

Why is key:value pair displaying as [object Object] in the debugger?

  • August 5, 2022
  • 1 reply
  • 1097 views

Hello,

While troubleshooting my web events going to Analytics, my eVar18 value is displaying as "[object Object]" in the Adobe Experience Platform Debugger.  

When I look at my web tools console, I do see expected content for those same key:value pairs.

Why is the debugger not display the correct values for the key:value pair?

Here is the out put from the web tools console:

"""

[Adobe Analytics] Applying the following properties on tracker: "{"eVar1":"search_page.select","eVar2":"https://dev2.doc.workday.com/r/Z9lz_01hqDMDg6NSf7wCBQ/Jp4qKxuD~SKGomsmdrKAkA","eVar3":"dev2.doc.workday.com","eVar4":"« payroll » • Search Results • Administrator Guide","eVar5":"Z9lz_01hqDMDg6NSf7wCBQ","eVar6":"Authentication and Security","eVar8":"Jp4qKxuD~SKGomsmdrKAkA","eVar9":"Steps: Set Up Multifactor Authentication Using Emailed One-Time Passcode","eVar10":"/r/Z9lz_01hqDMDg6NSf7wCBQ/Jp4qKxuD~SKGomsmdrKAkA","eVar11":"https://dev2.doc.workday.com/api/authentication/sso/okta/callback?client_name=okta","eVar13":"fc2ba492-9432-44ea-8d5c-38fe8d82f2df","eVar14":"2aac8ae1-a869-4988-bccb-300918f1ad33","eVar15":"payroll","eVar17":"global","eVar18":[{"key":"prodname","values":"Authentication"}],"eVar19":1,"eVar20":null,"prop1":"search_page.select","prop2":"https://dev2.doc.workday.com/r/Z9lz_01hqDMDg6NSf7wCBQ/Jp4qKxuD~SKGomsmdrKAkA","prop3":"dev2.doc.workday.com","prop4":"« payroll » • Search Results • Administrator Guide","prop5":"Z9lz_01hqDMDg6NSf7wCBQ","prop6":"Authentication and Security","prop8":"Jp4qKxuD~SKGomsmdrKAkA","prop9":"Steps: Set Up Multifactor Authentication Using Emailed One-Time Passcode","prop10":"/r/Z9lz_01hqDMDg6NSf7wCBQ/Jp4qKxuD~SKGomsmdrKAkA","prop11":"https://dev2.doc.workday.com/api/authentication/sso/okta/callback?client_name=okta","prop13":"fc2ba492-9432-44ea-8d5c-38fe8d82f2df","prop14":"2aac8ae1-a869-4988-bccb-300918f1ad33","prop15":"payroll","prop17":"global","prop18":[{"key":"prodname","values":"Authentication"}],"prop19":1,"prop20":null,"linkTrackVars":"eVar1,eVar2,eVar3,eVar4,eVar5,eVar6,eVar7,eVar8,eVar9,eVar10,eVar11,eVar13,eVar14,eVar15,eVar16,eVar17,eVar18,eVar19,eVar20,eVar22,eVar23,prop1,prop2,prop3,prop4,prop5,prop6,prop7,prop8,prop9,prop10,prop11,prop13,prop14,prop15,prop16,prop17,prop18,prop19,prop20,prop22,prop23"}".

"""

 

Thank you.

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 yuhuisg

Verify how you're setting eVar18 in your implementation. If the value that you're using is indeed a standard JavaScript key-value object, then you should stringify it, i.e. with JSON.stringify(value), so that it gets tracked as a proper string value.

The browser console shows JavaScript values in a human-readable friendly manner. Generally, if you're seeing your eVar18 value in a different font and/or colour than the other eVar values, then your browser console has purposely formatted it nicely for you to be able to read it. But the value is still an object.

1 reply

yuhuisg
Community Advisor
yuhuisgCommunity AdvisorAccepted solution
Community Advisor
August 5, 2022

Verify how you're setting eVar18 in your implementation. If the value that you're using is indeed a standard JavaScript key-value object, then you should stringify it, i.e. with JSON.stringify(value), so that it gets tracked as a proper string value.

The browser console shows JavaScript values in a human-readable friendly manner. Generally, if you're seeing your eVar18 value in a different font and/or colour than the other eVar values, then your browser console has purposely formatted it nicely for you to be able to read it. But the value is still an object.

    E
    earl5273Author
    Level 2
    August 12, 2022

    @yuhuisg 

    Sorry I have not yet been able to confirm your suggestion, the code is managed by our SaaS vendor and they have not yet updated the code with your solution.

    Terms & ConditionsAccessibility statement

    Loading footer...