By Nate Nunta - September 1, 2020
For e-commerce analytics teams, creating a source of truth for your disparate data across multiple e-commerce channels like Shopify, Amazon, and your own site can be a daunting endeavor. However, if you can build a single view of your transactions across channels, you’ll accelerate your ability to understand why key metrics like AOV, LTV, and acquisition change.
When you can monitor these metrics in real time, your analytics team can finally provide the business with actionable insights, informing everything from promotions to product packaging to future product decisions.
At Sisu, our Implementation and Customer Success teams have supported dozens of analytics teams in creating cloud-native data architecture tuned for the realities of e-commerce analytics. Here are a few of the best practices and tips we’ve picked up along the way. While some of these recommendations are common knowledge for data engineering and analytics teams, others result from our practical experience delivering faster, comprehensive, and more accessible analytics for customers.
Before you can begin analyzing your e-commerce data, you’ll need all your disparate data stored in a central location — ideally a cloud-native data warehouse.
There’s a myriad of benefits to using cloud data warehouses that we go into in our full-length guide. For e-commerce analytics, what’s important is moving your data sources to a centralized online location to create a nearly infinite, low-cast, and scalable solution. Data warehouses also move both the security and management of your data to the cloud, providing additional security that is hard to replicate if you’re storing data on your own.
With your cloud-native data warehouse set up, outline the key metrics your business will want to track and identify, particularly if there are any unique metrics you need to pay attention to for your online sales.
Then you’re ready to create a data map. While it may seem tedious, this data mapping step is crucial to the success of the project. Different sales channels report transaction data in different ways. When you’re moving to consolidate the data, you need to ensure it’s moving from your disparate data sources to your data warehouse consistently.
To make this more concrete, imagine you’re an analyst at the Awesome Energy Bar company. You sell five flavors of energy bars (Chocolate, Peanut Butter, Coconut, Cherry Vanilla, and Chia Crunch) through an online marketplace, an e-commerce platform, and your website. Each sales channel provides slightly different ways of reporting transactions.
In your data map, you should include everything your business will need to know in the current environment and everything you envision they’ll want to know in the foreseeable future.
For example, Awesome Energy Bar currently only cares about how flavors and product categories impact AOV, but they’ve earmarked a budget to add marketing attribution data in the next six months. That means that you’ll need to start moving to the cloud warehouse without that attribution data in place. But with a data map, you can plan for this by researching the metrics the team will want to monitor, identifying the unique data factors the new marketing application provides, and leave room for those factors on the data map.
We’ve found that adding the intel you gather to the data map as early in the process as you can will make your e-commerce analytics easier in the long run. Plus, it has an added benefit of allowing you to answer unexpected questions from the business unit.
Particularly when you’re dealing disparate data sources like those in e-commerce analytics, having a single table that combines them all into a standard schema will allow you to see correlations within and across the funnel. It will help you create a single definition for a transaction, even if each sales channel provides different factors.
There’s an added benefit of allowing you to capture insights that may not have been obvious correlates: for example, at Awesome Energy Bar company, if the business was intent on capturing geolocation metrics and had aggregated their data according to that metric, they may have missed something less intuitive: that flavors with labels listing organic ingredients are actually a more significant factor in sales than location.
Think through the structure of your data table, including:
In the past, analyzing your data across each online channel would have been slow, using CSVs, or focused only on one data source at a time. Now that you have all your disparate data in a central location, you can point an augmented analytics tool like Sisu at it to diagnose changes in your e-commerce data in real time.
For our fictitious Awesome Energy Bar company, they’ve connected Sisu directly to their data warehouse and can quickly see actionable facts from across their retail channels like: