Need Consistent approach for tracking Action name on web interaction clicks

[Naveen_KumarPr]

Hi everyone,

our implementation - we are sending data to adobe analytics through AEP WEB SDK using DCR approach through EDGE network

Issue

As per the existing Implementation - we are tracking the CTA button names/text present on the U.I on the Web Interaction Link Click calls. However, on the Web Interaction Commerce events (Like add to cart, instant purchase etc) we are passing custom hard coded value as name of the CTA, which is polluting the data that is flowing to Adobe Analytics 

especially, we are not firing a seperate link click call on the click of CTA's like "Add to Cart", "Buy now" for which, we are firing only commerce typed web interaction call where we are passing custom hard coded names as "Action name" on these calls

When i checked with Developer to make the CTA name (Action name) tracking consistent on all web interaction calls, he mentioned he was having some technical challenges which I don't know/I'm not aware of

Currently, I proposed an alternative solution to Implement link click call on click of all CTA button's (no matter what), tracking the exact name/text of CTA's/Links 

& 

having a seperate web interaction call for e-commerce events 

this is adding up the calls, which the client doesn't like

can any one help me with any solution

Thanks & Regards,

[bjoern__koth]

Hi @Naveen_KumarPr 

Sometimes an additional call may help if that saves you a lot of customization on the development side.
It's not hard to give you a good recommendaiton without knowing your exact setup. But it really depends on the website and tools that are in use.

One question: if you are already on a product detail page, is there no information in your page's data layer that describes the product that is shown?

And, are you using a tag manager like Adobe Launch?

[Jennifer_Dungan]

Hmm yes, like @bjoern__koth I think we might need to understand more about your setup... while I understand the need to reduce server calls, my "best practice" is to try and match web and app as close as possible.

So, if there is a click action on web, the same flow should exist on the app. However, this is why I have reduced actual "click" / "action" calls in both web and app. Relying on Activity Map for context about what was clicked, and working with my developers to create a custom "Activity Map Replication" in our apps.

This way I have streamlined a lot of our tracking, while maintaining important flow information.

[Harveer_SinghGi1]

Hi @Naveen_KumarPr ,

I'd like to understand something related to your current solution, what you mean by "polluting the data that is flowing to Adobe Analytics"? Does this mean you don't want to see commerce CTA hard coded values in custom links report?

If that is the case, it's necessary for any tracking call sent to AA through AEP SDKs to have xdm.web.webInteraction.name, web.webInteraction.type, and web.webInteraction.URL fields populated (as per this documentation on Send data to Adobe Analytics using the Web SDK) to treat these calls as web interaction calls in AA, otherwise these calls will start appearing as page view calls which you don't want. So, as long as you need to send this data to AA I'd suggest to keep this implementation as it with maybe a slight change to xdm.web.webInteraction.name field where you could pass a concatenated string with information on type of link/CTA and it's name like "commerce click|add to cart" and "navigation click|contact us" etc. and use the link type categories to identify the relevant links for your reporting by either using them as it is or splitting into two reports with classification. This will hold true even if you decide to use two separate calls, the commerce call will still need the link related fields so you'd end up adding an additional call unnecessarily.

If you means something else by AA data pollution then please share some information on that so that this can be reviewed and answered accordingly.

Cheers!