Activity map details getting attached to Decisioning Proposition Fetch Server call instead of Page View Server call | Community
Skip to main content
A
AbhilashSh
Level 3
February 23, 2026
Solved

Activity map details getting attached to Decisioning Proposition Fetch Server call instead of Page View Server call

  • February 23, 2026
  • 1 reply
  • 41 views

Hi all,

I am using “Event grouping using session storage” feature to track activity map links in Adobe Analytics using Web SDK. (As shown below)

 

For my Adobe Target and Adobe Analytics setup, I am using 2 send events on every page load.

  1. eventType:- decisioning.propositionFetch and "renderDecisions": true
  2. eventType :- Web Webpagedetails Page Views and "personalization": {
        "defaultPersonalizationEnabled": false,
        "includeRenderedPropositions": true
      } so that the display event is sent for A4T purpose along with AdobeAnalytics variables (eVars, props and events).

Due to this behavior, Activity Map details are getting attached on decisioning.propositionFetch server call on the subsequent page and not available in Adobe Analytics reporting. 

Is there any way to make the Activity Map to attach on to subsequent page view server call? 

I don’t want to use “No event grouping” as it increases server call usage.

Thanks in advance!

Best answer by sreeCharan73

Hello ​@AbhilashSh 

Are you making use of Guided Events, where the propositionFetch events are to be marked for “Personalisation” and pageViews can then be marked as “Collect Analytics”, in this way, the propositionFetch calls to AT would never include the analytics details. Either way AT only needs the viewName for its rendering, which could be added in the PropositionFetch event.

1 reply

sreeCharan73
sreeCharan73Accepted solution
Level 3
March 11, 2026

Hello ​@AbhilashSh 

Are you making use of Guided Events, where the propositionFetch events are to be marked for “Personalisation” and pageViews can then be marked as “Collect Analytics”, in this way, the propositionFetch calls to AT would never include the analytics details. Either way AT only needs the viewName for its rendering, which could be added in the PropositionFetch event.

A
AbhilashShAuthor
Level 3
March 11, 2026

Hi ​@sreeCharan73 ,

Thanks for your response!

I was using a single rule in Adobe Launch (Based on Adobe Client Data Layer pageview event push) with two separate actions (decisioning.propositionFetch and Web Webpagedetails Page Views)

I also tried Guided Events with “Personalisation” and “Collect Analytics” method.

It seems like I was using web object (name, viewName) on both actions. Hence the Activity Map details were getting attached on decisioning.propositionFetch server call.

sreeCharan73
sreeCharan73
Level 3
March 11, 2026

Yes, if we use the same web object, it would result in similar behaviour. Hence I always a explicit mapping for the AT calls to send only viewName under the web object. If we do not map explicitly, the web object is included by default, as it is a mandatory field(object). In my experience, this trick always worked. Hope you find it suitable.

    Terms & ConditionsAccessibility statement

    Loading footer...