Does every element on my web page need tagging? | Community
Skip to main content
February 28, 2025
Solved

Does every element on my web page need tagging?

  • February 28, 2025
  • 2 replies
  • 616 views

Let's say I have a webpage with 100 different buttons and I want to track if a user has clicked on these buttons.

 

With Adobe analytics, do I need to tag each of these buttons individually to ensure that the clicks are captured?

 

Or does Adobe have the ability to auto-identify clicks for all 100 buttons even without them being individually tagged?

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

Hi @emailmkarthik 

 

in general, no you don't need to tag every single button on your page. 

You have different options

 

1. Use a generic click rule in your tag manager that captures button clicks

and apply your business logic to map your tracking call's props and eVars.

(hint: have a look at this cheat sheet by Jim Gordon which logic I apply in the screenshot below)

 

2. you can enable Activity Map to automatically capture clicks "a bunch of UX elements" in the out of the box Activity Map dimensions and metrics in Analysis workspace.

(this is actually meant to populate click data for the Activity Map v3 browser extension but can be used in dashboarding as well)

I am deliberately saying "a bunch of UX elements", since they will need to match certain criteria (see screenshot).

https://experienceleague.adobe.com/en/docs/analytics/analyze/activity-map/faq

Once your markup matches these criterias, the functionality automatically captures link name, the region where it was in as well as the page name the element was on.

https://experienceleague.adobe.com/en/docs/analytics/analyze/activity-map/overview

 

You can also provide custom code that can rewrite / adjust these values as needed, to provide for instance a specific region name, should the given page markup not provide this information.

2 replies

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
February 28, 2025

Hi @emailmkarthik 

 

in general, no you don't need to tag every single button on your page. 

You have different options

 

1. Use a generic click rule in your tag manager that captures button clicks

and apply your business logic to map your tracking call's props and eVars.

(hint: have a look at this cheat sheet by Jim Gordon which logic I apply in the screenshot below)

 

2. you can enable Activity Map to automatically capture clicks "a bunch of UX elements" in the out of the box Activity Map dimensions and metrics in Analysis workspace.

(this is actually meant to populate click data for the Activity Map v3 browser extension but can be used in dashboarding as well)

I am deliberately saying "a bunch of UX elements", since they will need to match certain criteria (see screenshot).

https://experienceleague.adobe.com/en/docs/analytics/analyze/activity-map/faq

Once your markup matches these criterias, the functionality automatically captures link name, the region where it was in as well as the page name the element was on.

https://experienceleague.adobe.com/en/docs/analytics/analyze/activity-map/overview

 

You can also provide custom code that can rewrite / adjust these values as needed, to provide for instance a specific region name, should the given page markup not provide this information.

Cheers from Switzerland!
christel_guidon
Adobe Champion
Adobe Champion
February 28, 2025

Hello,

In addition to what Bjoern says below:

Tracking every single click (s.tl calls/click events) can lead to high costs. You may want to consider appending a parameter to your buttons instead. This could be used as a sort of 'internal campaign' parameter. This would be captured on the following page as part of that page load. 

This would keep your costs down, but also allow you to see traffic and conversions for each button click (like all your buy buttons for example). Even if several are used in a session, participation metrics could help you understand the influence of each. 

Just an extra note....

Thanks - Christel

March 10, 2025

Thanks Christel and Bjoern,

If Adobe autocaptures events, I am not sure what the difference that PostHog mentions here.