Button tracking using data layer manager

Question

Hi everybody!I´ve been setting up our buttons´ clicks using the data layer manager. Because our site is super simple, our dev created only event data layer and I configured each one (there are only 7) as a rule and its own event on the report suite. I've been testing on our dev environment and it seems we are getting the data. However, because I did that as an event, I have to select each event and use it on the metric field. (as bellow)

For our app we did both, set up as an event and also as a processing rule, this way I can see all the actions in a table.

How can I do that in this case? Would I also have to create a data element for it and also an evar?Thank you in advance

Pablo_Childe · Accepted Answer

You may also want to look at activity map tracking.

1 no extra dev work out of box

2 can allow you to do advanced mappings links/regions reporting

3 allows you to due near realtime (basic heatmaps) on page vis browser extension

Then just use custom links when coding/pae doesnt auto track activity map...

GLTU

Jennifer_Dungan · Answer

Adobe "click" actions have a default parameter called Link Name (it will show up in Workspace as "Custom Link")

In your app, your trackActions also pass a value that will populate this field (though it should be noted that the app will append "AMACTION:" to the beginning of the custom link value (there is nothing you can do to prevent this 😞 )

The Occurrences metric will trigger on all page views and actions automatically.. so if you have Custom Link set, you should be able to see it like your App table already, just use "Custom Link" as your breakdown and Occurrences as the metric (assuming of course that you set unique values for your Custom Links when you did your tracking)

However, if you have set up a custom eVar or Prop called "Action Name" you should be able to set this value in Adobe Launch on your clicks, or map it in with processing rules (it really comes down to personal preference).

You can set up any props, eVars, events, etc etc that you want on your button clicks/actions. Just like page views, you can populate any correlation values that you need to give your action insights.

You can use both solutions if you choose.. a custom event for each button, and the occurrences (just like you have for your app) there are many ways to accomplish this... but it's hard to rally give direct advice without seeing your implementation, but hopefully these tips help, and if you need more advice, please let me know.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded