Adobe Analytics - Virtual report suites

Adobe Analytics virtual report suites segment our Adobe Analytics data so that we can control access to each segment. The virtual report suite inherits the data from the global report suite. For example, if we would like to manage the web and mobile Analytics data into a single report suite and all data are flowing into a global report suite, but to segregate those data further those data also flowing into smaller report suites. We set a variable to multiple report suites, and send their data to more than one report suite. This is referred to as multi suite tagging or base/parent report suites.

So, the purpose is to send the data to one report suite, which then is divided according to segments. And based on that segment we can control the access of Analytics data like what information should visible to a particular Analytics user.

Benefits of using Virtual report suites

1. Simplify implementation by allowing you to use a single Report Suite ID (RSID) across all sites/domains. Having all data in a single report suite enables customer analytics as we move toward the next generation of Adobe Analytics.
2. Business users in your organization always see only the data segments that are relevant to them.
3. Improve security by allowing Admin users to control data access more easily and more granularly after implementation.
4. Provide the ability to participate in Device Co-op
5. People metric
6. A single-customer view of data (in the future)
7. The ability to create unlimited virtual report suites to segment out data

Reference:

1. Adobe Experience League - Virtual report suite

Uncaught SyntaxError: Unexpected token const

const may already be written in your code which is not terminated. Please terminate that first using a semicolon(;) and then declare a const again.

OR

Use the same first const and for the second constant declaration simply write the constant name and assign value without using the const keyword.  

How dispatcher fulfill request?

When clients send HTTP requests to the web server, the URL of the requested page must be resolved to the content in the Dispatcher cache, and eventually to the content in the repository.

 

1. The domain name system discovers the IP address of the web server which is registered for the domain name in the HTTP request.
2. The HTTP request is sent to the web server.
3. The HTTP request is passed to Dispatcher.
4. Dispatcher determines whether the cached files are valid. If valid, the cached files are served to the client.
5. If cached files are not valid, Dispatcher requests newly-rendered pages from the AEM publish instance.

References

1. AEM dispatcher client request