Learn Track - Getting Started

Transcript

Hello everybody, welcome to the Skill Exchange. This is Ashok Gaurabadi, I’m a Senior PM for Adobe Analytics, here to lend you a brief introduction to Adobe Analytics and Analysis Workspace. This track is intended for people just starting out on their exciting Adobe Analytics journey, and by the end of the session, you will have familiarized yourself with the Analytics user interface. In this series, you’ll be able to start creating your first Analysis Workspace project, and you will learn more about the different building blocks like data tables, visualizations, and panels that will help you translate data into meaningful insights. This is the Getting Started segment of the track, and my colleagues Maria and Jennifer are waiting in the wings to continue your learning path with the Analyzing the Data and the Putting it All Together segments in due course. So let’s get started, shall we? The goals of the session are simple. It’s intended to kickstart your learning path in Analytics. We will have barely scratched the surface of everything you can do in Analysis Workspace, but you will be armed and ready to rumble by the time you’re done exploring some of the fundamental aspects and concepts of Workspace. We won’t really delve into advanced topics like implementation, or APIs, or processing rules and such, since the good news is that those concepts can totally wait until you get a hang of the reporting interface and are hungry to learn more and be the analytics expert at your company. If you are somebody that has never used Adobe Analytics and are looking to get started, then that’s absolutely perfect, because this right here is square one and the start of a hopefully fruitful, data-driven journey as you discover the sheer power and flexibility that Workspace has to offer to make data bend to your will.

So yeah, what is Analytics? It’s obviously more than a fleeting business buzzword. In this day and age of hyper-personalization and consumer and customer choice, Analytics is a table stakes prerequisite for improving customer experiences. You can only, obviously, improve what you can measure, and Analytics is the arsenal that lets you track customer behavior and activity across touchpoints in order to both improve their experience as well as influence the business outcomes you’re after. Data and insights are the lifeblood of business intelligence, and it’s this intelligence that can help you analyze user activity right down to the granularity you seek. You can learn from your past efforts, so you can tweak your optimization strategies or channel your advertising spend to avenues that offer the most promise. Analytics is also central to efforts that are squarely aimed at customer conversion and retention, and definitely an input to your efforts to engage and delight your customers. So yeah, in a nutshell, Analytics is what separates those businesses that play from those that actually win. So yeah, before we get to Adobe Analytics and Analysis Workspace, it’s essential that we get super comfortable with some of the basic reporting terms that are fundamental to being able to use and make sense of data in Adobe Analytics. Everything you do in Workspace will rely on a combination of one or more of these building blocks or components as they’re referred to in Workspace land. The first would be metrics. They are simply quantitative measures of your user or customer activity. This is the component that helps you answer the how many question. Like for instance, how many page views or purchases or cart editions do you have? These are often counters that get incremented every time a specific activity is performed on one of your digital properties. You can use metrics to quantify something, like how many mobile users from the UK did we have in the second quarter. You can use them to compare two different datasets, like how did purchases on the mobile app compare to purchases on the website last week. You can also use metrics to do historical comparisons, like for instance, answer questions like was there an uptick in revenue after we revamped our lifestyle section of the site? The second of your data building blocks is what we call dimensions. These are non-numeric descriptors you can use to slice and dice your way through your data. This is the component that helps you answer the who, the what, and the which types of questions. Like for instance, which pages contributed the most to your page views for the month of August? Some typical dimensions include page names, products, marketing channels, campaigns, and so on. The third component that rounds out the trio of fundamental components are segments. These are powerful components in that they can help you apply a custom lens to your data. You can segment your data to get to a subset of visitors or visitor behavior on your site that meet a set of rules or criteria that you define. Segments are incredibly useful and they help you answer such questions as did visitors from California submit more orders in the month of June than those from Texas? In fact, any example I can come up with will fall short of the sheer flexibility that segments offer you and if you have mastered segments, trust me, you are well on your way to being an analytics expert.

So you probably noticed how I made a distinction between Adobe Analytics and Analysis Workspace and this is why. Adobe Analytics is the collective term for a bunch of tools that help you collect, process, analyze and share data, whereas Workspace is the interface where you would spend most of your time if you are analyzing data. On the data collection side, you may eventually start getting familiar with launch, which is how you get tags on your properties and start sending in data in a format that is tailored for your business. You may also start using Adobe data connectors or data insertion APIs to send in data to be collected and analyzed in Workspace.

Apart from Workspace, there are a couple of ways for you to interact with our data. One of them is the Reports tool, which is a separate section within Analytics, but will be folded into the Analysis Workspace section as part of a transition that will take effect next year. Then by way of methods you can use to export data, you have Report Builder, which is our popular Excel plugin that will let you create and update reports directly in your spreadsheets. There’s also some advanced data export tools like Data Warehouse and Data Feeds that will let you get data out and into other tools like Power BI and so on. You don’t have to worry about any of those other tools or methods for the duration of the session since we are going to focus exclusively on Analysis Workspace. So getting to Analytics and Analysis Workspace, you will log in via the Experience Cloud. You will need to have your admin create an account for you. You can either log in using your username and password or if your Analytics instance is set up for SSO, then it’s as easy as logging into your SSO provider. You will need to create your own password in this case.

Once you log in, you will land on the Experience Cloud homepage from where you can navigate to the Analytics instance and then Analysis Workspace. Workspace is an incredibly powerful, suitably flexible data analysis and report creation engine. If you can pardon my immodesty, it is one of the best tools out there for crunching through unimaginable volumes of data without breaking a sweat or breaking out your SQL or Python skills. It is a combination of multiple features and options like freeform tables, cohort analysis, attribution modeling and navigation padding that you can use to both make sense of your data as well as distill your understanding into insights that can then be easily distributed across your org. There is no sampling in that your big picture analysis is based on the full story and it’s all hosted on the web, so you don’t have to run pesky local editions of the tool. It may take a minute for you to get familiar with the feature-rich interface and get a handle on all the questions Workspace can help you answer, but once you do it, it will become, I promise you, as second nature as any other productivity or communication tool you use in the course of your day. As you get started in Workspace, you can begin with reports, which are pre-built instances of projects fueled by out-of-the-box components. Reports are a quick and easy way for you to get instantaneous value out of Workspace. You have a selection of multiple reports categorized under the engagement, conversion, audience and acquisition buckets. These are similar in spirit to the reports you get to see in something like Google Analytics, if that’s what you’re transitioning from. Once you get a hang of reporting that’s available in Analytics throughout this section, you can then move on to projects, which would allow you to build your own data tables and add visualizations to answer your own business questions.

First things first, like I said before, reports used to be a separate section within Analytics, but are now being folded into Workspace. To get to the version of Workspace that will be accessible to all our users starting December, I’d recommend that you turn on the new landing page option to get a head start on projects. That way you’ll be working off of the eventual incarnation of Workspace right off the bat.

This is what the Workspace landing page looks like. We are constantly at work trying to make this as useful, personalized and delightful as possible, so look out for incremental improvements to this page as you start using it. Like I said, this is how you’d get to those pre-built reports with out-of-the-box components. If you want to get familiar with Workspace and everything it has to offer, you can access the Learning section that would link you to a ton of videos to guide you through various features, functions and use cases that Workspace has to offer. The Learning section is an incredibly handy source for Workspace training you can get through at your own pace.

The landing page will display a bunch of projects that you created, or those that were created by other users at your company and were then shared with you. Depending on your permissions, you can create a project and share it with everyone at your company, in which case it’ll show up in this list for every user. You can search for projects by name, or use filters to hone in on a collection of projects that meet a certain criteria. You can start a project so it appears under your favorites, you can delete, share or rename a project from right within the dashboard. You can also create a copy without ever opening the original version, and then work off the copy if you do not want to make changes to the underlying project. You can also pin projects so they appear at the top of the table always. If the columns in the dashboard aren’t doing it for you, you can customize it so the table only includes those columns and labels that make sense to you. Like I said earlier, the Reports section is a really handy shortcut to actual reporting and analytics. You can quickly load up these reports for a seamless introduction to analytics, even as you’re getting a hang of workspace. There’s also a training tutorial you can access that’s really nifty. You can use the tutorial that includes simple step-by-step instructions on using and understanding data, adding visualizations and building your first project. I’d highly recommend that you start with Reports and then move on to the training tutorial and follow along to build your very first reporting instance. I know we took the scenic route to get here, but finally, here’s how you’d create a project. No surprises, obviously, you’d click the Create Project option from within the landing page. You can also create a project intended for the Adobe Analytics mobile app that offers an experience that is tailored to business users and execs that need to consume insights off of a mobile app, but that can come later. Let’s dive in to see how you’d create a project to be consumed on the desktop. You’d click Create Project, select Workspace Project, and then the first thing you’d do is select a report suite. We’ll see what report suites are in a minute, but you’ll select one and that’s it. You can start dragging and dropping components onto their rightful places and sections in the project and you’re well underway.

Just a quick detour to learn more about report suites. Think of report suites as the equivalent to a view in Google Analytics, for those of you familiar with GA. It is, at its most fundamental, a collection of data you can use to build your workspace projects. When you tag your sites or apps or send data in via the data insertion APIs, you will direct all of that data to a report suite and that is what you will use to build a project. Report suites are typically set up and configured during the implementation phase. For those of you that are going to operate at the business end of the tool, you do not need to worry too much about them, except to the extent that you need to know which reports to use and also to begin your analysis by first selecting the right report suite.

Once you’ve selected a report suite, you can dive right into creating your workspace project. You can absolutely trial and error your way to populating data tables and connecting visualizations and adding commentary and so on. You can spend just a little while on the learning tab we were looking at earlier to get a hang of the features, options and ideal navigation techniques to make the most of workspace. Like I said, Workspace is a bit of a blank canvas, so you can totally paint your data masterpiece as long as you get used to some of its whims and quirks. This is a snapshot of the menu options you’d find within the project, which I’m sure you’ll quickly get familiar with. Moving on, just like metrics, dimensions and segments are the three basic building blocks you would combine to answer a specific business question, panels, visualizations and components are the three basic building blocks you’d use to construct your project. You can think of panels as the pages within your project. These pages would in turn contain data tables that are made up of components and also visualizations that help illustrate or simplify the information that you’re trying to present to your viewers. Like they say, a great data wish is worth a thousand data rows.

Ah, wall of text. Sorry about that. But I just wanted to list all the different panels you can use to lend structure and definition to your project. Seven times out of ten, you’d be using a blank panel to add tables and visualizations.

But please don’t lose sight of some of the other panels that are available, especially the Quick Insights panel that is really popular with users just starting out on their workspace journey. Quick Insights, like some of the other panels listed here, has a really helpful fill in the blank structure you could use to query your data without having to contend with the ton of options that might be a bit confusing for the untrained eye. So step four, after you click through Create New Project, you select a report suite and choose a panel to structure your data, would be to choose your components. All the components contained in the report suites are listed along a left navigation pane within the project and are neatly divvied up across one of four categories. Dimensions, these are usually the rows in the data table. Metrics, these are usually the columns. And then segments and date ranges. Segments and date ranges are the lengths or the constraints you would apply to your table to lend more definition or get to a more or less granular view of your data. I’m sure you’d have a lot of fun dragging and dropping your way to glory.

Step five, after you click through from the landing page, select a report suite, choose a panel and add components in various combinations that make sense to you. All that’s left is to add a visualization or 10 to really make your data talk and tell a story. You have no shortage of WIS types to choose from. In fact, you can choose from 21 different visualization types on offer to you within Workspace. We do keep adding to the list so that the number is only going to get bigger, all in service of the storyteller in you. It might seem a bit expansive and open-ended at the beginning, but once you get a hang of it, Analysis Workspace can be just the tool you’re looking for to better understand and optimize your customer journeys.

Just a side note on the learning tab we were looking at earlier on the homepage. If you are somebody just starting out on your workspace journey, the learning tab is a nifty resource full of best practices and hard-won wisdom. These are bite-sized videos and user guides that you can keep coming back to as you get started, as you get going and get really good at making your data, do all the talking in Workspace.

Another great source of hands-on learning is the training tutorial. You can get to the tutorial project via both Workspace and the report section.

What it is, is a Workspace project that includes instructions on building your first analysis. It starts off with the very basics and by the end of the tutorial, you would have created a tutorial that includes freeform tables, visualizations, as well as slightly more advanced customer journey analysis tools like flow, fallout, and cohort analysis. We highly, highly recommend that you start your workspace journey by first test driving the tutorials project.

Let me leave you with a sneak peek of Analysis Workspace by giving you a quick demo.

This is how you would get into Adobe Analytics. On the experience cloud login page, you would insert your Adobe ID or log in via a single log in if your org is set up for it. You would enter your password and be taken to the experience cloud landing page. This right here is the experience cloud landing page and you would navigate to analytics from here. This is the workspace home page I was talking about and this is where you would come in and choose the new landing page options. So you’re presented with the experience that would be common across all our users starting December next year when we finally retire the reports section and fold that into workspace. This is the workspace landing page that lets you access all the projects that you have access to, the projects that you have created, the projects that have been shared with you. These are the reports and learning tabs that you can access to get to pre-canned reports under the report section as well as the learning tutorials and video guides to help you get started on workspace if you’re just getting started. Going back to projects, this is how you would create a workspace project. You would click on the blank project link and you’d be dropped on the blank canvas. This is the left nav that will let you access the metrics, dimensions, segments and the date ranges that you’d use to build your project.

This right here is the report suite selector and this would include a list of all the report suites that you have access to based on the permissions that your admin has entitled you to. I’m going to choose a report suite and that will determine the components that are listed for me in the left nav. I’m going to drag one metric, any metric, I’m going to look for views. Drag the metric onto the drop zone in the panel and you’ll see that the table has defaulted to date. That is what it will default to if you only drag a metric without adding a dimension to the table. I’m going to see if I can drag a dimension onto the table so I can see page views broken down by the most popular pages that drove traffic to my site.

I drag the page dimension, which like we discussed are the rows, and then I see a list of the top pages that drove the most traffic to my site in terms of page views. Say for instance I want to see all the page views that can be attributed to people visiting my site from a mobile device, I can drag the segment onto the canvas and the lens is applied and what I’m looking at are those page views and the top pages that can be attributed to mobile customers. You can also apply, like we discussed, date ranges to your heart’s content to arrive at a view that is as granular as you want it to be.

That’s a demo of Workspace. Once you get started with the training tutorial, you should be going with creating projects in no time. Again, for those of you familiar with Workspace to an extent, I’m sorry if I bored you guys to death, but for those of you starting out or those of you that are yet to have a taste of Adobe Analytics or Analysis Workspace, trust me, what we went through so far and what Jennifer and Maria will go through in the course of the rest of the session may seem a bit simplistic or basic, but I cannot overstate how fundamental these concepts are and how everything else you do with Analytics will rest on this foundation. Good luck and Godspeed. Really looking forward to the questions you have.

Thanks. Welcome everyone to the Q&A. I’d like to welcome Sonja Charles, Solution Consultant for Data and Insights. Thanks so much for being with us for the Q&A. Hey, Tom. Happy to be here. Thank you.

Great. So let’s jump right in. So we’ve had a few questions here from the audience. I’d just like to remind everyone, as you start to digest all that information, please keep adding those questions. We’ll cover anything we can during this section. One of the first questions here, will this particular track cover using the Experience Platform Debugger tool? Oh, okay. That’s a great question to start with. So we’re not covering the debugger in this particular session. And for those of you who are at home or not aware, the debugger is a really simple plugin that we have, enables you to download it in a couple of easy steps and get a really good understanding, for example, if you’ve implemented analytics, you can kind of see how you’ve set up your pages, et cetera, and the values that you have set up for them. So it gives you a good overview of that implementation setup. We’re not covering it in today’s session. However, I really point you towards the Experience League resources that we have online, which will take you through how to download and configure that debugger and how to use it on your page.

Yeah, thanks, Sonja. A good final call out there is that if you do want to learn more about that particular debugger, there’s plenty of documentation online, and our Experience League platform is probably the best place to start in terms of learning about all of the Adobe solutions.

On a similar note, this kind of is related to the second question here. There’s a question about resources that are available to analytics users who want to have experience with the platform beyond things like the YouTube videos or other tutorials. What can other users expect to be able to have access to to really get more experience of using Adobe Analytics? Yeah, another really great question. So, well, the YouTube videos are great, and they’re one of my personal favorites. But aside from that, Experience League, which I just referenced, is kind of like the Bible, really, in terms of resources.

It’s experienceleague.adobe.com, keep me honest. I think that’s the URL. It’s a complete kind of A to Z of how to use our solutions, applications. There are tutorials on there. There’s documentation. We have a community section in there, so you can post questions that can be picked up by some of our experts, consultants, as well as other customers. We have customers who can help out other customers who are encountering issues that they have. So, a really fantastic resource that I would encourage everyone to use. It’s completely free. It’s available in multiple languages. And we have tutorials on how to use Experience League as well. You can reach out to your customer success manager or Adobe rep for help on that as well. Yeah, absolutely, Sonja. I completely agree. Experience League absolutely is the home for all free-to-access resources. I would just call out, if you did want something more comprehensive or in-depth in terms of technical support or particular training or enablement or learning for your teams, you can work with our professional services and learning services functions. So, for that type of engagement, you’re better off contacting your Adobe rep and they can discuss next steps with you. Yeah, that’s a great call-out, Tom, actually. And the benefit of the learning services is you can customise your learning programme as well and have them come and do bespoke training for you.

Brilliant. Thanks, Sonja.

The next question here is more related to the product. And I think, simply put, really the customisability. So, will there ever be a feature update to be able to change the colour of the visualisations? This is particularly from an individual who wants to clean up reports to share with various stakeholders within their organisation.

Yeah, so the good news is you can change the colours. If you are in a project, if you go to settings, you should see an option to change the palettes and colours, the colour schemes that you have in play. You can change them to, for example, match your brand or company colours. So, if you’re sharing reports with your organisation, it’s really great if you can kind of configure the reports to reflect whatever your company or brand colours are and share them across the org. Thanks, Sonja. Great to hear that that is available there.

Another question here. What is the best way to go about understanding insights on what is being tracked on a mobile app via Adobe Analytics? Have you got any tips on this, particularly tracking mobile journeys? Yeah, sure. So, we have within Analytics, obviously, you can build out reports that show journeys and how your customers are engaging with your different properties, including mobile. So, you can build out flow reports, you can build out journeys that show how your customers are moving, even across different devices as well, so from mobile to say desktop and back again. If you look in the visualisations panels, you’ll see the different kind of, there’s a flow journey that you can build out to see that as well. Obviously, you have, you know, we have SDKs, the mobile SDK, you can understand your customers’ engagement on your mobile properties as well by deploying that. So, there’s a number of different ways of understanding what’s happening on mobile and specifically in your app. So, you can track things like the number of times your app’s downloaded, you know, how many people are downloading the latest version of your app, for example, when you deploy a new version so you get an understanding of how many of your customers are using the latest and greatest versions. So, yeah, I would say within app, anything that’s kind of occurring in that environment can be tracked through Analytics. There’s a lot there. So, again, I’m going to sound like a broken record probably on this track, but Experience League takes you through step by step how you can track that information.

Brilliant. Thanks, Sonja.

I’ve got a question here, which is more about actual analytics segments. So, when creating a segment initially, you know, what do you need, what are the considerations you need to make when choosing between visits, visitors, you know, and those types of metrics? What are the key differences between those? Oh, that’s a great question. So, we get lots of questions actually around this kind of like a visit, a visitor, etc.

So, when you’re building the segment, I think the key thing is to think about what am I trying to understand here? So, if I want to understand, for example, you know, how many visitors, how many unique visitors am I getting to a particular section of my site, for example, then the visitor or unique visitor, we kind of use them interchangeably is really the metric that you want to be looking at.

Page hits, for example, or we often call them page views, gives you an understanding of like which of my pages is the most popular, how many times did this particular page get a view, you know, across a period of time. So, that could be, you know, the metric that you would use in that instance. So, and then visits, often referred to as sessions. So, in analytics, a visit or a session is recorded each time somebody comes to your site or to your mobile property. And after 30 minutes of an activity, we would close that and record it as a session or a visit. So again, if you’re looking to understand, you know, how many times a visit occurred over a certain period of time, then that’s the metric that you would use. So, I would say start with the question of what am I trying to understand here? Visitor, how many people are coming or how many times something is viewed, and then kind of take it from there.

Another way of looking at it is how granular do you want to get really? The hit is a very granular one. So, if that’s how deep you want to go, then choose that metric.

Yeah, great. Thanks, Sonja. Yeah, I think that’s really good advice is sort of, you know, start with the question you’re trying to solve, and then you can figure out the best methodology from there. Thanks, Sonja. A few questions here on bounce rate, actually, or how bounce sort of came up. There’s a question really here on how is it set up in analytics? So, I guess, how do we define bounce rates within Adobe Analytics? Is it different to other analytics technologies such as Google Analytics? And also on bounces, is it just available in Workspace or is it available in Data Warehouse, for example? Okay, so working backwards. I believe it’s available in both. So, if you’re tracking that, if you’re looking at that analysis workspace, you should also be able to see that in Data Warehouse as well.

So, bounces are really, you know, when you’re looking at people that are coming to the site and then bouncing, like leaving immediately, so they’re not actually remaining on the page. And in terms of the similarity with that with Google, I’m not entirely sure what the direct equivalent is in Google and whether they call it something different. My instinct would be it would be bounce as well or something very similar to that because it’s the same kind of concept. So, I believe that they would call it the same thing.

But it’s a very useful thing for our customers to kind of track because it can indicate a problem with a page. For example, if someone’s clicking on a link or search result and they come to the page and it’s completely irrelevant to what they were looking for, then they will leave instantly. And then this can tell you as an analyst, we’re looking at a really high bounce rate here. We’re seeing people come to the page, bounce straight off. There’s a problem here. It could be the keyword search is not matching with the page results that they’re seeing or there’s an issue with the page, the URL is broken, etc. So, yeah, it’s a useful metric that we encourage customers to keep an eye on because it gives an indication of if there are any problems there on the page. Brilliant. Okay, thanks, Sonja.

Next question here I’ve got is on cross-domain tracking. The specific question is, is cross-domain tracking only available in customer journey analytics? So, yeah, my question to you is, where is cross-domain tracking available within the analytics products? So, it’s available in analytics as well. It’s not just the CJA analytics. As long as the different domains are your domains and your company domains, you can track across those different domains as people move them across them. So, a good example is brands that owns multiple websites, perhaps for different products or different parts of the business. If their domains all fall under that one particular entity, that one particular company, they’re able to obviously track as people move across those different domains.

Where we run into issues, I think everyone’s aware of the issues we have today with third-party tracking. So, where domains fall outside of your organization and third-party cookies are not blocked or not enabled, then there’s a different situation there. We’re not able to track in the same way or easily track. But certainly, in answer to the first question, cross-domains are available in analytics as well as in customer journey analytics as well.

Great. All right. Good to hear. Thanks, Sonja. Another question here, kind of related to what we alluded to just in that last question about having multiple brand sites. This question is, can I set up Adobe Analytics for five websites within the same dashboard? How would you approach that, Sonja? Yeah, certainly you can. We have customers that have multiple websites, as I spoke to before, multiple brands. There are different ways you can set that up in terms of reporting. So, best practice would be to have perhaps different report suites set up. And for those of you who are not familiar with report suites, I think we’ll cover it in a separate session later today. It’s essentially like a placeholder.

Within each report suite, you’re basically able to report on a website or websites and data from there. So, if you have multiple websites, the way to approach that is you’d typically want to be collecting data for those sites separately to track what’s happening. You’d have different dimensions, et cetera, across those different sites. So, you’d have a single report suite for each of those. They can all report up into a global report suite. But having them out separately means that you can configure access to them across the different brands. So, there could be stakeholders in those five different brands that you don’t want to give access to across all brand data. So, you can just enable that access to each report suite individually.

And yeah, it’s a good idea to kind of just, as I said, separate that information out into different suites.

Yeah, that’s good advice. Yeah, the whole idea of data governance, that’s another question mark when we talk about multiple sites within a single account. Definitely something to think about when you’re deciding on the best approach there.

Another question here, just is it or will it be possible to apply the new visualization key metric summary to an existing freeform table instead of creating a new? How would you approach that, Sonja? Right, that’s a really good question I need to check on because I know that we have the ability to copy and paste certain elements across different reports today.

I would need to double check if that is the case for the visualization that you just referred to there, that key summary. So, really great visualization enables you to, you know, if you have a freeform table with data across several months, for example, for a year and you want to understand what the percentage fall or rise in is, you can have that data in, click on each row and you can automatically see in your key summary, or from one month to the next, there was a 14% drop in page views, for example. So, my thoughts are that if the data is going to be different across different reports, so the copy and paste might not work in that instance, but that’s something I actually need to double check on.

Again, the answer will be in experience league, no doubt, but yeah, I’ll check in on that. Great, thanks Sonja. Yeah, absolutely. Something we can follow up with the various teams or indeed with some additional documentation. So, thanks very much for that question.

Unfortunately, that’s all we’ve got time for. So, thanks very much Sonja. We’ll see you back here after chapter two. I look forward to it Tom, thank you.