---
title: Revenue impact is unavailable
description: Understand why an issue can have occurrences and affected sessions before it has a defensible impact estimate.
slug: impact-unavailable
---

# Troubleshoot unavailable impact

An issue can be real and actionable before Dozenfold can estimate its commercial impact. Occurrences
and affected sessions are direct evidence; money additionally requires a defensible comparison.

## Read the reason

- **Collecting:** fewer than 30 affected or 100 clean entries can be compared so far. A wider window or more traffic helps.
- **Partial coverage:** some affected sessions lack a verified SDK–Pixel link, verified timing or a known uniform sampling rate. They stay visible but are not compared.
- **No conversion gap:** affected sessions converted at least as often as comparable clean sessions. There is no amount to show, but the issue can still hurt the experience.
- **Directional:** the gap is positive but its 95% interval still includes zero. An amount can be shown, clearly labelled as directional rather than measured.
- **More reference orders needed:** fewer than 20 complete clean orders exist in the store's main currency. The gap stays visible without an amount; no shop-wide average fills in.
- **Evidence unavailable:** the query could not return complete valid evidence. This is different from an empty comparison.

## What to do

Open the comparison details. Confirm that the SDK and Pixel link and purchase events are arriving.
Recent sessions need their full 30-minute follow-up, and session evidence refreshes about once a minute. A wider window can help with sample
size, but cannot repair missing linkage, unknown context or inconsistent sampling. For a query limit,
try a shorter window.

Continue triage with frequency, recency, regression state, journey position, affected environments,
friction and technical evidence. Do not interpret unavailable money as zero impact.
Read [Revenue impact methodology](/docs/revenue-impact) for the calculation boundary.