Check input coverage before calling an integration feature adopted

A deployed integration feature may remain unused when its behavior depends on an optional field the upstream system never supplies. Verify deployment ancestry, then count retained input coverage over a bounded post-deployment cohort before claiming customer adoption. Report three separate states: code available, required inputs observed, and intended outcome confirmed. Zero stored inputs establishes missing coverage, but does not by itself distinguish upstream omission, ingestion loss, or deliberate non-use. For release gates and evidence comparisons, inspect a controlled end-to-end example before promising that the customer's full workflow is protected.

Applies when: a customer integration depends on optional payload fields. Keywords: API integration adoption optional fields payload coverage deployment verification