In terms of code it would be quite heavy. I would advise you to explore other product that use heat map functionality. I believe some products already do that out of the box lke ContentSquare: https://contentsquare.com/platform/zone-based-heatmaps/

For the HIT all of the rules needs to be TRUE in the HIT itself. So only visits where ALL the rules are met in SAME HIT will be picked up. For the VISIT all the rules needs to be TRUE during the VISIT lifetime so one or more HIT can contain one or more rule to be TRUE. i.e : RULE 1 evar1 = 123AND RULE2 evar 2 =123ANDRULE 3 evar3 = 123 VISIT 1HIT1 evar1=234,evar2=123,evar3=123HIT2 evar1=aaa,evar2=aaa,evar3=aaaHIT3 evar1=123,evar2=aaa,evar3=aaa VISIT 2HIT1 evar1=123,evar2=123,evar3=123HIT2 evar1=a...

You might as well check other tools that provides you with a heat map view of your page like ContentSquare, it also allows you to do recording of users session so you can understand in depth how users use your site. Also it is better when you want to understand specific bug as you can see in recordings how your site behaves. Another approach is to ask your developers to update the data layer with details about element interacted with. Nowadays website are created based around reusable components...

Please be aware that exposing the application version client side in any shape or form can create security issues. As long as the user knows which version is deployed then can exploit an existing bug if found.

If data is sent to the report suite and is partially recorded then you can check the following:In the admin section under report suite, select your production report suite and check if eVars and props are configured correctly and enabled.If they are configured correctly then there might be some additional processing that overwrites your values.Check the processing rules and validate there is no overwrite of values.Extract data feed https://experienceleague.adobe.com/docs/analytics/export/analyti...

Get the URL of your adobe launch library and remove .min and reload. Now you can see in clear all data elements, extensions and rules configured in production. You can even use some custom code to parse the library to extract the details you need. Another way is to go to your developer tools and type _satellite._container You will see property rules which will tell you how many rules are configured and their details.The property dataElements will list all dataElements configured. (i.e: Object.ke...

Update comment as previous was not correct. So basically the issue is that when a web property is created with option "Configure for extension development (cannot be modified later)", it is not possible to copy some elements between non development web property and development properties.

Just use the steps to deploy code using JavaScript implementation as described here: https://experienceleague.adobe.com/docs/analytics/implementation/js/overview.html?lang=en You simply need to inject the AppMeasurement.js library and then instantiate Adobe Analytics. Also you will need to deploy Visitor ID services and instantiate it before Adobe Analytics. These steps are if you do not use AEP.

1. Check which adobe launch library is loaded in production. If you dev report suite is getting the data then either you did not configure correct report suite in adobe analytics extension or wrong environment is loaded in production for adobe launch. I believe if you type _satellite.environment you should see which environment is being loaded. Also check _satellite.property to make sure correct property is loaded. Finally check _satellite.buildInfo to check when the library was last build, shou...

The search features allows to some extend to do this. Best option and the fastest one if to load the library in the browser without the .min and either use the browser search functionality to look for data element or copy the content of the library and do a search in your code editor