Recently we were diving into the integrations DigMyData customers use the most. We realized our Authorize.net integration was not being used as much as others. This seemed odd, because it is a valuable integration.
Our Authorize.net integration provides great information:
Average revenue per customer, etc.
These metrics are even more valuable when you layer them over your other DigMyData metrics.
But, the Authorize.net integration requires more information to integrate than some of our other connections.
With Authorize.net, we require not just your API key, but your transaction key. This is standard in gateway integrations and is for your security.
A transaction key is a complex value that uniquely identifies a merchant’s payment gateway account, and is similar to an account password. Transaction keys are used to authenticate requests submitted to the payment gateway.
The problem in integration occurs because Authorize.net doesn’t save the transaction key in your profile.
As you can see above, the API ID is something that is easy to get (this one is ‘greened’ out for security reasons).
But the transaction key is not.
Authorize.net doesn’t save it in your profile.
If you don’t save it yourself in another (secure) location, and decide to integrate something else, you have to get a new one.
When you generate a new key, the old one will automatically expire within 24 hours.
The question is: what does that affect?
Everything your Authorize.net account is integrated with.
Including your shopping cart and merchant account.
Important things, that you want to be fully functional at all times.
How can you resolve this so you can add more integrations, easily without worrying about something not working?
Save your transaction ID in a secure location
Alternatively, keep a list of everything your have integrated Authorize.net with
In addition, when you change something related to your payment process or flow – always test a couple transactions to ensure that they are going through properly.
This past week I found myself totally overwhelmed with prioritizing all the work that we should be working on for the current release and the next two releases (and in my mind – several releases after that). We are heavy users of Atlassian’s JIRA (we’ve hacked together our own priority system where each release gets a priority) and, over time, we’ve created and closed thousands of issues on DigMyData.
As I was planning the next release (slated for late July), I found that there’s just no room for the work that we need to do. There was already a release-worth of work to be done. How are we going to fit in the important improvements and new features that we’d just talked about at our retreat in St Petersburg? Where did all this work come from?
Ah – and then it hit me (actually – it didn’t hit me until the next day after agonizing about what to do). Over the past 6-8 months, I had been postponing tickets from previous releases AND also prioritizing new bugs and improvements in future releases. Why did I do this? Well, there wasn’t enough time in the then current release to do them.
The net effect? We were working on old priorities – like 2 to 3 month old priorities. And – as parts of the application would change – we’d find that older requirements for one part of the application (Settings) didn’t make as much sense after more recent changes to the Metrics page. But that kind of scrutiny often eluded us as these tickets had been well thought out when they were conceived.
So what did we do?
I got rid of all of them. Ok – I didn’t actually get rid of them, but I changed all tickets with a future priority to “Needs priority”, closed a bunch, and even removed a bunch of tickets from the June release (we’re aiming to be code complete on Friday Update: we were code complete on Friday but we’re still testing. Yea – still need to improve our testing/release process). Then I grabbed a piece of paper and wrote down all of the important bits of work that we need to be working on. I didn’t look at our backlog, I didn’t reference tickets. It felt great – so liberating!
As the items went down on paper, it became very clear what work need to happen right away (July) and what needs to wait. But this time I didn’t slide the lower priority items into August, September, and October. Who knows what the priorities will be by then? What will we learn between now and then? And I don’t need to worry about losing these important thoughts – they are all right there in JIRA – immanently categorized and searchable.
Last night we had a team meeting – tried to do it on Google Hangout but it turned into Google Hangup (we’ll try again next time)! We went over the real priorities and started with a clean slate for July’s release.
It’s easy to build up a mental model of the future and then get stuck trying to make it happen.
Update 1 It’s been almost two weeks since our hangout and the one difference I see in our working is focus. We’re all working on related work now (specifically – July is about making what we have work better, no new features, just work better). We’re no longer working with a 3 month lag between decisions and getting the work done.
Update 2 Apps like Mailbox and Boomerang are great for hiding emails until they are actionable. But – I also notice that I will push out an email into the future to delay making a decision. Then Monday mornings I’ll open my email box to see a whole bunch of emails that I have already triaged.
tl;dr – we launched two new integrations and a ton of new features.
We’ve been super busy developing and testing but not so busy writing blog posts. Frankly this should be about 10 different blog posts – but here it is – in just one post.
Metrics emails – this is our second major attempt at sending a weekly report – this time we think we got it right.
How does it work?
It takes all of the shown metrics in the Metrics page and sends them to you each week on Monday morning.
What do we show?
– Metric data for two weeks ago, one week ago, the past week, and the forecast for the current week.
– We highlight the metric that changed the most the past week (this is the metric at the very top of the email)
– In the best/worst weeks for that metric we will highlight this (best sales week ever!)
– For those weeks where you don’t hit a max or min, then we’ll help you understand how you did compared to last week (better/worse/no change)
Who will get these emails?
Right now we have this feature only turned on for brand new users. We want some air time with this before we invite everyone to turn on the feature. But if you want access to this feature right now just go to: https://app.digmydata.com/account/notifications
Holy cow – I’m getting way too many metrics in my email!
Congratulations – you have access to tons of data in DigMyData! And there is way out – see the very next new feature which not only hides metrics from the Metrics page but also from the weekly report (someday we’ll create a better way of selecting metrics for the weekly report).
Metrics Page – Hiding metrics from Metrics page
Spreedly – Add Spreedly Customer ID to details
Click on the Subscriber ID and we will link you directly to the corresponding Spreedly page.
MailChimp – we now can access all subscribers (not just double-opt in subscribers)
New Integration – Intercom
Intercom makes communication between businesses and their customers super easy. If you have written us for help through the in-app support mechanism then you’ve used Intercom. We were one of the very first customers of Intercom and have found it to be a great way to communicate by email or within DigMyData. Recently we wanted to know a few metrics about how many of our customers are using the app (Active Users). See – it’s great to have trials and signups – but something has to happen in between. What is that? Users have to fall in love with your product. Surely there is a way to measure this right? Well, Intercom does a great job of tracking all of this for us – and we wanted a way to see this at a high level in DigMyData.
Now in DigMyData when you add Intercom you will have three new metrics:
New Intercom Metric: New Users – How many new users signed up for your service?
New Intercom Metric: Active Users – How many of your users logged into your service?
New Intercom Metric: Total Users – This is a cumulative view of the number of users who have signed up for your service.
(As with all metrics you can view this by Day, Week, Month, and Quarter – and forecasted!)
I was introduced to Intercom at the ’11 Business of Software Conference in Boston by Des Traynor, and the awesome folks at Intercom just raised another bundle of money. It’s a great product now, and we’re excited to see what they build with all that money.
New Integration – Spreedly (Core)
As part of our partnership with Spreedly we have also taken on their new product – Spreedly (previously Spreedly Core now just known as Spreedly and the subscriptions product is now Spreedly Subscriptions). Spreedly allows businesses to securely vault credit cards and use multiple gateways for processing transactions. Their product is very popular with non-USA businesses but also with any business that wants to keep portability between gateways.
New Spreedly (Core) Metric: Revenue – See all the money coming into your business in one place. Because we love all these international businesses we’re even splitting up the revenue by currencies. Because USD$100 isn’t the same as GBP£100 (as much as this American traveler wishes).
New Spreedly (Core) Metric: Transactions – Simple view of the number of transactions in your Spreedly data. Very handy when trying to create some custom metrics (like average order).
New Twitter Metric: Retweets – Track the number of times your tweets are retweeted.
New Spreedly (Subscriptions) Metric:Spreedly Conversion metrics – This is actually two metrics. Trial to Paid Conversions and Free to Paid Conversions.
New Spreedly (Subscriptions) Metric: Tenured Churn Rates – We have offered this metric for some time for our Stripe users and we’ve now made this available to our Stripe subscribers. Tenured Churn Rate takes into account when a subscriber signed up when calculating churn rate. Oftentimes SaaS companies have very different churn rates for new (high churn) and old (low churn) subscribers. Big changes in the individual tenured churn rates give you a more detailed view in how your customer base is changing. We split churn rate into four total metrics: Overall Churn, 0-30, 31-90, 91+.
New Spreedly (Subscriptions) Metrics: Plan revenue – SaaS businesses have the huge advantage of offering the same product at many different prices (different features or grandfathered plans). We now split out the revenue per plan so you can see which plans are contributing (or not) to the bottom line.
New Spreedly (Subscriptions) Metrics: Active users – Same as plan revenue but gives you a number if you want to create some custom metrics (average revenue or group certain plans together: premium plans, etc).
Support for Spreedly currencies – Better support for different currencies for Spreedly (Subscription) users – we now show the correct symbols in the chart.
– New Company Settings page – New style plus add your company’s URL and we’ll pull your favicon for your company and put that in the company selector; this is a fun touch plus helpful for those of your managing two or more companies in DigMyData.
– Metrics page is default page now
– Spreedly Core improvements
– Touched up lots of styles – a lot more fun to use
74 smallish to big new features
Muchos bug fixes (101!)
What else has been going on?
We’ve been very busy putting together the last couple releases – but we’ve also had a bit of fun. At the beginning of June we all got together in Saint Petersburg, Russia for the “DigMyData 2013 Summit”. It was the first time we had all been together – most of us had meet separately but this was the first time we had the whole core team together. I’m putting together a full writeup of the summit that we’ll post here on the blog. For now I’ll leave you with two nuggets – there will be an “easter egg” in DigMyData in our next release (early July) and this picture:
Over the next couple months we’ll be updating each of the integration’s settings pages to the new design. As we do that we’ll be updating the underlying code which will allow us to make some long standing improvements (like hoping between pages without reloading!). With your feedback we will touch up the weekly reports – send feedback to firstname.lastname@example.org. We will also spend some time on some mechanisms to let you know when your data needs babysitting (connecting again to PayPal, Stripe, Facebook, etc) so we can all avoid the gaps in data.