Does an empty result mean no matches, or missing evidence?
Coverage is part of the answer, not a footnote. A query can return useful records while another source is unavailable or a later page remains unread. Keep the result's status, gaps and freshness with the data. This prevents a plausible summary from claiming a complete population that the underlying response never established.
Before summarizing this result, report the actual sources, selected accounts, freshness, partial or unavailable states, and any continuation cursor. Distinguish confirmed no matches from missing evidence. Keep those limits attached to every count.Read status before interpreting counts
Inspect the response's metadata and any coverage notes alongside the returned records. A useful partial result can still be an HTTP success. Distinguish a completed search with no allowed matches from a source that could not be reached or an operation that did not finish. Do not collapse those states into the same zero-valued metric.
Check population and freshness
Record which accounts, sources and time interval were actually inspected. Compare the record timestamps with the capture or observation time where those fields exist. A current request may return older retained evidence, and a small preview may represent only part of a saved result. Neither situation should be described as complete current coverage.
Separate access limits from pagination
A continuation cursor indicates more of an existing result may be available; it does not prove a source is broken or that missing rows were deleted. Conversely, no cursor does not establish platform-wide completeness. Read the actual coverage state and stated limits before deciding whether to continue, refresh deliberately or stop with a documented shortfall.
Carry gaps into the final brief
Report actual observed counts and list the conditions that restrict interpretation. If a requested source or relationship is unsupported, say so instead of swapping in easier data. Describe what additional evidence would be needed to answer the original question. The final conclusion must be no broader than the population and time window the response supports.
Keep the boundaries clear.
- HTTP 200 is not proof of complete source coverage.
- Unavailable and uninspected populations are not zero-match populations.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.