Replies: 3 comments 3 replies
-
I had your same problem with DA + RUM. With RUM, we can proxy their event functions down into the WC Shadow DOM. I'm not sure this is ideal for Milo / Commerce WCs, though. The perfect ideal would be to somehow reuse the data attribute patterns the martech team came up with (AKA DOM Tagging). Even if there's a re-implementation of those to bubble those up correctly. Their code is likely only looking at a typical dom and not shadow doms. Shadow doms are really brick walls for this type of stuff. You have to know what WCs you're looking for... and you cannot do wildcard element querySelectorAlls to find all WCs. So I look at this almost like fragment loading where we treat each WC as their own little island to instantiate. Here's what I would try: Ideal
Next ideal
Next ideal (but not great)
|
Beta Was this translation helpful? Give feedback.
-
thanks Chris! i'll go on that conversation once i got in touch with mentionned martech people :) |
Beta Was this translation helpful? Give feedback.
-
@npeltier Can you provide a sample page URL and specify exactly which links that are at issue. I'm unclear if the daa-ll values are not being added, or they ARE being added but there no analytics are being sent. |
Beta Was this translation helpful? Give feedback.
-
Hey! I have behavior from depth of a component’s shadow dom I would love to get tracked in analytics. Problem is clicks will just not bubble above the component level. First trial with decorating sub items (it's a menu) with daa-ll ended up in complete silence because of this.
I guess proper way would be to somehow dispatch an event from the component and register it in analytics but I’m not sure how to achieve the later
Beta Was this translation helpful? Give feedback.
All reactions