Sunday Funday – Day 1 – Epic Metrics

May 7, 2018| Mike Stott

So, if you read my last post you’ll have seen I decided to start a new side project. This was to give me easy to produce “epic metrics” for my transparency reports.

To save me the time in manually putting together spreadsheets and moving them into visualisations (charts) for coverage on the blog.

However, it’s something that – although I found the merit in doing my own solution, I also started to hit some walls with it.

I then found a solution online – Metorik does a lot of good things and I’m using that alongside my Sunday Funday builds.

Building “Epic Metrics”

Epic Metrics is what I’m currently focussing on with my Sunday Funday’s. Epic Metrics is effectively a “souped up” Sales Dashboard for my WooCommerce stores, which will save me time when it comes to producing transparency reports. They’ll also give you a way to hop on over and see “live” how the metrics are doing (without having to manually produce charts from WooCommerce Dashboards).

Day #1 – Recap

In the first day of Sunday Funday I scoped out exactly what I was looking to build and how I’d go about doing it. Here’s the initial set of Metrics I wanted

  • Revenue Chart (New, Renewals Failed, Refunds)
  • Monthly Recurring Revenue and Churn
  • Cashflow Forecasts
  • Product Report Breakdowns

I know I have the information on the first one in my WooCommerce reports, so this would be the easiest to tackle.

Setting up the Database and Finding the API

Great, so both WooCommerce and WooCommerce Subscriptions have APIs which I can “consume” to do my calculations.  Luckily I’ve already got a good handle on these from WooSync for Zero BS CRM and the Sales Dashboard, so a lot of this work will be expanding that into a standalone solution which connects to the APIs and maintains the site.

Here’s how my database of subscriptions looks (the variable types might need some tweaks, but it’s how I’m doing it for now)

$sql = "CREATE TABLE IF NOT EXISTS ". $woosub_t['subscriptions'] ." (
    'woo_site' int(11) DEFAULT NULL,
    'woo_subid' int(11) NOT NULL,
    'woo_parentid' int(11) NOT NULL,
    'woo_orderkey' varchar(100) DEFAULT NULL,
    'woo_status' varchar(100) DEFAULT NULL,
    'woo_curr' varchar(3) DEFAULT NULL,
    'woo_ver' varchar(10) DEFAULT NULL,
    'woo_inc_tax' int(1) DEFAULT 0,   
    'woo_customer' int(11) DEFAULT NULL,      
    'woo_contact' int(11) DEFAULT NULL,
    'woo_discount_total' decimal(19,4) DEFAULT '0.0000',
    'woo_discount_tax' decimal(19,4) DEFAULT '0.0000',
    'woo_shipping_total' decimal(19,4) DEFAULT '0.0000',
    'woo_shipping_tax' decimal(19,4) DEFAULT '0.0000',
    'woo_cart_tax' decimal(19,4) DEFAULT '0.0000',
    'woo_total_tax' decimal(19,4) DEFAULT '0.0000',
    'woo_total' decimal(19,4) DEFAULT '0.0000',
    'woo_method' varchar(50) DEFAULT NULL,
    'woo_method_title' varchar(200) DEFAULT NULL,
    'woo_billing_period'  varchar(5) DEFAULT NULL,
    'woo_billing_interval' int(14)  NOT NULL,
    'woo_start_date' int(14)  NOT NULL,
    'woo_trial_end_date' int(14) NOT NULL,
    'woo_next_payment_date' int(14)  NOT NULL,
    'woo_end_date' int(14) NOT NULL,
    'woo_created' int(14)  NOT NULL,
    'woo_modified' int(14) NOT NULL,
    'woo_completed' int(14) NOT NULL,
    'woo_paid' int(14) NOT NULL,
    ENGINE = InnoDB
    COLLATE = utf8_general_ci";


Quite the chunk of data which I’ll be bringing in from the API. On top of those, there’s the “Line Items” for a subscription (so you can see which products make up that subscription) as well as the Orders related to that subscription.

Importantly, I setup the data to have a top level of woo_site which is an index meaning I can run the same import routines

Here’s how it looks “sketched” out and how I’ll be linking it all together via the data.

Importing the data

This was a case of running through each page of the WooCommerce API response and storing the data, I wrote a couple of quick AJAX functions to do this. These request the subscription and transaction resource and run through updating the database.

I wrote a lot of ADD / UPDATE type functions using standard $wpdb->insert or $wpdb->update so that all the information utilises the WordPress SDK and Codex, and is properly prepared (using $wpdb->prepare).

Charting the data

The next thing was to visualise the data into a handy chart 🙂 for this I used Chart.js but also factored my SQL to be run and produce the necessary information. It’s not as simple as just running a query (this is resulting from querying the transaction database, NOT the subscription database). Here’s how the SQL looks (if you’re interested!)


MONTH(FROM_UNIXTIME(wp_epic_woo_transaction_lineitems.woo_created)) asmonth,
YEAR(FROM_UNIXTIME(wp_epic_woo_transaction_lineitems.woo_created)) asyear,
COUNT(wp_epic_woo_transaction_lineitems.ID) ascount,
SUM(wp_epic_woo_transaction_lineitems.woo_total) as revenue,
FROM wp_epic_woo_transaction_lineitems";
$sql.=" WHERE wp_epic_woo_transaction_lineitems.woo_site = %d";
$sql.=" GROUP BY
ORDER BY year ASC, month ASC";


So, now that I have all the data in the database and the chart data prepped, drawing it with chart.js is easy. I also added a simple “site select” which lets me filter between sites so I can view my stats.

It’s only available on my local host right now, but here’s how it’s looking (which you’ll see in my Transparency Report ending 30 April 2018)

Summary of Day 1

So, in Day 1 of my Sunday Funday I built a database layer, and “DAL” functions (data access layer) these are standard functions which do the app / updating and grabbing of the data and charting of the results.

I’ve not decided on a official domain to host this yet or whether it’s something I’ll eventually sell as a plugin, or a SaaS but for now it’s certainly been a fun, productive day.

Categories: Sunday Funday

One thought on “Sunday Funday – Day 1 – Epic Metrics”

Leave a Reply

Your email address will not be published. Required fields are marked *