Web SDK decisioning.propositionFetch Causing CJA Session Starts and Marketing Channel Mismatch
Hey there!
After implementing the Web SDK guided events, CJA reporting and setup are impacted by decisioning.propositionFetch events. We currently have to exclude this event type via segments to align CJA with AA, but doing so breaks Session Starts and our Internal Domains logic.
Impact in CJA (we are using raw AEP data, no Adobe Analytics Source Connector):
-
Sessions / Page Views / Session Starts
-
With an event-level exclusion segment (eventType = decisioning.propositionFetch):
-
Sessions ≈ AA Visits
-
Page Views ≈ AA Page Views
-
Session Starts much lower than AA Entries
-
-
Without the exclusion segment:
-
Sessions and Session Starts are higher than AA
-
Page Views still align with AA
-
At a dimension level (e.g., Canonical URL, Marketing Channel), we sometimes see Sessions > Page Views, which should not occur
-
-
Root cause: decisioning.propositionFetch fires first, so CJA treats it as the session-start event. Excluding it via segment removes most “first hits,” so Session Starts collapse.
-
-
Internal Domains (Marketing Channel)
-
Internal Domains in CJA is defined as:
-
Session Starts is set (to mimic AA “Is First Page of Visit”), AND
-
Web Referrer URL in a list of internal domains (e.g., www.mywebsite.com, etc.)
-
-
With the exclusion segment:
-
Overall Session Starts and Internal Domains metrics are much lower than AA.
-
-
Without the exclusion segment:
-
Total Sessions/Session Starts are higher than AA, and Internal Domains Page Views are extremely low vs. Sessions/Session Starts, indicating non-pageview events are acting as session starters.
-
-
What’s the recommended setup approach to achieve CJA parity with Adobe Analytics for Visits/Entries and Internal Domains—without relying on exclusion segments that remove most first hits? Or should we avoid exclusion segments altogether and accept expected variance between platforms?
Thank you!
Leyla