A company wants to track their website's usage without visitors seeing which data points are being collected. The following information must be tracked: • Page names • Form names • A counter event for each page of the checkout flow • s.products populated on each page of the checkout flow Which approach should the Architect recommend?

The core requirement is to prevent visitors from seeing the data collection calls. The Data Insertion API facilitates server-to-server data transmission. The company's web server would collect user interaction data and then send it directly to Adobe's collection servers via an API call. This process is entirely on the back-end, making the tracking request and its payload invisible to the client's browser. This method fully supports populating standard and custom variables like page names, events, and the products string, meeting all tracking requirements securely and discreetly.

A. VISTA rules process data after it has already been collected, typically via a client-side call that would be visible to the user.
B. Importing web server logs via Data Sources is typically for batched, historical data and is less suitable for real-time, interaction-based tracking.
C. A CNAME is a domain alias for the collection server; it does not hide the client-side tracking request or its contents from the browser.

1. Adobe Experience League. (2023). Data Insertion API Overview. Adobe Analytics Documentation. Retrieved from https://experienceleague.adobe.com/docs/analytics/import/c-data-insertion-api/c-overview.html. (States the API lets you "bypass client-side data collection" and send data "directly from your servers," confirming option D).

2. Adobe Experience League. (2023). Server-side implementation. Adobe Analytics Implementation Guide. Retrieved from https://experienceleague.adobe.com/docs/analytics/implementation/server-side/overview.html. (Contrasts client-side and server-side collection, highlighting that server-side methods like the Data Insertion API avoid browser visibility).

3. Adobe Experience League. (2023). CNAMEs and the Experience Cloud. Adobe Experience Cloud ID Service Documentation. Retrieved from https://experienceleague.adobe.com/docs/id-service/using/reference/cnames.html. (Explains CNAMEs are for creating a first-party collection endpoint, not for hiding the request, invalidating option C).