Guide

Compare audiences without losing the context

A useful comparison names the groups, shows the counts, and stays honest about what might explain the gap.

The useful part

Keep these three things in mind.

  • Define the audience and date range before comparing.
  • Keep sample sizes and overlapping groups visible.
  • Treat a difference as a question to investigate, not proof of cause.

How this piece was prepared. An original practical framework. Examples illustrate a method; they are not measured product results.

Begin with a reason to compare

“What is different about our customers?” is too large a starting point. Choose a comparison that could inform a specific piece of work. A store considering separate welcome and replenishment messages might compare first-time buyers with returning buyers on the reason for today’s purchase.

Write the intended use before opening filters. This keeps an interesting chart from quietly changing the question. If the goal is to understand replenishment, comparing product categories may be useful later, but it should be a named follow-up rather than an unnoticed change to the original task.

Define both groups in plain language

Record exactly who belongs on each side. “Returning” might mean a customer with an earlier completed order, while “first-time” means someone without one under the definition used by your data. Check that definition rather than relying on a familiar label.

Use the same collection dates and question version where possible. Note whether the groups overlap. Comparing “all buyers” with “returning buyers” includes some of the same people on both sides; it is a different comparison from first-time versus returning. Also choose whether your unit is a customer, an order, or a response. These are not interchangeable.

Read counts beside percentages

Consider a deliberately invented example: 12 of 40 first-time respondents and 30 of 200 returning respondents mention a particular reason. The shares are 30% and 15%, a difference of 15 percentage points. Yet more returning respondents selected the answer in absolute numbers.

Neither view cancels the other. The share describes how common the answer is within each responding group. The count describes how many observed answers you have. Keep both visible, and label the denominator. With a multi-select question, people can contribute to several answer counts, so the shares need not add to 100%.

Keep missing answers in the picture

Find out how many eligible people did not answer the question, if that information is available. Do not quietly turn a response-only denominator into a claim about every buyer. If one group encountered a different survey path or had a different opportunity to respond, that can affect what you are comparing.

Keep “other,” “not sure,” and unavailable data distinct when they mean different things. A customer declining to name a reason is not the same as a system failing to attach an order attribute. Before explaining a difference, check whether a filter has simply removed more records from one side.

Look for alternative explanations

First-time and returning buyers can also differ in what they buy, when they shop, which offer they saw, and how much they spend. An observed gap does not isolate customer history as its cause. Name a plausible alternative explanation before deciding what to do.

A useful follow-up is to repeat the comparison within one relevant product category or a consistent period. Keep that follow-up limited and record it. Searching through many small slices until something looks dramatic makes it easy to overstate an unstable pattern. There is no universal response count that makes every comparison trustworthy.

Write a finding another person can inspect

Use a short finding with four parts: the question, the exact groups, the observed shares and counts, and the limit on interpretation. Finish with a proposed action that matches the evidence. “Review replenishment wording for returning buyers” is a narrower commitment than rebuilding all retention marketing.

Save the filters and the date of the comparison so a colleague can reproduce it. If the evidence is sparse, write down what additional observation would change your view. A comparison earns its place in the workflow when it helps you choose a proportionate next step, including the choice to wait.

Sources & method

An original practical framework. Examples illustrate a method; they are not measured product results.

This piece presents our own decision framework, rather than a report of independent product testing.

Sources checked Sep 6, 2026. Product capabilities can change; verify the current documentation before making a commitment.

Published by Pixel & Shelf. Prepared with AI assistance, with claims checked against the linked sources.

Our editorial approach Suggest a correction ↗

Keep exploring

Another useful perspective.

Explore the library

Keep a useful idea close

Your reading list.
Your next good question.

Save an article for later, or follow Cartweather in your feed reader. No algorithm between you and the next edition.