Adobe Commerce Intelligence integrations and configurations

This is Russell with Adobe, and we’re going to be talking about Adobe Commerce Intelligence. Today we’re going to cover the topics of integration options, and briefly describe the commerce integration. We’re going to talk about syncing tables for additional reporting, syncing more columns within the same table, changing the sync type. We’re going to cover some basic building blocks of reports such as metrics, filters, and filter sets. Starting off, we’re going to go to the Manage Data tab, and this is sometimes called the backend of Adobe Commerce Intelligence. And this is how you set up and configure everything for your project. And you can see here there’s a lot of areas to explore, but today we’re just going to focus on a few of them. We’re going to cover the integrations, the data warehouse, and the reporting capabilities. We’ll see the current integration information. And from this example, you’ll show that an Adobe Commerce database is integrated as a MySQL connection. And if you want to review this or edit this in the future, you click on this little icon, and from here you’ll see the settings that were used to make this connection to Adobe Commerce Intelligence. And here, this link force update, this will force the integration to connect and sync the data. If you want to add more integrations, you click the Add Integration button on the top right, and then you can do things like do the preconfigured Google Analytics or Google Commerce. You can even use a native API to import data. And then there are some standard integrations that are available. Typically, you can have up to about five integrations. Be sure to check your contract to know what was part of your package. But if you need more than that, you can reach out to your sales team and figure out how to add more. And finally, in the integration section, there are premium integrations, and these are generally not included as part of a standard contract, but they are available, and just reach out to the sales team to learn how to enable these options. For data integrations that are not pre-built, you still have a few options available. You can use the Data Import API and upload a file. If the source of your data is an API, it is recommended to use the Data Import API. And once it’s connected and synced to the data warehouse, you can use this information for your reports. If it’s just a one-off piece of data or not available from an API endpoint, then the best option is upload a file. Most of the time, merchants, when they use this option, will have an Excel or CSV file, and it contains the data necessary to put in the storage in the data warehouse. So once you’ve uploaded that file, you’ll be able to see this data in your data warehouse as a DB table. Now, from that point, you can use it as a reference for data, and then you’ll be able to create a report or charts on top of it. From the Data Warehouse button on the left side, this is where you can see what tables are synced to Adobe Commerce Intelligence. When you log in for the first time, the tables shown will be the default ones that were used to create the out-of-the-box reports and dashboards. There’ll often be a need for additional tables and columns for your custom reports. Another scenario may be that you need to add some columns to an existing sync table for some customized reporting. Let’s add a new table to the sync. Let’s say it’s the customer entity decibel. And now you’re going to go through and check some columns that you want to export. If you click on this icon, it looks like a circle with the check inside. That’s how you can sync this table with the data warehouse of Commerce Intelligence. Now, let’s say you want to see what columns are being synced from an existing table. And the reason is you want to add a new column to that syncing table. You’ll find this list by clicking on sync tables. Let’s find one that we’re interested in. Let’s say it’s the sales order. And then you’ll see the synced columns. And if you see these green tick marks over here, that means this column is already synced with the data warehouse of Commerce Intelligence. However, if you see this icon, that means it is not synced. For a special type of sync data, off to the right side, you’ll see this blue square with the pencil. Wherever you see this icon, that means it’s a calculated column and does not exist in the source database, but we still need the data. So what we do is we join data from other tables to make the reporting faster and easier. For example, we want to throw the billing city into the sales order. And once again, this is a calculated column. This data is not available in the sales order table of Adobe Commerce. So if you look at the database, it won’t be there. So in sales order, this is the ID that we’re looking for right there. Okay? And then what we’re doing is we are joining it to the sales order address using this ID as a reference. And that’s how we find the billing address city, and we join it to the sales order automatically for the export. And that’s an example of how you can add a new column to your data import. On to metrics. So for someone who understands SQL, you can consider a metric as a stored query. And if you don’t understand SQL, then a metric would be basically a repeatable question that you’re asking your data warehouse or your table. So for example, let’s say you want the average first 30-day revenue. Then we can have this as a stored query or a repeatable question, and then we can call it a metric. So how is a metric different than a report? So for example, a metric, let’s just say it could give you the first 30-day revenue, but a report would give you the revenue per city or maybe add a filter to skip some order IDs or some email addresses that you don’t want to have. So a report would be an insight to bring out of your data. Now, if you want to understand how this metric was created, you’re going to click on edit, and you’ll see that this entity ID is our reference, and then we’re doing a count on it. And then we’ve added a column metric of customer’s first order date and then a filter. So this just shows you how we created this metric and the configurations for it. Also, you can create additional filters if you feel it’s warranted for this type of metric. So let’s quickly cover a filter set. If you create a filter on the customer entity table and you want to use it in any of the metrics you’ll create, so the point of this would be that you create it once and use it in multiple places. And one typical example for this would be, let’s say you’re creating some orders in your application and you want to skip those orders that have some sort of email pattern. You don’t want those to show up in your reporting. What you’ll do is you’ll create a filter on your sales order table and filter out those email IDs, for example, like testorderatexample.com. And once again, creating this filter set, you’ll use it in all of your metrics. And if you click on reports, this will show you all of the reports that have been created. If this is your first time logging in, this will be those initial set of reports that were created to help you get you started. Well, that’s it for now. Please continue learning about Adobe Commerce Intelligence, as well as the rest of the Adobe Commerce application and experience link.