01Introduction

Inquiro

Location-based data visualization

Footfall Analysis shows how many people visit a location, and how often, over time. Mall advertising managers use it to set their ad prices and advise their advertisers. I designed the flow to create the report and the dashboard that shows the results. I was the only designer.

  • B2B
  • New product
  • Data visualization
  • Accessibility
The Footfall Analysis dashboard on a laptop, with a contents menu, the report summary and a chart of unique visitors per month

The problem

One of our clients wanted new ways to use our data. The data team made a Footfall report for them by hand, and the client liked it.

But a manual report does not scale. Every new request needed the data team’s time. Inquiro decided to turn it into a feature in our platform, so clients could create the report themselves.

Before, manual report: Client A, Client B, and Client A with a new time frame each go to the data team, who builds a report by hand every time.

Ideation

User story

“As an advertising manager, I want to see visitor traffic in the mall at different times, so I can set ad prices based on data and give better advice to advertisers.”

With this user in mind, I looked at what clients already knew. They already used the Audience Builder, so I reused its step-by-step flow and its dashboard layout. Clients did not have to learn a new tool, and developers could reuse the components.

  1. Step-by-step flow with a timeline, from the Audience Builder.

  2. Dashboard with a contents menu, from the Audience Dashboard.

  3. Download as PDF, JPG or CSV, from the same export.

User flow: from the Footfall Analysis section on the home page, step 1 select location, step 2 select time frame, summary, then the dashboard. From the dashboard, users can download visualizations as PDF or JPG, download data as CSV, or create a new report.
User flow. After the summary, users land on the dashboard and can download the report or create a new one.

The design

Data entry with a timeline

A timeline on the left shows the current step and the next steps. We planned to add more options to Footfall later, so the timeline needed room for more steps. Clients wanted to see their data by hour, day, week and month, so the time frame step supports all four.

Step 2, Select a Time Frame, with notes: the timeline shows where you are, and you can pick a time frame that is hourly, daily, weekly or monthly.

A dashboard that feels familiar

The dashboard uses the same layout as the Audience Dashboard, with a contents menu on the left. The top shows a summary of the report: location, time frame and number of snapshots.

The Footfall Analysis dashboard for Bayside Mall, with notes: create a new report or download it, a contents menu like the Audience Dashboard, and a summary of what the report covers.

Complex design decision

The visit frequency chart

One of the hardest charts to design was visit frequency: it shows how many people visited once, twice, and so on, each month. I combined the data from 6 charts into one, so users can compare the months side by side.

Before (manual report by data team)

Six small bar charts, one per month from January to June, each with ten bars in different bright colors.
Six charts, one per month, in high-contrast colors. Simplified recreation.

After

One stacked bar chart, percentage distribution of monthly visit frequency, with January to June side by side and ten visit groups from 1x to 10x and above.
One chart, with the months side by side. The pattern over time is easy to see.

The color problem

The chart has 10 visit groups, from 1x to 10x and above. There are not enough high-contrast colors for that many groups, and the data team’s usual high-contrast colors did not follow our brand.

  1. We asked users: which differences matter to you?

    The difference between 1x and 2x matters a lot. The difference between higher groups, like 4x and 5x, matters less.

  2. So what did I do?

    I used a dark and a light shade of the same hue, one after the other. Groups that sit next to each other are easy to tell apart, and the whole chart stays on brand.

Ten color swatches in five pairs: dark and light blue for 1x and 2x, dark and light cyan for 3x and 4x, dark and light green-teal for 5x and 6x, dark and light green for 7x and 8x, and light and dark yellow for 9x and 10x and above.
Five hues, each with a dark and a light shade.

Testing for color blindness

I checked the chart with color-blindness simulations. In every case, the difference that matters most to users, 1x vs 2x, stays easy to see, because each pair changes lightness, not only hue.

Protanopia (red-blind)

The visit frequency chart as seen with protanopia. Neighbor groups still differ in lightness.

Deuteranopia (green-blind)

The visit frequency chart as seen with deuteranopia. Neighbor groups still differ in lightness.

Tritanopia (blue-yellow blind)

The visit frequency chart as seen with tritanopia. Neighbor groups still differ in lightness.

Achromatopsia (no color)

The visit frequency chart in grayscale. Neighbor groups still differ in lightness.

Outcome

Footfall Analysis shipped, and mall advertising managers used it for their reports.

Now · self-serve

Now, self-serve: clients use Footfall Analysis in the Inquiro web app (1. select location, 2. select time frame, 3. review summary) and get a report.

Clients now create basic reports themselves, any time, without waiting for the data team.

Not yet for every need

Some clients asked for very complex charts that were not in the scope, so the data team still makes those by hand.

What I learned

Key takeaways

  • Reusing the Audience Builder flow made Footfall easier for clients to learn and faster for developers to build.
  • Asking users which differences matter to them helped me solve a color problem that had no perfect answer.
  • The data team’s six charts were accurate, but hard to compare. Putting the months side by side in one chart made the pattern easy to see.
  • Manual work can be a good test. The data team’s report proved clients wanted this before we built it.