How can I test: collectHighEntropyUserAgentHints

[tcrewes1]

Hello everyone, 

I hope you are well.

We looking to implement High Entropy User Agent Hints through App Measurement. We have added the variable to our App Measurement code as documented here: https://experienceleague.adobe.com/en/docs/analytics/implementation/vars/config-vars/collecthighentr...

My question is, is there a way to test this is working as expected before we deploy? I can't see any additional variables in the network request, but might be missing something. 

[Jennifer_Dungan]

Not all browsers are compatible with high entropy data, but those that do, you can use JS to get those values using your browser's console:

navigator.userAgentData
  .getHighEntropyValues([
    "architecture",
    "bitness",
    "formFactor",
    "fullVersionList",
    "model",
    "platformVersion",
    "uaFullVersion",
    "wow64"
  ])
  .then((values) => console.log(values));

For more information see: 
https://developer.mozilla.org/en-US/docs/Web/API/NavigatorUAData/getHighEntropyValues 

Since this is all processed based on the User Agent, you may not see anything in the server call... it may all be processed on the Adobe Server...

Sadly, as far as I am aware, the "Post Processed" Data on the Platform Debugger is still broken... so I don't know if you will be able to see the data as it is processed...

I am not sure if all this data will be available in Workspace either... It might be available in the Data Warehouse or Raw Data Feeds...

This is pretty new, and something I was actually just thinking of enabling myself... so if you find anything, I would love for you to share it back here, and I will do the same

[tcrewes1]

Thanks @Jennifer_Dungan , I had a feeling this might not be overly testable, but good to know we haven't missed anything obvious.

[Jennifer_Dungan]

It's pretty new... in fact, I didn't even see the documentation.. I came across the option by accident in Launch when I looking into something else I was working on...

But if this will help get more details to identify browser data, I am all for it...

One thing to keep in mind, since we are essentially at the mercy of Adobe anyway on how they determine the browser in use, I am not sure how much testing we need to do.. with so little control to begin with (I think making sure nothing breaks is the most important factor).

However, if you are like me, and you really like to dig into things... you could try capturing the User Agent and some the Client Hints into your own dimensions... then compare them to what Adobe is coming back with?