Review Across Report Suites to Ensure Optimal AA Performance

[#1]

Governance

Component	Where to Find	Reason for Revision
System Admins	Navigate to Admin Console > Users > Administrators.	Identify the number of System Admins for your organization. It is not recommended is to have more than 4-5 system admins.
Product Profiles with Zero Users/Permissions	Navigate to Admin Console > Products > Analytics > Product Profiles > Permissions.	Identify the user profiles that do not contain any permissions or profiles that do not include any users. Remove these user profiles.
Data Governance Settings	Navigate to Analytics > Admin > Data Governance.	Identify if the implementation includes labels across AA data. If not, consider adding these labels to help your AA users more efficiently identify the components they need for reporting.
Segment Sharing Permissions	Navigate to Adobe Analytics > Admin Console.	Identify if Segment Sharing permissions are enabled for all AA users. As there is a limit on number of segments that can be shared to the Experience Cloud, permission should not be given to every user, otherwise there is the risk that the segment sharing will reach its capacity.
Inactive Report Suites	Navigate to Analytics > Admin > Report Suites to view all configured Report Suites.	Identify which report suites are still visible in the AA UI but contain little to no data. It is suggested to hide report suites, as they cannot be deleted, from the UI if they are not used.

Performance

Component	Where to Find	Reason for Revision
Traffic Settings	Navigate to Analytics > Admin > Report Suites, pick the Global report suite (or most prevalent), then Edit Settings > Traffic Management > Permanent traffic.	Identify if permanent traffic is set. Check that the permanent traffic number matches the number of server calls that your organization currently has configured for the selected report suite. You can change expected traffic levels so Adobe can reassign resources to handle the new traffic level. Otherwise, you can schedule a traffic spike if you want to temporarily reassign resources.
Data Feeds	Navigate to Analytics > Admin > Data Feeds and see if there is more than one feed set up for each report suite.	Identify the number of data feeds configured. It is not advised to have more than one feed per report suite, as all data should be sent into a single location and then dispersed internally.

Settings

Component	Where to Find	Reason for Revision
Internal URL Filters	Navigate to Analytics > Admin > Report Suites, pick the Global report suite (or most prevalent), then Edit Settings >General > Internal URL filters.	Excessive filters may skew data if they are not necessary/ appropriate. Check if your implementation has set internal URLs that should not be classified as external traffic.
Marketing Channels	Navigate to Analytics > Admin > Report Suites, pick the Global report suite (or most prevalent), then Edit Settings >Marketing Channels >Marketing Channels Processing Rules.	Order/hierarchy is crucial for Marketing Channels. Make sure your channels follow a logical and appropriate order. See more information on Marketing Channels order here.
Privacy Reporting	Navigate to Analytics > Admin > Report Suites, pick the Global report suite (or most prevalent), then Edit Settings >Privacy Management > Privacy Reporting.	Check if the implementation is leveraging consent managers and/or the Privacy API. Enabling these OOTB variables will help to identify the number of users that are opting out of data collection, which may be valuable in your reporting.
Bot Rules	Navigate to Analytics > Admin > Report Suites, pick the Global report suite (or most prevalent), then Edit Settings >General > Bot Rules.	At a minimum, the IAB bot filtering rules should be enabled. Selecting Enable IAB Bot Filtering Rules uses the IAB’s (International Advertising Bureau’s) International Spiders & Bots List to remove bot traffic.

Implementation Strategy

Component	Where to Find	Reason for Revision
Variable Descriptions	Navigate to Analytics > Admin > Report Suites, pick the Global report suite (or most prevalent), then Edit Settings > Conversion > Conversion variables.	Identify if variable descriptions are included across description fields for conversion variables (eVars), traffic variables (props), and events to ensure AA users are leveraging the appropriate variables for reporting.
Multi-suite Tagging	Navigate to Analytics > Admin > Server call usage > Report Suite Usage.	Identify if your organization has any secondary server call volume. Since the inception of Virtual Report Suites, SSCs are not needed for most use cases.
Library Version	Leverage the Experience Cloud Debugger to check the appMeasurement version in use.	Identify the implementation’s appMeasurement version and check if there is a newer version available. If there is a newer version, you may want to consider upgrading.

[#2]

This is really helpful! Thanks for this.

[#3]

I agree - very helpful! Thanks!