Tag Archives: retail analytics

Bringing Real-time Analytics to the Store

When we released the first full production version of DM1 in May, it was a transformational leap in customer location analytics. Now, six months later, we’re releasing the first major upgrade to DM1 – and it’s a doozy. We’re adding powerful new approaches to improving the store and driving actionable results while putting the competition even further in the rear-view mirror (they’re back there somewhere). Some of the coolest new features include:

Real-time View:  See and track what’s happening in the store as it happens

Real-time Messaging: Integrate with Associate and Shopper Mobile devices based on what’s happening right now

Playback: See what happened in the store using a time-lapse simulation of actual shopper behavior

Week-Time: A cool new visualization that shows a Day-Time part analysis for ANY metric or segment

Flexible Cloud Hosting: Azure or Google Cloud, your choice.

And that’s just the big stuff. There have been a host of small tweaks, fixes, performance enhancements and visual improvements in the intervening months.

That initial version of DM1 had a pretty remarkable feature set for a V1 product in a brand new market. It delivered a revolutionary store visualization tool that mapped its powerful metrics into the store at any level of abstraction – from Display to Section to Department to Floor to Store. And the metric set if provided shattered existing door-counting paradigms by delivering real journey metrics. What shoppers did first. Where they spent the most time. Every place they shopped. What got the most consideration. What converted. What didn’t. And DM1 V1 integrated a rich set of Associate tracking metrics into the basic product as well. Associate presence, intra-day STARs, interaction rates and times, and associated lift. DM1 also delivered powerful grid-based reporting and charting, a really cool funnel analytics tool and a powerful side-by-side comparison tool.

With the new features, we’ve focused on adding a set of capabilities that extend DM1 deeper into the store and make it easier to integrate into broader store marketing and operations efforts. The biggest part of that is, of course, real-time.

We’ve always collected store data in real-time – and all of our collection technologies support near real-time data about the shopper. But in the V1 release, everything we did was batch processing and next-day analytics. That isn’t just because batch processing is easier (though that did matter to us). It was also because many years of experience in digital analytics convinced us that the applications for real-time analytics were fairly rare. There was a time when real-time reporting was a huge part of the digital analytics sales process. But in the end, the dominant tools in digital analytics deliver intra-day but far from real-time analytics. So we figured if a very mature market like digital analytics could do without real-time, we didn’t need it for our V1 release.

But the store is different beast than a Website, and we’re finding that having a real-time view of what’s happening makes it possible to add value at the Store Manager level AND support both CRM and queue management applications that help improve the customer experience.

So real-time became a central piece of our V2 release. And once we built out the core capability, we took advantage of it in multiple ways.

The Realtime view show’s what’s happening right now in the store. Associates and Shoppers are shown (using different symbols) and you can quite literally track exactly where they are and where they are going. We even color-code Shoppers to make it easy to identify how long they’ve been in the store.

Check it out:

realtime, location analytics, store analytics, store traffic, DM1, Digital Mortar

Pretty cool. The Playback capability provides the same view but processes historical data. Since it’s historical, it can collapse time periods into a time-lapse view. So you can see an hour or a day in five minutes.

Being able to see real-time data is cool and highly useful for folks on the ground, but I won’t claim the analytic implications are enormous. What is enormous, though, is the capability to tie DM1’s tracking and measurement into real-time messaging systems. We’ve built a straightforward Webhook messaging interface that lets you get three kinds of data out of DM1: current metric data (for uses like queue length), real-time shopper data, and real-time Associate data.

The real-time shopper data can be based off any customer key we have. And it provides a CRM view that includes Entry Time, Total-Time in Store, Presence and Lingers by Section, Current Location, Time since Interaction, and Associate ID of last interaction. You can use this data to generate real-time messages via your mobile application or in-store beacons to the shopper.

As cool as this shopper interface is, I’ve long been a believer that messaging Associates is even more fundamental and important. With shoppers, opt-in is always a challenge. And barring a truly compelling application, I think it’s tough to get enough opt-ins for messaging to make it impactful. But Associates are increasingly being armed with digital tools that allow them to do more (like distributed PoS) and serve the customer better. Being able to optimize Associate interactions with real-time data and positioning is a huge leap forward in operational sophistication.

In addition to real-time, we’ve made a boatload of analytic enhancements too. And one of my favorite new views is the WeekTime report. We’d already build a custom report around staffing that laid out STARs (Shopper to Associate Ratio) by day of week and time of day (down to the hour). But that report wasn’t a thing of beauty and, in any case, it was specific to the STARs metric.

Because Day-time parting is so fundamental to the store, we wanted a generalized analytics tool that would do the job. The WeekTime tool lays out any metric by day-of-week and time-of-day.

Here are some examples of the WeekTime tool. The first view shows when the store had the most shoppers. The second view shows when shoppers spent the most time in the store.

Shopper Traffic by Day-TimeAvg. Shop Time by Day-Time
Day-Time Traffic View for DM1 retail analyticsDM1 Avg. Time by Shopper for Store Analytics

And like all DM1 workbench tools, the Weektime tools is driven by our big data event-level engine so it supports integrated segmentation across any time-period. It’s a really nice analytic addition to the Workbench and the Dashboard view. It makes it much easier to quickly visualize and understand how day-time parts are driving performance on any measurement.

One of the biggest changes we made in V2 isn’t functional but environmental. We built DM1 on Azure and it’s been a great platform. But we’ve seen that our clients are going in all sorts of directions in an incredibly competitive cloud marketplace. And if the rest of your infrastructure is on Google Cloud (GCP), then it just makes sense that DM1 live there too. So in V2, we offer the choice of cloud provider. We’ve ported the entire platform into GCP and – as a bonus gift to ourselves – made the deployment process a lot more automated and easier for us. Microsoft Azure or Google GCP – it’s now your choice. And it’s just part of making sure DM1 is the most technologically sophisticated AND seamless platform around.

V2 is another big step for us. But we’re just getting started. I keep an ever-growing Trello board of new features and some of the most exciting stuff to come includes a full real-time Store Manager tool, a much more comprehensive and beautiful Associate performance report, a store-change report that automatically shows you the impact of every store change in a period of time, the integration of D3 into our charting capability, a full pathing tool, a robust segmentation builder, and even an initial foray into machine learning.

Can hardly wait!

An Easy Introduction to In-Store Measurement and Retail Analytics with DM1

My last post made the case that investing in store measurement and location analytics is a good move from a career perspective. The reward? Becoming a leader in a discipline that’s poised to grow dramatically. The risk? Ending up with a skill set that isn’t much in demand. For most people, though, risk/reward is only part of the equation. There are people who will expend the years and the effort to become a lawyer even without liking the law – simply on the basis of its economic return. I’m not a fan of that kind of thinking. To me, it undervalues human time and overvalues the impact of incremental prosperity. So my last and most important argument was simple: in-store measurement and location analytics is fun and interesting.

But there’s not a ton of ways you can figure out if in-store measurement is your cup of tea are there?

So I put together another video using our DM1 platform that’s designed to give folks a quick introduction to basic in-store measurement.

It’s a straightforward, short (3 minute) introduction to basic concepts in store-tracking with DM1 – using just the Store Layout tool.

The video walks through three core tasks for in-store measurement: understanding what customer’s do in-store, evaluating how well the store itself performed, and drilling into at least one aspect of performance drivers with a look at Associate interactions.

The first section walks through a series of basic metrics in store location analytics. Starting with where shoppers went, it shows increasingly sophisticated views that cover what drew shoppers into the store, how much time shoppers spend in different areas, and which parts of the store shoppers engaged with most often:

retail analytics: measuring store efficiency and conversion with DM1

The next section focuses on measures of store efficiency and conversion. It shows how you can track basic conversion metrics, analyze how proximity to the cash-wrap drives impulse conversion, and analyze unsuccessful visits in terms of exit and bounce points.

DM1 Layout Overview Video

Going from what to why is probably the hardest task in behavioral analytics. And in the 3rd section, I do a quick dive into a set of Associate metrics to show how they can help that journey along. Understanding where associates ARE relative to shoppers (this is where the geo-spatial element is critical), when and where Associates create lift, and whether your deployment of Associates is optimized for creating lift can be a powerful part of explaining shopper success.

retail analytics with dm1 - analyzing associate performance, STARs and lift with DM!

The whole video is super-quick (just 3 minutes in total) and unlike most of what I’ve done in the past, it doesn’t require audio. There’s a brief audio introduction (about 15 seconds) but for the rest, the screen annotations should give you a pretty good sense of what’s going on if you prefer to view videos in quiet mode.

I know you’re not going to learn in-store measurement in 3 minutes. And this is just a tiny fraction of the analytic capability in a product like DM1. It’s more of an amuse bouche – a little taste –  to see if you find something enjoyable and interesting.

I’m going to be working through a series of videos intended to serve that purpose (and also provide instructional content for new DM1 users). As part of that, I’m working on a broader overview right now that will show-off more of the tools available. Then I’m going to work on building a library of instructional vids for each part of DM1 – from configuring a store to creating and using metadata (like store events) to a deep-dive into funnel-analytics.

I’d love to hear what you think about this initial effort!

Check it out:

Building a Career Around In-Store Measurement and Location Analytics

Over the nearly two decades I spent in digital analytics, I did a lot of selling. More than I ever wanted to. But during that time, I saw the process of selling digital analytics transformed. When I started, way back in the ‘90s, selling web analytics was evangelical. I had to convince potential clients that the Web mattered. Then I had to convince them that analytics mattered to the Web. If I got that far, I just to convince them that I was the right person to buy analytics from. But since there were only about five other people in the world doing it, that last part wasn’t so hard!

Over time, that changed. By 2005, most companies didn’t need to be convinced that the Web mattered. The role of analytics? That was still a hard sell. But by around 2012, selling digital analytics was no longer evangelical. Everyone accepted that analytics was a necessary part of digital. The only question, really, was how they would provision it.

I didn’t miss the evangelical sell. It’s a hard path. Most people are inherently conservative. Doing new stuff is risky. Most organizations are pretty poor at rewarding risk-taking. It’s great to suggest that analytics is powerful. That it will do the organization good. But for someone to take a risk on a new technology and process, there needs to be real upside. Think of it this way – just as VC’s expect out-sized returns when they invest hard-cash in risky startups, so do decision-makers who are willing to go outside the well-trodden path.

Well, with Digital Mortar, I’m right back in the evangelical world. I have to sell people on the value of in-store customer measurement and analytics – and often I have to do it within environments that are significantly disrupted and challenged. So here’s the question I ask myself – what’s in it for an influencer or a decision-maker?

I think that’s a surprisingly important question and one that doesn’t often get asked (or answered).

If you’re thinking about in-store measurement and analytics, here’s the personal questions I’d be asking if I were you (and my best guess at answers):

1. Is there a future career in this stuff?

There was a time when understanding how to create digital analytics tags was a really critical skill. That day has passed. Tagging is now a commodity skill often handled by offshore teams. In technology and analytics, in-demand skills come and go. And it’s critically important to keep building new skills. But which skills? Because there’s always lots of possible choices and most of them won’t end up being very important.

It’s pretty obvious that I believe location analytics has a big future or else I wouldn’t have started Digital Mortar. Here’s why I think this stuff matters.

I saw how compelling analytics became in the digital world. With increasing competition and interaction between digital and physical experiences, it’s just implausible to believe that we’ll continue in a world where online experiences are deeply quantified and physical experiences are a complete mystery. Every digital trend around customer centricity, experimentation and analytics is in-play in the physical world too – and all of them drive to the need for location analytics.

The thing is, measurement creates its own demand. Because once people understand that you can measure something, they WANT to know.

It will take a while. Change always does. But I have no doubt that in a few years, measurement of the physical customer journey will be well on its way to being the kind of table-stakes must-have that digital analytics is in the web world. That means new roles, new department, new jobs and new opportunities. Which brings me to…

2. Is there a real benefit to being an early adopter?

The people who got into digital analytics early carved out pretty admirable careers. Sure, they were a smart group, but in a new analytics domain, there is a real premium to early adoption. When that field starts to get traction, who gets to speak at Conferences? Who gets to write the books? It’s the early adopters. And if you’re the one speaking at conferences or writing the books, you get real opportunities to build a unique career. Being an early adopter of a technology that pans out is a huge win for your personal brand. It almost guarantees a set of terrific career options: leading a consultancy, having a cush job as an evangelist at a place like Google, getting recruited by a technology unicorn, or managing a large group at a premium company. All good stuff.

And by the way, it’s worth pointing out that this type of measurement isn’t limited to retail. You think resorts, arenas, and complex public spaces don’t need to understand the customer experience in their spaces? Location analytics won’t be in every industry. But it will be every WHERE.

But none of that stuff will happen unless you have some success.

3. Can I be successful right now?

How much success you need is easily exaggerated. Early adopters (and this is a good thing) are like fisherman. We mostly know how to tell a good story. But getting real success IS important. And fortunately, location analytics systems are good enough to do interesting measurement. The capture technologies have plenty of issues, but they work. And a platform like DM1 lets you do A LOT with the data. Best of all, if you’re already experienced with digital analytics, you know a bunch of what’s important about dealing with this data. That makes early adoption a little less frightening and a lot more likely to be successful.

There are real use-cases for this technology. Use-cases that have been hidden by the generally awful analytics capabilities of previously existing systems. This kind of measurement can identify and help solve line and queue management problems, answer questions around store and location design, resolve issues around staffing and associate optimization and feed better forecasting and allocation models, and drive powerful enhancements to customer CRM and personalization efforts.

4. How risky is it?

Middling. This stuff is still pretty new. But it’s starting to mature rapidly. The technology is getting better, the analytics software just got MUCH better, and the needs just keep growing. As with most analytics – the hard part is really organizational. Getting budget, getting authority, driving change – those are always the hardest tasks no matter how challenging things are on the data collection and analytics front. But no one’s ever seen this kind of data before. So the bar is incredibly low. When people have spent years living with hunch, intuition and door-counting as their sole metrics, you don’t have to provide world-beating analytics to look like a star.

5. Is it interesting (because no one wants to spend their life doing boring stuff)?

Yep. This stuff is deeply fascinating. Customer experience has long been one of the most interesting areas in analytics. People are great to study because their behavior is always complex. That makes the analytics a challenge. And because its people and behavior and the real-world, the problem set keeps morphing and changing. You’re not stuck analyzing the same thing for the next ten years.

Even better, identifying problematic customer behaviors is the table-set for actual business change. Once you’ve found a problem, you have to find a way to fix it. So the analytics drives directly into thinking about the business. I like that a lot. It means there’s a purpose to the measurement and the opportunity to brainstorm and design solutions not just analyze problems. If you enjoy doing digital analytics (or have always thought you might), this is an even richer and more complex set of analytic problems.

Yeah. It’s fun.

Which brings me to the bottom line. Risk is risk. A lot of businesses fail. A lot of technologies don’t take off. But I’m pretty confident that in-store journey measurement and location analytics will become a significant discipline in the next few years. If I’m right, there will be real dividends to being an early adopter. Both for the companies that do it and the people who drive it. And along the way there’s some fascinating analytics to be had and a whole bunch of really interesting stuff to learn. That doesn’t seem like such a bad deal.

The Myth of the Single KPI for Testing

Continuous Improvement through testing is a simple idea. That’s no surprise. The simplest, most obvious ideas are often the most powerful. And testing is a powerful idea. An idea that forms and shapes the way digital is done by the companies that do it best. And those same companies have changed the world we live in.

If testing and continuous improvement is a process, analytics is the driver of that process; and as any good driver knows, the more powerful the vehicle, the more careful you have to be as a driver. Testing analytics seems so easy. You run a test, you measure which worked better. You choose the winner.

It’s like reading the scoreboard at a football game. It doesn’t take a lot of brains to figure out who’s ahead.

Except it’s usually not that easy.

Sporting events just are decided by the score. Games have rules and a single goal. Life and business mostly don’t. What makes measuring tests surprising tricky is that you rarely have a single unequivocal measure of success.

Suppose you add a merchandising drive to a section of your store or on the product detail page of your website. You test. And you generate more sales of that product.

Success!

Success?

Let’s start with the obvious caveat. You may have generated more sales, but you gave up margin. Was it worth it? Usually, the majority of buyers with a discount would have bought without one. Still, that kind of cannibalization is fairly easy to baseline and measure.

Here’s a trickier problem. What else changed? Because when you add a merchandising drive to a product, you don’t just shift that product’s buying pattern. The customer who buys might have bought something else. Maybe something with a better margin.

To people who don’t run tests, this may come as a bit of surprise. Shouldn’t tests be designed to limit their impact so that the “winner” is clear? ‘

Part of a good experimental design is, indeed, creating a test that limits external impacts. But this isn’t the lab. Limiting the outside impact of a test isn’t easy and you can  never be sure you’ve actually succeeded in doing that unless you carefully measure.

Worse, the most important tests usually have the most macro-impact. Small creative tests can often be isolated to a single win-loss metric. Sadly, that metric usually doesn’t matter or doesn’t move.

If you need proof of that, check out this meta-study by Will Browne & Mike Jones (those names feel like generic test products, right?) that looked at the impact of different types of test. Their finding? UI changes of the color and call-to-action type had, essentially, zero impact. Sadly, that’s what most folks spend all their time testing. (http://www.qubit.com/sites/default/files/pdf/qubit_meta_analysis.pdf)

If your test actually changes shopper behavior, believe me, there will be macro impacts.

It’s usually straightforward to measure the direct results of a store test. It’s often much harder to determine the macro impact. But it’s something you MUST look at. The macro impact can be as or more important than the direct impact. What’s more, it often – I’ll say usually – runs in the opposite direction.

So if you fail to measure the macro impact of a store test and you focus only on the obvious outcome, you’ll often pick the wrong result or grossly overstate the impact. Either way, you’re not using your analytics to drive appropriately.

Of course, one of the very real challenges you’ll face is that many tools don’t measure the macro impact of tests at all. In the digital world, the vast majority of dedicated testing tools require you to focus on a single KPI and provide absolutely no measurement of macro impacts. They simply assume that the test was completely compartmentalized. That works okay for things like email testing, but it’s flat-out wrong when it comes to testing store or website changes.

If your experiment worked well enough to change a shopper’s behavior and got them to buy something, the chances are quite good that it changed more than just that behavior. You may have given up margin. You likely lost some sales elsewhere. You almost certainly changed what else in the store or the site the shopper engaged with. That stuff matters.

In the store world, most tools don’t measure enough to give you even the immediate win-loss results. To heck with the rest of the story. So it can tempting, when you first have real measurement, to focus on the obvious: which test won. Don’t.

In some of my recent posts, I’ve talked about the ways in which DM1 – our store testing and measurement platform – lets you track the full customer journey, segmentfunnel and compare. Those capabilities are key to doing test measurement right. They give you the ability to see the immediate impact of a test AND the ways in which a change affected macro customer behavior.

You can see an example of how this works (and how important that macro behavior is in store layout) in this DM1 video that focuses on the Comparison capabilities of the tool.

https://www.youtube.com/watch?v=lbpaeSmaE74&t=13s

It’s the right way to use all that power a store testing program can provide.

Store Testing & Continuous Improvement

Continuous improvement is what drives the digital world. Whether applied as a specific methodology or simply present as a fundamental part of the background against which we do business, the discipline of change and measure is a fundamental part of the digital environment. A key part of our mission at Digital Mortar is simply this: to take that discipline of continuous improvement via change and measurement and bring it to stores.

Every part of DM1 – from store visualizations to segmentation to funnel analytics – is there to help measure and illuminate the in-store customer journey. You can’t build an effective strategy or process for continuous improvement without having that basic measurement environment. It provides the context that let’s decision-makers talk intelligently about what’s working, what isn’t and what change might accomplish.

But as I pointed out in my last post, some analytic techniques are particularly useful for the role they play in shaping strategy and action. Funnel Analysis, I argued, is particularly good at focusing optimization efforts and making them easily measurable. Funnels help shape decisions about what to change. Equally important, they provide clear guidance about what to measure to judge the success of that change. After all, if you made a change to improve the funnel, you’re going to measure the impact of the change using that same funnel.

That’s a good thing.

One of the biggest mistakes in enterprise measurement (and – surprisingly – even in broader scientific contexts) is failing to commit to your measurement of success when you start an experiment. It turns out that you can nearly always find some measure that improved after an experiment. It just may not be the right measure. If folks are looking for a way to prove success, they’ll surely find it.

Since we expect our clients to use DM1 to drive store testing, we’ve tried to make it easy on both ends of the process. Tools like funnel analysis help analysts find and target areas for improvement. At the other end of the process, analysts need to be able to easily see whether changes actually generated improvement.

This isn’t just for experimentation. As an analyst, I find that one of the most common tasks I have do is compare numbers. By store. By page. By time-period. By customer segment. Comparison provides basic measurement of change and context on that change.

Which makes comparison the core capability necessary for analyzing store tests but also applicable to many analytics exercises.

Though comparison is a fundamental part of the analytic process, it’s surprising how often it’s poorly supported in bespoke analytics tools. It took many years for tools like Adobe’s Workspace to evolve – providing comprehensive comparison capabilities. Until quite recently in digital analytics, you had to export reports to Excel if you wanted to lay key digital analytic data points from different reports side-by-side.

DM1’s Comparison tool is simple. It’s not a completely flexible canvas for analysis. It just takes any analytic view DM1 provides and allows you to use it in a side-by-side comparison. Simple. But it turns out to be quite powerful in practice.

Suppose you’re running a test in Store A with Store B as a control. DM1’s comparison view lets you lay those two Stores side-by-side during the testing period and see exactly what’s different. In this view, I’ve compared two similar stores by area looking at which areas drove the most shopper conversions:

Retail Analytics and Store Testing: Store Comparison in DM1

You can use ANY DM1 visualization in the Comparison. The funnel, the Store Viz or traditional reports and charts. In this view, I’ve compared the Shopper Funnel around a single merchandising category at two different stores. Not only can I see which store is more effective, I can see exactly where in the funnel the performance differences occur:

Retail Analytics and Store Testing: Time Comparison

Don’t have a control store? If you’re only measuring the customer journeys in a single store or if your store is a concept store, you won’t have another store to use as a control. No problem, DM1’s comparison view lets you compare the same store across two different time periods. You can compare season over season or consecutive time periods. You don’t even have to evenly match time periods. Here I’ve compared the October Funnel to Pre-Holiday November:

Retail Analytics and Funnels: Store Testing

Store and Date/Time are the most common type of comparison. But DM1’s comparison tool lets you compare on Segments and Metrics as well. I often want to understand how a single segment is different than other groups of visitors. By setting up a segmentation visualization, I can quickly page through a set of comparison segments while holding my target group constant. In the first screen, I’ve compared shoppers interested in Backpacks with shoppers focused on Team Gear in terms of how effective interactions with Associates are. With one click, I can do the same comparison between Women’s Jacket shoppers and Team Gear:

Funnel Analytics and Store TestingStore Analytics Comparison: Store Testing Segments

The ability to do this kind of comparison in the context of the visualizations is unusual AND powerful. The Comparison tool isn’t the only part of DM1 that supports comparison and contextualization. The Dashboard capability is surprisingly flexible and allows the analyst to put all sorts of different views side by side. And, of course, standard reporting tools like Charts and Table provide significant ways to do comparisons. But particularly when you want to use bespoke visualizations like Funnels and DM1’s store visualizations, having the ability to lay them side by side and quickly adjust metrics and view parameters is extraordinarily useful.

If you want to create a process of continuous improvement in the store, having measurement is THE essential component. Measurement that can help you identify and drive potential store testing opportunities. And measurement that can make understanding the real-world impact of change in all its complexity.

DM1 does both.

Click here to sign-up for a Demo of DM1.

Analyzing the In-Store Journey as a Funnel with DM1

Visualizing the customer journey in the context of the store is the foundation for analyzing in-store data. The metrics and the store context provide a framework for translating customer measurement data into something that is immediately understandable as a shopper’s journey. But visualizing information is just the first step in making it actionable. Understanding the data is, of course, essential. But you can understand data quite well and still have no idea what to do with it. In fact, that’s a problem we see all the time with analytics. And while it’s a problem that no technology solution can solve entirely (since there are always business and organizational issues to be tackled),  there are analytic and reporting techniques that can really help. We’ve built a number of them into DM1, starting with in-store funnel analytics.

The idea behind a conversion funnel is simple. The customer journey is chopped up into discrete steps based on increasing likelihood to purchase. If we analyze the journey by those discrete steps, we can work to optimize the flow from one step to the next. Improve the flow between any funnel step and the next, and the chance is excellent that you’ll improve the overall funnel conversion as well. Funnels give you a specific place to start. They let you figure out which parts of the overall customer journey are already working well and which aren’t. They let you focus on specific areas with the confidence that if you can improve performance you’ll make a significant difference. And they make it possible to easily measure success. All you have to measure is the number of people moving from one step to the next.

Funnels are THE paradigm for analytics and optimization in eCommerce. In fact, it was largely on their ability to help merchants understand and improve eCommerce funnels that digital analytics solutions first gained traction. And to this day, eCommerce testing and analytics practitioners almost always work by breaking down the customer journey into funnel steps and then working to optimize each step. While the measurement of funnels is itself interesting, I think the real value in funnel analysis is the process it supports. That ability to target specific aspects of the journey, figure out which ones are the most broken, and then test possible improvements is at the heart of so much of the continuous improvement that makes digital players successful.

One of our big goals with Digital Mortar is to bring the in-store funnel paradigm and the discipline of continuous improvement to the store. DM1 delivers on the technology and analytic part of that program.

With DM1, you can start a funnel at any place in the store and at any stage in the customer journey. But the most natural place to start is with a shopper entering the store. As you can see, DM1 lets you choose any area of the store you’ve defined and lets you pick from a range of engagement metrics.

Retail Analytics - In-Store Shopper Funnel DM1

 

Nearly 84 thousand shoppers entered the store in October. Since that’s where the measurement starts, this first step of the funnel doesn’t have any fallout. Everyone I measured, by definition, entered the store. It’s worth noting – and I get asked this a lot – that you CAN track Retail Analytics - In-Store Shopper Funnelpass-by traffic if you setup the measurement system appropriately. Doing so allows you to extend the funnel outside the store!

I could build a store-wide funnel, looking at conversion across the whole store. But it’s usually more interesting and actionable to focus a bit. So my funnel is going to focus on a specific section of the store – Team Gear.Retail Analytics - In-Store Shopper Funnel Linger and Consideration

Adding “Visits to Team Gear” to the funnel, I can see that around 15 thousand shoppers – about 18% of store visitors – visited Team Gear. It took the average visitor about 2 minutes before entry to reach Team Gear. Which makes sense because this area is pretty front of store

But one of the real complexities to in-store measurement is that since shoppers are navigating a physical environment they often pass-thru areas without being interested in them. That doesn’t happen much in digital.

I want to know how many people SHOPPED in Team Gear out of the folks who had the opportunity. And I caRetail Analytics - In-Store Shopper Funnel falloutn see that by selecting Lingers as my metric in the next funnel step. These last two steps illustrate a powerful metric in store measurement that’s simply never been available before. Stores have been able to measure conversion (checkouts/door entries) at the macro level, but at the area level this gets reduced to sales per square foot.

That isn’t reflective of the real opportunity a square foot provides. By measuring where shoppers actually WENT and where they SHOPPED, we have a real KPI of how well a section is performing given its opportunity.

Only about 1 in 7 shoppers who passed through Team Gear actually Shopped there. That’s a problem I’d probably want to tackle.

From here, I can add Fitting Room and CashWrap to the funnel. At every step along the way I can see how many shoppers I’m losing from the total opportunity. I can also see how much time is passing and how many stops the shopper made in-between.

In the end, I have a customer funnel for Team Gear that runs from Store Entry to Cash-Wrap that looks like this:

Retail Analytics - In-Store Shopper Funnel and Funnel Analytics

Any start place. Any level of engagement. Any steps in between. DM1 builds the funnels you need to support analytics and testing.

Pretty cool.

There’s no doubt in my mind that the picture of the shopper journey that DM1 provides drives better understanding. But as I said earlier, analytics isn’t improvement. It’s a way to drive improvement.

The funnel paradigm works less because of it’s analytics potential than because of the process it helps define. In-store funnels focus optimization efforts and make them easily measurable. Whether I tackle the step with the highest abandonment rate, try to build the initial opportunity, or attempt to remove distractions between key steps, funnel analysis helps guide my reasoning about what to test in the store and provides a fully baked way to measure whether store changes drove the desired behavior.

Retail Analytics: Store Visualization and DM1

Location analytics isn’t really about where the shopper was. After all, a stream of X,Y coordinates doesn’t tell us much about the shopper. The interesting fact is what was there – in the store – where the shopper was. To answer most questions about the shopper’s experience (what they were interested in, what they might have bought but didn’t, whether they had sales help or not, and what they passed but didn’t consider), we have to understand the store. In my last post, I explained why the most common method of mapping behavior to the store – heatmaps – doesn’t work very well. Today, I’m going to tackle how DM1 does it differently and (in my humble opinion) much better.

Here are the seven requirements I listed for Store Visualization and where and why heatmaps come up short:

Store Visualization: Heatmaps and retail analytics

Designing DM1’s store visualization, I started with the idea that its core function is to represent how an area of the store is performing. Not a point. An area. That’s an important distinction. Heatmaps function rather like a camera exposure. There’s an area down there somewhere of course – but it’s only at the tiny level of the pixel. That’s great for a photograph where the smaller the pixel the better, but analytically those points are too small to be useful. Besides, store measurement isn’t like taking a picture. The smaller the pixel the more accurate the photo. But our measurement capture systems aren’t accurate enough to pinpoint a specific location in the store. Instead, they generate a location with a circle of error that, depending on the system being used, can actually be quite large. It doesn’t make a lot of sense to pretend that measurement is happening at a pixel location when the circle of error on the measurement is 5 feet across!

This got me thinking along the lines of the grid system used in classic board games I played as a kid. If you ever played those games, you know what I’m talking about. The board was a map (of the D-Day beaches or Gettysburg or all of Europe) and overlaid on the map was a (usually hexagonal) grid system that looked like this:

BoardGame

Units occupied grid spaces and their movement was controlled by grid spaces. The grid became the key to the game – with the map providing the underlying visual metaphor. This grid overlay is obviously artificial. Today’s first person shooter games don’t need or use anything like it, but strategy games like Civ still do. Why? Because it’s a great way to quantize spatial information about things like how far a unit can move or shoot, the distance to the enemy, the direction of an attack, the density of units in a space and much, much more.

DM1 takes this grid concept and applies it to store visualization. Picture a store:

store journey analytics

Now lay a grid over it:

Visualizing Store Data

And you can take any place the shopper spends time and map it to a grid-coordinates:

Mapping customer data to the store

And here’s where it really gets powerful. Because not only can you now map every measurement ping to a quantifiable grid space, you can attach store meta-data to the grid space in a deterministic and highly maintainable way. If we have a database that describes GridPoint P14 as being part of Customer Service on a given day, then we know exactly what a shopper saw there. Even better, by mapping actual traffic and store meta-data to grid-points, we can reliably track and trend those metrics over time. No matter how the shape or even location of a store area changes, our trends and metrics will be accurate. So if grid-point P14 is changed from Customer Service to Laptop Displays, we can still trend Customer Service traffic accurately – before, after and across the change.

That’s how DM1 works.

Here’s a look at DM1 displaying a store at the Section level:

Retail Analytics: Store Visualization in DM1

In this case, the metric is visits and each section is color-coded to represent how much foot traffic the section got. These are fully quantified numbers. You can mouse over any area and get the exact counts and metrics for it. Not that you don’t need a separate planogram to match to the store. The understanding of what’s there is captured right along side the metric visualization. Now obviously, Section isn’t the grid level for the store. We often need to be much more fine-grained. In DM1, you can drill-down to the actual grid level to get a much more detailed view:

Retail Analytics: Store Detail in DM1

How detailed? As detailed as your collection system will support. We setup the grid in DM1 to match the appropriate resolution of your system. You’re not limited to drilling down, though. You can also drill up to levels above a Section. Here’s a DM1 view at the Department level:

Retail Analytics: Store Meta Data and Levels in DM1

In fact, with DM1, you have pretty much complete flexibility in how you describe the store. You can define ANY level of meta-data for each grid-point and then view it on the store. Here, for example, is where promotions were placed in the store:

Retail Analytics: Store Merchandising Data Overlay

DM1 also takes advantage of the Store Visualization to make it easy to compare stores – head to head or the same store over time. The Comparison views shows two stores viewed (in this example) at the Section Level and compared by Conversion Efficiency:

Retail Analytics: Store Comparison in DM1

It takes only a glance to instantly see which Sections perform better and which worse at each store. That’s a powerful viz!

In DM1, pretty much ANY metric can be mapped on the store at ANY meta-data level. You can see visits, lingers, linger rate, avg. time, attributed conversions, exits, bounces, Associate interactions, STARs ratio, Interaction Success Rate and so much more (almost fifty metrics) – mapped to any logical level of the store; from macro-levels like Department or Floor all the way down the smallest unit of measurement your collection system can support. Best of all, you define those levels. They aren’t fixed. They’re entirely custom to the way you want to map, measure and optimize your stores.

And because DM1 keeps an historical database of the layouts and meta-data over time, it provides simple, accurate and easily intelligible trending over time.

I love the store visualization capability in DM1 and I think it’s a huge advance compared to heat-maps. As an analyst, I can tell you there’s just no comparison in terms of how useful these visualizations are. They do so much more and do it so much better that it hardly seems worth comparing them to the old way of doing things. But here it is anyway:

DM1 Retail Analytics Store Visualization Advantages

DM1’s store visualization is one powerful analytic hammer. But as good as they are, this type of store visualization doesn’t solve every problem. In my next post, I’ll show how DM1 uses another powerful visual paradigm for mapping and understanding the in-store funnel!

[BTW – if you want to see how DM1 Store Visualization actually works, check out these live videos of DM1 in Action]