Web SDK - Link-click interactions not being captured when using recommended event-grouping setting

[PeterNo8]

Hi. I'm dealing with conflicting information on how to include the `web.webInteraction` object to capture internal link clicks in page-view events using the Web SDK extension.

Details:

• In the extension config I've selected all internal link tracking options, as well as the "event grouping using session storage" option to group page views and link clicks as single events.
  
• The official documentation seems to suggest that this is all that's required for page-view events to include the `webInteraction` object alongside the other auto-collected objects under `web` (the latter of which are being successfully auto-captured under my current ruleset)
  
• However, I get conflicting messaging when exploring the "Update Variable" action in the UI. This seems to be telling me that `webInteraction` is NOT automatically mapped, and apparently needs explicit mapping logic instead?
   
  
  
• Under the current setup, `webInteraction` is not being included in the payload or resulting dataset rows:
  
  
  
  

• Using console logs I can confirm that the link-click variables are accessible via the "filter click properties" callback, but these are ultimately not making it to the sendEvent command:

  

   

Considering the issues, am I misinterpreting what the documentation is saying? Do I actually need to explicitly map `webInteraction` using Update Variable? Where & how should I be trying to pull these values from?

[bjoern__koth · Accepted solution]

Hi @PeterNo8 

yeah it's a bit special that one and the documentation not very clear what will release the information.

hope this thread helps, we discussed it a while back, including our own findings as well as support feedback.

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform/eventgroupingenabled-web-...

You will ultimately see it in the contextdata of the succeeding page view if all is properly set up.

 

[PeterNo8]

@bjoern__koth Thanks so much! Quite the rabbit hole but I managed to narrow down my particular issue from your thread posts. I just needed to explicitly map the page name and  view-count integer in the xdm object before sending the event.

In case anyone else stumbles on this thread and are using CJA rather than AA like myself: I wasn't sure if I'd need to do more manipulation to pull those values out of the returned contextData object, but it looks like they're auto-included under the right fields in the xdm object as well. Nice.

[bjoern__koth]

You're welcome, glad it worked for you!

Bear in mind that this approach will only store the last activity map interaction on the page before the navigation happened. If you have a website that opens/closes menus, scrolls up or down on mouse click, this may lead to lost calls.
as far as I know, right now, you cannot enable or disable this feature as needed through the activity map filter click callback or similar. Maybe in a future version