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