Which method is recommended for tracking user interactions in a Single Page Application (SPA) using Adobe Launch?

Single Page Applications (SPAs) dynamically rewrite content on the current page rather than loading new pages from the server. Therefore, traditional page-load-based tracking is ineffective. The recommended method is Event-Based Tracking, where developers push events to a data layer when a view changes or a significant user interaction occurs. Adobe Launch rules can then listen for these custom events to trigger tracking beacons (s.t() for page views, s.tl() for links), ensuring that navigation and interactions within the SPA are accurately captured.

A. Direct API Calls is too generic. While tracking involves sending data via an API (beacons), the recommended method for triggering these calls in an SPA is based on events.
C. Cookie-Based Identification is used to recognize and persist user identity across sessions, not to track real-time interactions or view changes within an SPA.
D. Browser Refresh Tracking is the opposite of what is needed for SPAs, as it relies on full page loads, which SPAs are designed to avoid.

1. Adobe Experience League. (n.d.). Implement Adobe Analytics on a single-page application (SPA). Adobe Analytics Implementation Guide. Retrieved from https://experienceleague.adobe.com/docs/analytics/implementation/spa-implementation.html?lang=en. (This guide explicitly states, "The most robust way to measure your SPA in Adobe Analytics is to use an event-driven data layer.")

2. Adobe Experience League. (n.d.). Adobe Analytics for Single-Page Applications (SPAs). Adobe Analytics documentation. Retrieved from https://experienceleague.adobe.com/docs/analytics-learn/tutorials/implementation/implementation-basics/adobe-analytics-for-single-page-applications-spas.html?lang=en. (This tutorial emphasizes using custom events to trigger s.t() and s.tl() calls for SPA view changes and actions.)