Adobe Analytics dashboards Scorecard Builder

Transcript

Hi, this is Ashok Gorrepati, Product Manager, Adobe Analytics. In this video, I’m going to walk you through how you would create and share a mobile app scorecard. For context, scorecards are the new project type we’ve introduced in Analysis Workspace. Exclusively intended for the brand new Adobe Analytics dashboards app. The app is intended to lend execs and business users within your company, anytime, anywhere access to insights from Adobe Analytics. Before you or users within your company can start using the dashboards app, you will need to create and share these score cards with them. To create the scorecard, I begin with the new project creation workflow. You will notice a new template called Blank Mobile Scorecard. I select this new template and I’m taken to the mobile app canvas where I would start building my scorecard. The canvas is intended to ensure that the creators of this scorecards can work with a representation of what the execs can expect on their app. Another thing worth highlighting is the fact that we wanted the creation experience to be as simple, if not simpler than the consumption experience. I first select the report suite that the scorecard should be based on, just like I would in Workspace, I can see that the options in the left rail are updated based on my report suite selection. I will then select the default primary and comparison date ranges. What I’m doing here is choosing the primary and comparison date ranges that the scorecard should default to, when it is first opened in the app. That said, users will have the option to choose from other date range presets within the app. I’m going to choose this quarter for my primary range, and last quarter for my comparison rates.

Since a scorecard is a collection of key metrics that I know relevant to the intended recipient. I first drag and drop some high level metrics by way of tiles on the scorecard.

Each tile displays the key metric, and the percentage difference the metric has witnessed, related to the comparison date ranges. I’ll start with a few engagement metrics like page views, unique visitors, and the visits we’ve had from these visitors. I can also add some conversion metrics, like total orders, total revenue, and the orders we’ve had per visitor.

These are key metrics I think would be meaningful and interesting to the exec I intend to share the scorecard with. Now that I’ve curated key metrics onto the scorecard. What I do next is build a drill in view for each of these metrics. The drill in view is what the users of the dashboards app would see if they were to click into the key metric on the app for additional context. For instance, the exec might want to know which products led to the most orders, or which referring domain has been most successful in shepherding users along their conversion path, or maybe how orders has spread across all the countries that you operate in. I can drag dimensions that would land this context on to the key metrics, and that would feed the drill in view. Again, the second half of the canvas is an approximation of what the experience would be if somebody were to drill into the metric on their device. I can search for the dimensions I want in the left rail. I’ll start with the referring domain. Drag that onto the key metric. And what that does is feed that drill in view. I’ll look for other dimensions that could add additional context like product, and countries.

Note that I can also search for and add these dimensions from within the right rail. The tile you’re adding the dimension to is highlighted in blue. And the properties that appear in the right rail are properties that you’ve defined for this one tile. Just like I’ve added dimensions to the tile, I can also add segments to this scorecard, both at this scorecard level, in which case they would apply to all tiles within this scorecard or at the tile level, in which case, they would only apply to that specific metric. Say I wanted to apply a segment to the Unique Visitor metric. Say, I’m only looking at desktop users, I can look for the segment and drag and drop that metric onto the tile. And it would instantly update. Segments can also be applied at the scorecard level. In both cases, segments applied at the tile or the scorecard levels would not be visible to the end user. That said, if you did want segments to be visible to the user of the app, and even have them choose from a list of segments for different views of the same scorecard, you can curate segments into a segment filter. Say, I wanted the recipient of the scorecard to choose from a list of our most important segments. I can look for those segments in the left rail and drag them onto the segment filter, and start building my drop down filter. I’ll add two more of my important segments.

What I’m doing here is populating the drop down filter, so the recipient of the scorecard can cycle through these segments and re-animate the scorecard based on their selection.

If I wanted, say Diamond Customers to be at the top of the list, I can first disable the no filter option before dragging Diamond Customers to the top of the list. Say I wanted to rename how the segments appeared in the list. I can do that by selecting the segment filter, again highlighted in blue, and renaming the segments. I’m going to rename Diamond Customers to say, Diamond Users. Now that I have renamed the segment, the new name is what appears within the scorecard in the drop down filter. Note that the renaming only applies to the scorecard, without affecting what these components would show up as elsewhere in the solution. You can also rename the metrics you have curated onto the tiles, and even dimensions that you’ve layered onto each tile. Now that I’ve created my scorecard, what’s left is for me to share the scorecard with the intended users of the app. Before I do that, I will save this scorecard by either choosing Ctrl + S, give the scorecard a title.

I can also add a description explaining what the scorecard is, and the description would show up in the app when the scorecard is shared with the recipient. Now that I’ve saved my scorecard, I can share it with anyone within my Analytics login company slash product context with valid Analytics credentials. So if the exec you are hoping to share this scorecard with doesn’t already have an Analytics account, make sure that you create their account in the admin console and inform them of their login credentials before you share the scorecards with them. So I can look for any user that has access to my Analytics solution or product context and share the scorecard with them. Just to be safe, I would also ensure that the shared embedded components within the shared model is also selected, just so these users can view the scorecard without you having to do anything additional by way of assigning permissions or entitling them to product profiles. That’s it. I hope the video was useful and would help get you started on creating and distributing these scorecards across your company. Thank you. -