What should an empty analytics screen explain to a first-time user?

akelly

An empty report can mean several things: no data has arrived, a filter excludes all records, the user lacks permission, or the report has not been configured. A generic no results message leaves people guessing which problem they need to solve.

How would you distinguish these states without overwhelming a first-time user? What action should appear in each case, and when is sample data helpful? Suggestions for clear wording are welcome, especially where the screen should avoid implying that a sync is broken when it is simply still running.

dsanders

Use a specific heading and one next step for each state. For an active import, show that data is being prepared and provide its status. For restrictive filters, offer a clear-filters action. Permission issues should point to the appropriate owner without exposing restricted data. Keep optional sample data visibly separate from real results.