Best way to tag every clickable element on the page (retail site)

[DebanjanaBh1]

What is the best practice to tag every clickable element on the page? Especially on the checkout page where there are payment options plus delivery information etc. Right now our site A triggers link call for every interaction by the customer. I dont think this is the best way. Is there any guide (example site for ecommerce) that we could refer to see how product page, cart page, check out page should be tagged? Many thanks!

[Jennifer_Dungan]

I really can't tell you that, I don't know what data is available or what is important to you and your business.

[BShan]

At a higher level, I'd also be asking whoever you're reporting to which are the metrics that matter to them in terms of business objectives and KPI targets, and tag those up first.

After that, it would be a case of looking at which elements are the most important in terms of understanding how users are using each stage of the checkout funnel, (do they get stuck entering their address, or is the add to cart page have too many options?) and then start to tag those to capture them as indicators of user behaviour.

The metrics that track user behaviour can then help explain the performance of the KPIs/ business critical numbers, and give avenues for optimisation

[bjoern__koth]

Well technically you could use ActivityMap to capture those link clicks automatically. What will be missing is any relation to actual products on the page. This will rather give you indication on where the users clicked on the page but not what happened after.

[Jennifer_Dungan]

It depends... if each link results in a new page being loaded, then yes, Activity Map will work, if they are trying to get form element interactions (which sounds like it based on the description), Activity Map will only potentially get the "submit"... and I'm not even sure about that, since I discovered that buttons are no longer working with Activity Map..... 

[Krishna_Musku]

I lean towards the activity map tracking to track almost everything. I didn't know that button tags are no longer working with Activity Map. I checked for the documentation and found this. https://experienceleague.adobe.com/en/docs/analytics/analyze/activity-map/faq  this is last updated on Jun 27, 2024.

Only the attribute type="button" is not working with Activity Map.

 

[Jennifer_Dungan]

Buttons never worked "out of the box", but I had code to modify the Activity Map link id, that I've used for over a decade, that recently broke... something changed on Adobe's end... I should need to force all the buttons to have an attribute of "button" or to force it to have a submit attribute for it to work.....