- Analytics Admin Guide
- Analytics Release Notes
- Analytics Admin overview
- System requirements
- Admin Tools
- Admin Tools
- Billing
- Bot removal
- Code Manager
- Conversion variables
- Currency codes
- Custom report descriptions
- Customize calendar
- Data Sources
- Default metrics
- Exclude by IP address
- Finding methods
- General Account settings
- Internal URL Filters
- Logs
- Marketing Channels
- Menu customizing
- Metric visibility
- App management
- Paid search detection
- Publishing lists
- Publishing Widget
- Preferences manager
- Privacy settings
- Privacy reporting
- Processing rules
- Processing rules overview
- Processing rules configuration
- Dimensions available to processing rules
- Processing rules examples
- Examples of processing rules
- Populate a campaign ID from a query string parameter
- Set the product view event from the product overview page
- Add a subcategory by concatenating the category and page name
- Determine a path by copying an eVar value to a prop
- Clean up values in a report
- Populate internal search terms using a query string parameter
- Copy a context data variable to an eVar
- Set an event using a context data variable
- Remove an event from a hit
- Processing rules tips and tricks
- Real-time reports
- Scheduled reports queue
- Server-side forwarding
- Simplified reports menu
- Social management
- Success events
- Timestamps optional
- Traffic variables
- Unique Visitor variable
- Video management
- Analytics in the Adobe Admin Console
- Company Settings
- Manage report suites
- User and Product Management (Legacy)
- Data Governance
- Adobe Analytics and GDPR
- Adobe Analytics and CCPA
- CNIL Consent Exemption
- Frequently asked questions
- Adobe Analytics Data Privacy workflow
- View/manage report suite’s Data Governance settings
- Label report suite data
- Submit access and delete requests
- Data Privacy labels for Analytics variables
- Namespaces
- ID expansion
- Labeling best practices
- Labeling example
- Data Privacy and Data Connectors (Genesis)
- Data Privacy terminology
- Privacy Reporting Variables
- Server Call Usage
- Traffic Management
- Admin API
Create a report suite
A report suite is a silo of data that Adobe Analytics uses to pull reports. An organization can have many report suites, each containing different data sets. While separate report suites were important in the past, having a single report suite has become more advantageous. The introduction of virtual report suites and report time processing allows admins to create your own subsets of data, allowing the flexibility to obtain both global and site-specific data.
This article is designed for system-level administrators or Adobe Analytics admins to prepare for data collection.
Prerequisites
Adobe Analytics First Admin Guide: Ensure that a system-level administrator has granted you access to Adobe Analytics via the Experience Cloud Admin Console.
Create a report suite
-
Click Analytics > Admin > Report Suites.
-
Click Create New > Report Suite.
-
Select either a predefined template or an existing report suite to use as a template.
NOTEOnly settings can be copied, not the data. If Customer Care is copying the settings over, you will need to provide a written confirmation to the disclaimer provided by Customer care about the risks involved. See Settings not copied from a source report suite for more information.
-
Fill in the fields described in New Report Suite.
-
Click Create Report Suite.
A report suite ID has a maximum length of 40 bytes. A report suite friendly name has a maximum length of 255 bytes.
Troubleshooting
After logging in to the Experience Cloud, the Analytics icon is greyed out.
This means that your account has not been granted the correct permissions to Analytics. Work with a system-level admin in your organization to ensure you belong to a profile with adequate permissions to access Adobe Analytics.
Next steps
Create an Adobe Analytics tag property: Create an area to manage your Analytics implementation.
Business.Adobe.com resources
Resources
Adobe Account
