A virtual report suite (VRS) is a report suite that is created by applying one or more segment definition to a report suite. This allows users to maintain their data in one report suite, but manage the data as if it was in separate report suites.
Apps that use VRSs do the same thing as apps that use a regular report suite, except for managing the following features:
These values are managed in the parent report suite and are shared with the VRSs that belong to the same parent report suite.
The following areas can be accessed in the Adobe Mobile Services UI independent of the parent report suite:
A VRS can help you complete the following tasks:
Restrict data access
A multi-national company has an app that sends data to a report suite for all geo locations. However, the company wants to restrict the business user in one region from viewing the data in another region. The company’s admin can create a VRS to segment users by region and give permission to the VRS only to the business user who manages the region.
This restriction prevents business users from viewing data that is not related to their region. For example, a business user in EMEA does not need to see data for the APAC region.
Allow the control of in-app/push messaging, location POIs, acquisition, and postbacks with all data being sent to one report suite.
A multi-national company wants all the data to be sent to the same report suite for all geo locations. However, the company wants the marketing team from each region to handle their own in-app/push messaging. The company’s admin can create regional VRSs, and each team can manage their own app based on that VRS.
The regional team builds their app by using the config file from the VRS. The data is sent to the parent report suite, but in-app/push messaging, location POIs, acquisition, and postbacks are controlled in the app that was created from the VRS.
Only Adobe Analytics admins can create and modify virtual report suites in Adobe Analytics. To create a virtual report suite, see Create virtual report suites in the Adobe Analytics documentation.
Each VRS has a unique ID. To view the parent report suite ID in Adobe Mobile Services UI, on the Manage App Settings page, in the App Information section, click More Details.
In the Adobe Mobile Services UI, you can use a VRS to create an app and segment data to a specific group in your organization. This way, for example, a business user in Spain cannot see the data that is relevant to a business user in Japan.
You cannot modify the values that are inherited from the parent report suite.
A VRS is a server-side segment definition that is attached to a parent report suite. As a result, you cannot perform data collection to a VRS, because the SDK sends hits only to the parent report suite, which in turn records the hits.
In Adobe Mobile Services, you can create an app based on a parent report suite or a virtual report suite. When creating an app based on a virtual report suite, we recommend that you align the VRS segment with the definition of the app.
Push certifications are attached at the app level in the Mobile Services UI.
To ensure that your push messages are sent correctly, the audience segment must be correctly defined. For more information, see Audience: Define and Configure Audience Segments for Push Messages.
The time zone property on the Manage App Settings page is different from the time zone property that you use to create the VRS in Adobe Analytics. The property on the Manage App Settings page is inherited from the parent report suite, which is used to send data to Adobe Analytics. The property that you specify when you create the VRS in Adobe Analytics is used to display the reports in the Mobile Services UI and might be different from the parent report suite.
To use a VRS when you create an app, select the VRS from the Report Suite drop-down list on the App Information page. This list contains parent and virtual reporting suites.
To select a VRS from the list, locate an option with the blue dot and the vrs_
<company_name>
_
<unique name>
naming convention.
Here are the properties for VRSs:
The read-only properties are inherited from the parent report suite.
Property | Inherited from the parent reporting suite | Editable? | Notes |
---|---|---|---|
target.clientCode |
No | Yes | |
target.timeout |
No | Yes | |
audienceManager.server |
No | Yes | |
audienceManager.analyticsForwardingEnabled |
Yes | Yes | |
audienceManager.timeout |
No | Yes | |
acquisition.server |
No | No | |
acquisition.appid |
No | No | |
analytics.rsids |
Yes | No | |
analytics.server |
No | No | |
analytics.ssl |
No | Yes | |
analytics.offlineEnabled |
Yes | ||
analytics.charset |
Yes | No | |
analytics.lifecycleTimeout |
No | Yes | Should be the parent reporting suite, if users do not want their data to be inconsistent. |
analytics.privacyDefault |
No | Yes | |
analytics.batchLimit |
No | Yes | |
analytics.timezone |
Yes | Yes, when you first create the app. | This time zone property is used to send data to Adobe Analytics and is different from the time zone property that is set when a VRS is created. |
analytics.timezoneOffset |
Yes | No | |
analytics.referrerTimeout |
No | Yes | |
analytics.backdateSessionInfo |
Yes | Yes |
Here is some additional information about virtual report suites: