Which two actions can be taken to optimize an SDR for scalability?

A scalable Solution Design Reference (SDR) is built on principles of standardization and reusability. Using standardized variable names (e.g., eVar1 always represents 'Internal Search Term') across all report suites ensures consistency and simplifies management and analysis as the business grows. A modular event-tracking approach, where tracking logic is encapsulated in reusable components, allows for easy extension and maintenance. Instead of rewriting tracking code for similar events, a single module can be deployed, reducing complexity and potential for error when adding new features or websites.

B. Storing visitor data in the browser cache is not a standard SDR design practice for scalability; data is sent to Adobe collection servers.

D. While performance is important, minimizing API calls is a general web practice, not a specific strategy for designing a scalable SDR data structure.

1. Adobe Experience League. (2023). Create a Solution Design Reference (SDR). Adobe Analytics Implementation Guide. "A comprehensive and scalable implementation starts with the solution design. ... Keep variable use consistent across report suites."

2. Adobe Experience League. (2023). Implementation variables overview. Adobe Analytics Components guide. "Adobe highly recommends that you keep a Solution Design Reference (SDR) document to keep track of your organization's purpose for each variable." (This implies standardization is key).

3. Adobe Experience League. (2023). Getting started for developers. Adobe Analytics Implementation Guide. This guide emphasizes creating a flexible and scalable implementation, for which modularity and standardization are core software engineering principles.