The Virtual Suite That Leaked Data
A media company has a single global report suite feeding three brands (News, Sports, Lifestyle) plus an internal "All Brands" dashboard. They create three Virtual Report Suites, one per brand, each with a segment restricting to that brand's content. The internal dashboard uses the global suite. A privacy incident occurs: a journalist's draft article URL was visible in the Sports virtual suite's Pages report for two days before takedown. The legal team asks how data reached a brand suite it should not have, and whether the global suite is also affected. Separately, users of the News virtual suite complain that their saved Workspace projects show different numbers than the global suite for the same date range.
1. How could the draft article appear in the Sports virtual suite, and is the global suite affected?
Read the worked answer
A Virtual Report Suite is a view, not a data store - it applies a segment (and optional component curation) to the parent suite's data. So the draft article appearing in the Sports VRS means either:
- The brand-restriction segment did not exclude it (the segment logic keyed on a content attribute that the draft page lacked or that matched Sports), or
- The page was tagged and sent to the global suite at all, and the VRS segment simply did not filter it.
The global suite is definitely affected - the hit exists in the parent suite, and anyone with global suite access could see it. The VRS did not "leak" data into itself; it failed to exclude data that was already in the parent. This is the critical governance point: VRS segmentation is a reporting convenience, not a security boundary. True restriction requires controlling access to the parent suite and/or excluding the data at collection.
Remediation: Remove the page from collection (or apply a processing rule / data exclusion), audit the VRS segment logic, and confirm who has global suite access. Do not rely on VRS segments for privacy.
2. Why do News VRS users see different numbers than the global suite, and how do you explain it correctly?
Read the worked answer
The News VRS applies a brand segment to every report, so its numbers are a subset of the global suite by design - they should not match. The likely sources of confusion:
- Segment scope and date-range interaction. The VRS segment may be Visitor- or Visit-scoped, so a visitor who touched News and Sports is counted in the News VRS but their Sports activity may also be attributed depending on scope. Check the segment's container.
- Component curation. If the VRS curates which dimensions/metrics are visible, users may be comparing a curated metric to the global equivalent and seeing different definitions.
- Processing order. Segments apply after data collection; the global suite includes all traffic, the VRS excludes non-News.
Explanation to give users: The VRS is the global data filtered to News content. Differences are expected and are not errors. If users need to reconcile, have them apply the identical segment to the global suite - the numbers should then match, which proves the VRS is behaving correctly. If they still differ, the curation or segment definition is the culprit.