Compare data from 2 different Report Suites

[cvassant]

Hi Community !

Here is our situation : We will update our entire website really soon. Regarding Adobe Analytics, our new website will have a new tagging plan (with new evar/prop/events OR same variables but with a different name, for example our actual evar12 will now be evar48) and the data will be collected in a new Report Suite.

Here are my questions :

- How can we compare old data (the actual one) from Report Suite 1 to new data from Report Suite 2 within Adobe? Is there another way to do it, apart from comparing dashboards side by side in Analysis Workspace?

- If not, then we will need to export the data into a BI tool. How to avoid/resolve the de-duplication of visits & unique visitors?

Thanks a lot for your answers !!!

Best regards,

Cyril

- 

[yuhuisg · Accepted solution]

This might be better done with Report Builder. If you have a Windows computer with Microsoft Excel, get permission with your Adobe administrator to use the Report Builder add-on for Excel. This lets you build your own queries that pull data directly from AA into your Excel file. You can then run your report suite comparisons as you desire.

[jeff_bloomer]

This is definitely one of the more efficient ways to do it, AND if it's something you need to regularly share with the team, you can also set up scheduling right inside the Excel tool to deliver a PDF to their email, just like in Adobe Analytics.

[brentrad]

I had a similar situation last year in which there was a wholesale change in implementation. Ultimately, most of the comparisons had to be done outside of Adobe Analytics. The primary reason for this is that stakeholders didn't want to look at different dashboards or different panels within the same dashboards in order to draw conclusions. We export key data points from Adobe Analytics into a data mart, and were able to do some SQL magic to make our Tableau visualizations look continuous.

The best recommendation I can give about moving to a new implementation is to get stakeholders on board with any changes to how KPIs are defined as soon as you can. A site redesign may mean that website features associated with KPIs are completely different. For example, you may have a website feature that was condensed from multiple pages into a single page. This will mean that your old segments may no longer work, or your old definition of what constitutes a KPI (e.g. visitors does Thing A and then Thing B) may no longer exist.