Skip to main content

Marking Categories Not Applicable

When a data source genuinely doesn't apply to a client, mark it N/A on the Coverage page — the coverage score then reflects what actually matters, and the "gap" stops nagging you.

Written by Schae Lilley

When to use N/A

The coverage score counts connected sources against applicable ones. But not every source applies to every client: a digital-only brand has no retail data, plenty of DTC brands never sell on Amazon, a client might simply not run TikTok. Leaving those rows as open gaps makes the client's coverage look worse than it is — and buries the gaps you should chase.

Mark a source N/A only when it truly doesn't exist for the client's business. "We haven't gotten around to connecting it" is a gap, not an N/A.

How to mark a source N/A

  1. Open Coverage in the left rail of the Workflow product and pick the client.

  2. Find the unconnected source in the list.

  3. Choose Not applicable on that row.

  4. A confirmation appears — with an Undo button right there if you clicked the wrong row.

The row now shows marked N/A, and the coverage score recalculates immediately.

Why this keeps the score honest

N/A doesn't inflate the score by pretending a source is connected — it removes the source from the count entirely. A client with 6 of 9 sources connected and one genuine N/A becomes 6 of 8: the score now answers "how much of what applies is connected?" instead of "how much of everything imaginable is connected?" That's the number worth reporting, and it keeps the remaining gaps meaningful.

Undoing it

Marked something N/A that turns out to matter after all?

  1. Find the row on the Coverage page — N/A rows stay visible, marked with a dash.

  2. Choose undo on the row.

  3. The source returns to the applicable count as a normal gap you can act on.

Note: Live data always wins. If a source you marked N/A ever starts sending data — say the client launches on Amazon next year — it automatically counts as connected. An old N/A can never hide real data.

Note: A couple of sources can't be marked N/A by design. The client's order system is required — without a revenue anchor, scanning can't run at all — and MMM isn't a connection you manage, so it simply appears when a model exists.

Tip: Do an N/A pass when onboarding a client, right after setting metrics and goals. Ten seconds per irrelevant source, and the client's coverage score is trustworthy from day one.

Did this answer your question?