@bjoern__koth  I have a problem with the eventGroupingEnabled set up. The very first request is adobe target's eventType: "decisioning.propositionFetch", which unfortunately needs to have the web.webPageDetails.name set (otherwise, we can't run AT experiments on specific pages). The unfortunately bi...

@WestonNorwood the server call limit (and the impact) is an interesting question. Don't have a valuable insight on this front unfortunately (our set up is not in prod yet), but my gut feeling suggests that the impact will be substantial. Something, what needs to be discussed with adobe directly perh...

@bjoern__koth Re: "Also be aware that the XDM eventType must be the standard "Web Webpagedetails Page Views" and any other event types will not pull the sessionStorage in."That's not great as we will need separate events for pageLoads and everything else. Essentially, we will be replicating the "old...

@bjoern__koth Okay, makes sense. You just want to make sure that obj property exists and setting it to an empty obj if its not. Thought about something completely different, but thanks for explaining. 

@bjoern__koth  qq - you are setting an empty object as a fallback in the custom code. Below is the example.  content.__adobe.analytics.contextData = content.__adobe.analytics.contextData || {}; I normally set an empty string "", which prevents variable(s) from being populated. Just trying to...

@bjoern__koth  I have got the same reply from adobe engineer. My key findings:1. web.webPageDetails.name needs to be populated on the subsequent page load in order for the event grouping to work. I have started to populate this property on all events.2. Anchor tags will be triggered as stand alone e...

@bjoern__koth  thanks for the above - definitely a valid back up option. I have raised a ticket with adobe customer support and their engineers are looking into it. Would really prefer for this to work out of the box, but its good to have a back up option Weirdly enough, on my end, out of the box so...

@bjoern__koth  a bit of a tricky one. I will raise a ticket with Adobe - this is what our customer support has suggested.  In the current setup (without event grouping), the activity map is not amazing. It will results in an enormous amount of extra requests. Any nav link, toolbar, tab will result i...

Thanks for the update, much appreciated.

hi all, based on the adobe documentation clickCollection.eventGroupingEnabled is a boolean that determines if the library waits until the next page to send link tracking data (clickCollection | Adobe Data Collection). Have tried setting it to "true" and the event bundling does not work. The existing...