


If you use Web SDK for tracking purposes, you'll find that it is very difficult to read the event data in the AEP Debugger browser extension. This is because, by default, the Debugger does not parse JSON strings. As a result, all of the Web SDK event data gets lumped up in one loooooooooong single string, making it difficult to validate the individual field values properly.
Even worse, because of this deficiency, the Excel download that the Debugger provides also suffers from very looooooooong JSON strings. And given how Excel formats cell sizes, the resulting spreadsheet can be very unwieldly to use! Contrast this with the Excel download that the Debugger provides for Analytics hits. Now, that download is much easier to open in Excel, and the individual data points, e.g. props, eVars, events, can be inspected more efficiently.
(Side note: I've already added an Idea to parse the JSON output for Excel downloads in the debugger. Please upvote/like it if you want to see this Debugger enhancement too.)
Until the Debugger improves how it displays JSON outputs, I've resorted to the following steps to be able to validate Web SDK hits when using the Excel download from the Debugger. I hope these steps are also useful for those of you who need to validate your Web SDK hits.
For step 8, I had used a 3rd party website, https://www.convertcsv.com/json-to-csv.htm, to convert the JSON values in the hits to a format that is easier to read in Excel:
] [
becomes
,
You can now inspect the Web SDK values more clearly.
Yuhui | yuhui.sg | Analytics, A/B Testing, Development since 2006
Topics help categorize Community content and increase your ability to discover relevant content.
Thanks @yuhuisg for sharing your workaround on debugging web sdk
Views
Replies
Total Likes
Pretty helpful! @yuhuisg Thanks.
Views
Replies
Total Likes