Hello, to avoid generating lots of additional requests we've enabled eventGroupingEnabled in the clickCollection object, as per https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/commands/configure/clickcolle... - and as anticipated link tracking data (from when a user clicks on a link on the previous page) with is being combined with the page load event. See the attached XML!
However, we're finding that such requests end up being processed as hits classed as link clicks (page_event = 10 in the Adobe data feed). No pageview hits are generated. We're finding that we're massively undercounting pageviews on some pages which were reached through links.
Has anyone come across a similar issue? Is the expectation that requests that include both pageview and link parameters are processed as two separate hits?
Elsewhere in the documentation we're told that requests are either pageviews or links - there's nothing to suggest they can be both... very confusing!
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @andy121314
this feature should only populate the fields which would've classically been used by the Adobe Analytics Activity Map.
events[0].data.__adobe.analytics.contextData.a.activitymap.*
So basically this request is supposed to be treated as a link by design and is piggybacked on the page view call of the following page.
In other words, you are not reducing the overall billable server calls, you are just reducing the network requests and increasing click track quality which could have been impacted by cancelled link tracking calls on the previous page (upon link click with page navigation).
Here's a thread where we covered the topic
Views
Replies
Total Likes
Hi Bjoern, yes the intention is for link click parameters to piggy-back on the pageview request. However, we're not subsequently seeing two hits in the dataset - just one hit, for the link click!
Views
Replies
Total Likes