Multi-Suite Tagging

In Global vs Individual Report Suites, the hybrid strategy promised one implementation feeding both a global suite and individual team suites. Multi-suite tagging is the mechanism that delivers it: a single visitor interaction is duplicated and sent to several report suites at once, so the same page view lands in your global suite and your regional suite in one go. The idea surfaces wherever a global suite is weighed up, and again behind virtual report suites, so this section is less a new idea than the place it finally gets named.

More than a coding technique, this is an architectural decision, and you make it once, at setup. The question is simply how many real suites you collect into, and there are three common shapes.

Most teams land on the first shape. Multi-suite tagging is what you reach for when you genuinely need the third. Mechanically, in a library (AppMeasurement) implementation, you list the report suite IDs a hit should be sent to:

// Static: send every hit to all three suites
s.account = "globalrsid,regionrsid,brandrsid";

// Dynamic: decide the regional suite by context
var rsids = "globalrsid";
if (pageRegion === "us")      rsids += ",usrsid";
else if (pageRegion === "uk") rsids += ",ukrsid";
s.account = rsids;

In practice you will rarely type that by hand. In an Adobe Launch (Tags) implementation, which is almost certainly how you will deploy, you choose the destination suites in the interface: in the Adobe Analytics extension for a library setup, or on the datastream for a Web SDK setup. There is no page code to maintain. The full deployment story is the data collection module, so for now you can relax: the concept matters here, the clicking comes later.

The decision that saves you the most: multi-suite or a VRS?

This is where virtual report suites pay off. People reach for multi-suite tagging to give a regional team "their own data," and quietly triple their bill, when a virtual report suite would have done the job for free. The two solve different problems:

• Use a virtual report suite when you need a focused view of data that already lives in one suite. It is free, query-time, and adds no server calls. This covers most "give this team their slice" needs.
• Use multi-suite tagging only when you need genuinely separate suites: ones with their own settings, their own variable definitions, or that must serve as independent sources for Data Feeds or Data Warehouse, which a VRS cannot do.

The short rule: if you only need a different lens on the same data, that is a VRS. If you need a truly independent suite, that is multi-suite tagging, and you accept the per-call cost for it.

There is a second consequence of that independence, and it arrives as an argument rather than as a bug. Separate suites have separate settings, and eVar expiration and allocation are settings. So two suites receiving the identical hit, from the same tag, on the same page view, can report different numbers for the same question, because one suite credits the original value while the other credits the most recent, or one expires the eVar at the end of the visit while the other holds it for thirty days.