Best way to tag every clickable element on the page (retail site) | Community
Skip to main content
Level 2
July 31, 2024
Question

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

  • July 31, 2024
  • 3 replies
  • 3795 views

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!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 1, 2024

I agree, that doesn't sound efficient... also, what happens as users mis-click, go back and change options, etc before continuing to the next step... that would be a lot of useless "dither" values that didn't account for anything.

 

There is no "one size fits all" solution, but for me, when the user chooses to continue, I would bundle all the selected information onto the single "continue" action... this would give me their actual selections, on a single server call.

 

I would also create a relationship, using s.products, between the product page, add to cart, checkout, success, etc....

 

On the product page, I would track the key info that I need at that level... the product identifier is the "glue" that will hold together all the touchpoints.

 

On the product page, I might have a few merchandising eVars relevant to that product and page, and I might also set up a custom numerical event for "product page". (I say this because I might use "prodView for all views of the product from product page, to recommended content, to other people also bought, etc...)

 

Then, when the user "Adds to Cart", I would use s.products with the same product identifier, the scAdd event, and again relevant merchandising eVars....

 

The Cart view, which may have multiple products, I would track all the products with the appropriate identifiers, the scView, and again relevant merch eVars....

 

The checkout, again, all the products would be tracked with their identifiers and merch eVars, and the scCheckout event

 

And of course on success, I would have the product identifiers and merch eVars, the Orders metric, and also the quantity and price values from the purchase.

 

 

In my reporting, I would use the product identifiers as my breakdown, and have the relevant columns: Product Page, Add to Cart, Cart Views, Checkouts and Orders.... 

 

Those values you spoke of may be standalone values associated to the entire order (payment options, in store/delivery, etc), or specific to each product making them part of your merchandising eVar content per product....

 

I know this is a bit vague, it's hard to provide specifics without seeing your pages / flows.

Level 2
August 1, 2024

We do want separate evars, events so that we can get those variables for downstream reporting so activity map will not work. We also want to track every element to understand the user's engagement. Is there any example e-commerce retail site (based on app measurement implementation) that anyone can point me to see what is the best practice of tagging should be for product page > cart page > check out page? Thank you!

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 2, 2024

I am thinking of using two evars - 1/ delivery (values : pick up,ship) and 2/ payment method (values : card, other methods) and trigger success events when someone starts the delivery address, successfully completes and also another two events for payment initiation and payment success. Finally, 3/ order page. One event for successful order and another evar for all the order details. Is this the correct approach?


That sounds logical.. I know you can't share the website due to security, but it sounds like you have some good thoughts on the how to proceed.

 

It may take additional time, but sometimes playing with the flows and what is collected in a Dev/QA environment (even though its limited data), then trying to build a report can really help identify potential issues / scenarios you didn't anticipate, and it can spark new ideas of what to track...

In the long run, this approach can save you time and effort, because by the time it launches you already have a good sense of what you will get back.

BShan
Level 2
August 1, 2024

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
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 1, 2024

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.

Cheers from Switzerland!
Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 1, 2024

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
Community Advisor
Community Advisor
August 1, 2024

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.