What Are Report Suites

The fundamentals module covered what Adobe Analytics is. The more useful question here is what it actually does, and the answer is a single word: data. Adobe Analytics is not a video player, a spreadsheet, or a storefront. It is a machine for turning behavior into data, and data is only valuable once it is organized, stored, logically connected, and solid enough to carry real statistical analysis and produce trustworthy insights. The very first step in that direction is logical classification: deciding what data belongs together and what should be kept apart. The report suite is Adobe Analytics' answer to that classification problem.

A report suite is the concrete container your data lives in: the actual box that every hit lands in and is stored against. You can have one or many, and deciding how many, and where to draw the lines between them, is the central question of this entire module.

How many boxes do you need?

Picture an organization with more than one digital presence. A company operating across the globe might run a separate website for each country. An automobile manufacturer might have three business units, heavy vehicles, commercial vehicles, and consumer vehicles, each with its own site, plus a separate platform for spare parts and accessories. A B2B firm with only a handful of customers but high-stakes transactions might run both a web platform and a mobile app, two surfaces it needs to track distinctly. Every one of these raises the same question: should this data live together, or in its own container? That is the report-suite question, and it has no single right answer, only a right answer for your business.

A useful way to think about it: when you move house, you do not throw everything into one box. You separate the kitchen from the living room from the clothes from the crockery, and pack them into labeled boxes so you can find things later. Report suites are exactly that, boxes for your data, and you decide how to divide what goes where.

But here is where the analogy breaks, and the break is the single most important fact in this module. Moving boxes can be unpacked and their contents mixed back together, because it all belongs to one household, yours. Report-suite boxes are sealed. Once a hit lands in a suite, it stays there. You cannot pour data from one report suite into another, and you can never combine two suites' data in a single report. This is data isolation, and it is the line worth memorizing early because it shapes everything that follows: the boundary of a report suite is the boundary of every question you can ask. Draw the boundaries well and analysis is effortless. Draw them carelessly and you spend years unable to compare numbers that should have lived together.

Adobe does offer a couple of derived report-suite types that soften strict isolation, and it is worth knowing they exist before the sealed-box rule feels like a trap. A virtual report suite lets you carve a focused, segmented view out of a single suite, handy for giving a regional team just their slice of the data. But note the direction: it works within one suite, it does not stitch two suites together. A rollup report suite goes the other way and combines several suites, with an important catch.

The honest summary is that neither of these undoes isolation at the moment of collection. A virtual report suite gives you a segmented view of one suite; a rollup gives you an additive, undeduplicated total across several. The only way to get a single, genuinely deduplicated view across many properties is to collect them into one global suite from the start, which is the choice that global versus individual report suites weighs.

Every report suite the account can see

⤢

Two columns, and the left one is the part that does the work. Report Suite Id is the address your implementation actually sends to; Site Title is only what the interface shows you. They are set separately, nobody keeps them in step, and they drift apart in every account that has been running a few years, which is why "we send to the production suite" and "we send to Production" are not the same sentence and cannot be checked against each other.

What defines a report suite

• A unique RSID: every suite has a Report Suite ID (for example mycompanyglobal), the address your implementation sends data to, plus a friendly title you see in the interface. The RSID is the name on the envelope.
• Its own configuration: variables, processing rules, marketing channels, classifications, and settings such as internal URL filters all live per suite. Change one suite's settings and the others are untouched.
• Hard data isolation: two suites cannot be merged in a report. If you split data you later want to compare, no query brings it back together (the read-only workarounds above help in narrow ways, but they cannot undo a true split).
• A fixed time zone: each suite has one, and it defines when "a day" begins and ends for every time-based report. Choosing wrong skews every daily and hourly number you will ever pull.
• A single currency: revenue and currency metrics are normalized to the suite's configured currency.

// The RSID is what your implementation sends data to
s.account = "mycompanyglobal";   // a single report suite

// You can also send one hit to several suites at once
// (multi-suite tagging, covered later in this module)
s.account = "mycompanyglobal,mycompanyus,mycompanyuk";

Notice what comes first in that code: s.account. This is why the report suite sits at the center of data collection itself, not just storage. Every server call, the request that carries a hit to Adobe, names a report suite as its destination before anything else. The suite is the first thing every hit declares. You will see exactly how that request is built in the data collection module; for now the point is simply that the report suite is where data collection both begins and lands.

The rest of this module is really about drawing those boundaries well: how many suites and how to divide them (Global vs Individual Report Suites), how to get a focused view without re-collecting anything (Virtual Report Suites), the settings themselves (Report Suite Settings), and how to feed several suites from one implementation (Multi-Suite Tagging).