WooCommerce is a popular e-commerce plugin for WordPress websites. It enables users to easily set up and manage online stores, offering various features, customizable design options, and seamless integration with other WordPress plugins.
WooCommerce is an e-commerce platform for selling physical products, digital content downloads and/or subscriptions. An open-source WordPress plugin, you can customize it however you please. Add unlimited products, users, and take as many orders as you want without the typical costs of a comparable SaaS platform.
With Databox, track your most important WooCommerce metrics alongside performance data from other important tools like Google Analytics, SEMRush, Mailchimp, Klaviyo or your own databases or spreadsheets. Once connected, build custom reporting dashboards and instantly monitor it all on any device: computer, mobile, Apple Watch, TV display and Slack.
Get started in minutes by connecting WooCommerce and using one of our templates below, or by adding any of the metrics listed below to a dashboard of your own design.
Show more...
All data for custom WooCommerce metrics created using the Metric Builder, is pulled exclusively from the Analytics tab. This includes any filtering options specific to the Orders report in the Analytics tab.
Legacy reporting tabs are not used as a data source for these metrics.
Metrics that use longer date ranges (e.g., a quarter or longer) combined with small granularity (e.g., daily or weekly) may experience slower loading times.
For example, using ‘Last Year’ or ‘All Time’ date ranges with daily granularity can be excessive and lead to significant delays. To prevent this, Databox implemented a quota limit for all new (non-legacy) metrics of 60 requests per 5 seconds.
Smaller date ranges, such as ‘This Month’ or ‘Last Month’, typically load without any issues, even with daily or weekly granularity. However, as the date range increases (starting from a quarter or longer), applying small granularity like daily or weekly can slow down performance.
To improve loading times, consider: • Shortening the date range. • Switching to larger granularity, such as monthly, when working with long date ranges.
Revenue-related WooCommerce metrics (those with currency values) are always returned via the API in your store’s default currency. Although WooCommerce supports multi-currency functionality through extensions like Multi-Currency or WooPayments’ Multi-Currency feature, the Analytics and Reports APIs do not natively support metrics in multiple currencies. Therefore, reporting data is limited to your store’s default currency.
These metrics track the Average Daily Sales over time. However, if there are no sales on a specific day (resulting in a value of 0), it may appear as though the total value over the selected time period is 0.
This is because the API provides data only for the current day, with metrics refreshing daily. Since historical data is not initially available, each day’s synced data is stored in the Databox warehouse, allowing data to accumulate over time. As more data is collected, trends can be visualized on line or bar charts, enabling better analysis over extended periods.
To optimize these metrics:
When using metrics attributed to ‘Product’ (e.g., Net Sales by Product or Total Sales (Legacy) by Product) in a table, the displayed value for a product may not always show the correct total, especially when viewing data over periods spanning multiple days (e.g., Last Week, This Month, Last Month).
Databox calculates these values by fetching daily data for the selected period and summing the results. However, in some cases, only the data for the first day (or a single day) of the period is displayed in the table instead of the full total.
The correct total typically appears once all data for the selected period has synced, which may take a few minutes. To manually refresh the table, you can perform actions like changing the number of rows displayed or adjusting the ‘Sort by’ option.
Alternatively, switch the metric to a bar or line chart, add at least one dimension in the dimensions field, and enable the option to display the total value above the chart. Once the total updates correctly, you can switch back to the table view, and the correct value should display.
When comparing WooCommerce metrics in Databox, it’s important to note that the values can differ depending on the used metric. WooCommerce provides two sections for tracking data: Reports: Found under WooCommerce > Reports. Analytics: Found under WooCommerce > Analytics.
In Databox: Databox metrics labeled with ‘Legacy’ are pulled from the Reports section while metrics without ‘Legacy’ in their name are pulled from the Analytics section.
Since data between the Reports and Analytics sections in WooCommerce can vary for the same metric (e.g., Total Sales), it’s important to verify which metrics you’re using in Databox and compare them to the correct source in WooCommerce.
Legacy metrics are identified by the marker ‘(Legacy)’ in their names, such as ‘Total Sales (Legacy)’, whereas newer metrics lack this label (e.g., ‘Total Sales’). The primary difference between these metrics is the reporting system used to generate their data.
Legacy metrics rely on data from the older Reports tab, which uses WooCommerce’s legacy reporting system. In contrast, newer metrics are based on data from the Analytics tab, a more advanced reporting interface introduced in WooCommerce 4.0.
Since the values in the Reports and Analytics tabs may differ, it’s crucial to confirm which reporting system your WooCommerce store is using. This ensures that your Databox data aligns accurately with the corresponding WooCommerce data.
Data discrepancies for certain dimensions can occur if a dimension is renamed directly in the source. The first step is to check if the dimension has been edited, renamed, or changed in WooCommerce. Renaming dimensions in the source can lead to unexpected results, as Databox may interpret the renamed dimension differently.
If the metric updates historical data in WooCommerce, duplicate dimensions may appear in Databox. If the metric does not update historical data, duplicate dimensions will still appear, with one showing the old name and the other showing the new name.
As a general rule, any changes made directly in the data source can result in discrepancies in Databox. To resolve this, the affected metric or data source can be purged to remove previously synced data.
Due to an API limitation, Databox cannot fetch individual refunded orders from WooCommerce accounts with refunds. As a result, some users may notice data discrepancies in the following metrics, as the values do not account for refunds (this limitation may also affect related dimensions):
Total Sales (Legacy) Average Net Daily Sales (Legacy) Average Gross Daily Sales (Legacy) Net Sales (Legacy) Tax (Legacy) Orders Placed (Legacy) Items Purchased (Legacy) Refunded Amount (Legacy) Charged for Shipping (Legacy) Worth of Coupons Used (Legacy) New Customers (Legacy)
This limitation arises from the legacy API endpoint used by the WooCommerce Reports tab. Unfortunately, Databox cannot resolve this issue unless WooCommerce updates its reporting endpoints to include refunds.
Only WooCommerce accounts without any refunds are unaffected by this limitation.
‘Last 7 Days’ is set differently in Databox and WooCommerce, so comparing the points on a Line Chart will not result in a one-to-one match. In WooCommerce, ‘Last 7 Days’ includes ‘Today,’ whereas in Databox, ‘Last 7 Days’ does not include ‘Today’ unless the ‘Include Today’ checkbox is turned on in the date range options.
When a WooCommerce data source is first connected in Databox, 36 months worth of data is initially available for most metrics. Certain metrics may have more historical data available, while others may have less.
The following (legacy) metrics have no daily historical data available:
• Average Gross Daily Sales • Average Net Daily Sales • Refunded Orders • Refunded Items • Refunded Amount
Historical data is synced for these (legacy) metrics only in the form of total values for each available date range – for example, data is available for the date range ‘Last Week’, but it is not available for specific days of last week.
If these metrics are used in a Line Graph visualization, the number above the line will show the total metric value for the selected date range. However, the line itself will only display data starting from one day before the metric was first used.
A common cause of this error is the installation of a Cloudflare plugin on your site after connecting the source in Databox. This can block Databox’s requests to your WooCommerce account, resulting in failed connections.
To resolve the issue, ensure that the Databox IP address (52.4.198.118) is whitelisted in your Cloudflare settings.
To connect WooCommerce to Databox successfully, you must install a plugin that enables the REST API, allowing Databox to authenticate and access data from the Analytics tab.
If the plugin is already installed but the connection fails, consider these common issues: • Plugin Configuration: The plugin may not be set up correctly. Double-check the configuration to ensure it’s properly enabled. • WooCommerce Security Settings: Security settings in your store might be blocking Databox’s access. Verify and adjust these settings if needed. • Conflicting Plugins: Another plugin may be interfering with API access. Temporarily disable other plugins one by one, testing the connection after each, to identify the culprit. • WooCommerce Support: If the problem persists, reach out to WooCommerce support for further guidance.
By addressing these potential issues, you should be able to establish a successful connection.
The error ‘Cannot List Resources’ indicates that the credentials used to connect WooCommerce are incorrect or invalid. Common reasons for this issue include:
Please review these potential causes and address any that apply. After resolving the issue, reconnect your WooCommerce account to restore the connection.
This error indicates that the Databox IP address (52.4.198.118) has been blocked by the service you are using due to security measures, often by security plugins on WordPress-hosted pages. To resolve this, please check if the IP block can be removed on your end. Whitelisting the Databox public IP address will allow the connection. Once the security settings are adjusted, Databox should reconnect successfully.
A common reason for connection failures with WooCommerce is that the installed plugin is blocking API access for security reasons. This can include theme-related plugins or certain WordPress versions.
If you’re unsure which plugin might be causing the issue, try disabling your plugins one at a time, testing the connection after each. This process can help identify the specific plugin interfering with the API.
Once identified, you may need to adjust the plugin settings or consult with your developer to resolve the issue while maintaining security and functionality.
This issue is caused by Cloudflare’s security protection. Since Databox generates a high volume of requests in production, Cloudflare may classify the Databox app as a potential DDoS threat and block some of the API calls. Unfortunately, this is a built-in security feature that Databox cannot bypass.
To resolve this, we recommend either disabling Cloudflare protection for the Databox IP or host, or whitelisting the Databox IP address (52.4.198.118) within your security network or tool to allow Databox requests.
After making these adjustments, reconnect the data source to confirm if the issue has been resolved.