Google Sheets Bulk Component Manager for Adobe Analytics [Video]

Scroll all the way down if all you want to see is the Google Sheets Component Editor

Why you should probably use Virtual Report Suites

About three-and-a-years ago, Adobe Analytics introduced “Virtual Report Suites” (VRS). Especially if you are an organization that wants to onboard many end users to Analytics with as little friction as possible, Virtual Report Suites with enabled Component Curation are a must.

With default segments, your users never have to think about adding segments like “Exclude Bots” or “False Transactions removed” segments to their reports. You can change these segments or their definition anytime (e.g. when a new Bot is detected), and every VRS user benefits from it without doing anything. Because they are “simply” segments in the background, changes also work for past data (unlike filters in GA Views).
In Analysis Workspace, users see which components were “curated” for them in the current VRS.
You can drag components in and out of a a VRS and even rename them for just within this VRS.

“What should I use, and what means what?”

—> Component Curation to the rescue!

Component Curation is better and more end-user-friendly than any other admin feature that Adobe has ever released (e.g. tags, “approved” components, etc.). Users do not need to learn tagging conventions, nor do they need to know where to find the “approved” status and what that means. But more importantly, component curation is not a global “approved-or-not” dichotomy, it is relative to the context of the Virtual Report Suite: A Calculated Metric may be “working correctly” (“approved”), yet it makes sense only in the context of website A, but not B. So users of VRS A should find the Metric in A’s “curated components”, but not in B’s.

  1. Share all components that “work” and could be useful for anybody with “All Users” (so that people can use them if they know how to).
  2. Limit these shared components massively within each VRS via the aforementioned “Component Curation”. The guideline here is that only “report-ready” components should be part of the VRS (e.g. only the Calculated Metric for “Visits with Cart Views”, but not the underlying Segment “Cart View Hits”) — and of course, include only components that make sense in that VRS: If in doubt, leave out.
  3. Since all VRS components are still going to be a lot, I usually even add additional Workspace-specific component curation when e.g. a Template Workspace is done. It can be enabled in any Workspace under “Share” -> Curate Project Data”, and now your users see only the components under “Curated” that are actually used in this particular Workspace (you can add to them if you want them to see more).
  1. The default name of a component is not end-user friendly.
    Components are often worded very technically, e.g. they contain implementation-related terms like “Transaction ID (eVar78 - Merchandising)”. Your end users may instead understand “Order Number” better. And only yourself and some nerds will understand “Merchandising” or “eVar78”. But for the implementation dudes, it is important to know that this variable has to do with the Transaction ID variable, that it is merchandising-enabled, and that the eVar index is 78.
  2. You want to provide users a term in the company’s main language instead of English (which is usually the implementation language).
  3. You want to create components that mean different things in different VRS contexts, so you give them individual names. A typical case are suffixes like “(only on Redesign pages)” because the implementation for this component may still be incomplete within the scope of a VRS.

BUT: No Bulk Editing of Virtual Report Suites = Admin Hell!

That being said, there is one thing that Adobe has neglected: It is awesome for the end user IF a VRS is curated nicely and shows her just exactly what she needs in the language she understands. But all this curation work needed to make this happen is NOT awesome, because lazy me has to do all this, and that is tedious in the rather slow Admin interface. Just adding a couple of new components to a couple of Virtual Report Suites is a concentration nightmare because I have to go into each Suite and do the same thing again (and once in the third VRS, I ask myself “did I really add this one also in the first VRS?”, and back to square 1). Boooring, time-consuming, and a strain on my brain…

Adobe Analytics Component Editor for Google Sheets

So with this in mind, I thought I could try that thin ladder out of Admin hell as a motivation to finally learn how to do productive things with the Adobe Analytics API V2.0. That API, since this summer, officially supports Virtual Report Suite operations. The initial inspiration was a self-hacked Excel-based tool for global component editing by the aforementioned Professor/Hacker Boller. Senator Julien Piccini’s Python Wrapper for the API 2.0 plus Google Cloud (mostly Cloud Functions and PubSub, thanks @Yurii Serhiichuk for showing me around), Google Sheets and Google Apps Script helped as well.

Demo Video of the Adobe Analytics Bulk Component Editor for Google Sheets (sorry, I am not a video editor, I agree the quality should be improved).

What you can do with the Component Editor for Google Sheets

The Component Editor currently supports these functions:

  • Edit default name and description of multiple components at once
  • NEW: Filter components by how often and where they are used (see new article)
  • Add or remove multiple components from/to multiple Virtual Report Suites at once
  • Change the Curated Name for multiple components in multiple Virtual Report Suites at once
  • Delete many components at once
  • Pull in and view all components by VRS or a full list (all with the usual Google Sheets beauty, e.g. filter/sort/etc.)
  • Replace one or more components by another one (e.g. you want users to use Metric X instead of Y, so you can simply replace it automatically whereever it is used (Workspaces, Segments or Calculated Metrics).
  • Get an overview over all Workspaces by owner, modification date, number of actively scheduled jobs, etc. and delete workspaces in bulk
  • Changes to components are automatically saved in a change log tab.
  • Quickly find all components that have “Transaction ID” in them and make sure their Curated Name and Description mentions “Order Number” as well (which is what I have found users looking for usually)
  • Remove 180 components at once from a VRS that originally was created as a copy of another VRS, but had no use there (because they were related to functionality that only exists within the original VRS
  • Make sure everything with “First Time” or “First-Time”, “New” (e.g. Visits/Orders/Revenue) is coherently named “First-Time xy”. Likewise with Cart Additions (which were sometimes called “Add to Carts”, “Cart Adds” etc.). Likewise, make sure components that have to do with Orders have “Orders” in their (Curated) Names and not sometimes “Purchases” or “Bestellungen” (the German term).

How can I get it?

The Component Manager can now be licensed. Note that it is not a simple GoogleSheets Add-On (the power it needs surpasses Google AppsScript, so most of the stuff in the background runs securely on a server). But I can set up your own version of the Component Manager within just a couple of minutes, then share that sheet with you, and you are ready to go. Just go to the official website and request a demo & free trial.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Lukas Oldenburg

Lukas Oldenburg


Digital Analytics Expert. Owner of Creator of the Adobe Analytics Component Manager for Google Sheets: