Page View Display event for websd in SPA mode

HI ​@Kirill_Osokin 

Yes that’s correct. What exactly you’re looking for?  

Below document explain better 

https://experienceleague.adobe.com/en/docs/experience-platform/collection/use-cases/personalization/display-events#send-display-events-in-subsequent-sendevent-calls 

Please post if you still have queries. 

Thank you. 

Hi ​@Kirill_Osokin ,

The documentation example is intentionally minimal. The ... inside the xdm object is meant as a placeholder where implementers add their own XDM fields, such as page metadata (name, URL) and optionally an eventType.

For SPA implementations, what we send typically depends on the integration scenario:

Target-only (SPA view change):

alloy("sendEvent", {
  renderDecisions: true,
  xdm: {
    eventType: "view-change",   // optional, mainly for data semantics
    web: {
      webPageDetails: {
        viewName: "cart"
      }
    }
  }
});

Note: view-change is not a predefined event type, it can be passed just in case you want to filter these events in A4T later.

Analytics + Target (SPA page view + personalization): 

You can pass either web.webpagedetails.pageViews, in case this new view needs to be considered as a pageview in Adobe Analytics. Although, just passing name & URL is enough.

alloy("sendEvent", {
  renderDecisions: true,
  xdm: {
    eventType: "web.webpagedetails.pageViews",
    web: {
      webPageDetails: {
        name: "Cart",
        URL: "https://example.com/cart",
        viewName: "cart"
      }
    }
  }
});

• No default xdm.eventType is applied by Web SDK.
• If you want a specific semantic meaning in downstream data, it should be explicitly set in the payload.
• For Target SPA behavior specifically, the important field is web.webPageDetails.viewName, while eventType is optional unless needed for Analytics or data governance.

Thanks & Regards,
Vikas Ohlan
LinkedIn Profile