Separate requested, returned and admitted membership counts — what should the operator record?
A research workflow can request a target, receive a smaller set and admit only part of that set into a checked table. Those numbers answer different questions. Keep them separate in the ledger so a release summary cannot silently promote returned records into a population estimate or conceal a requested-count shortfall.
Keep operational counts tied to distinct stages rather than treating one number as total available supply.
Use requested_count, received_row_count, unique_returned_key_count and admitted_key_count with explicit meanings. Requested count comes from the brief, while the other values must be computed from actual permitted receipts and validation output, not filled from expectations.
Attach count_basis and artifact_revision to every reported value. If the source supplies no supported total, leave available_population unknown rather than equating it with a page limit, a local cache size or the accepted set's current membership.Define count stages
Use requested_count, received_row_count, unique_returned_key_count and admitted_key_count with explicit meanings. Requested count comes from the brief, while the other values must be computed from actual permitted receipts and validation output, not filled from expectations.
Identify the counting object
State whether keys represent posts, accounts, links or observations. A flattened relationship table can have several rows per object; its physical row count must not replace a distinct-object count merely because both appear in the same spreadsheet.
Reconcile exclusions
List duplicate, invalid-key, withheld and out-of-scope dispositions separately. Their actual memberships should explain the difference between received rows and admitted keys without forcing categories to add up when a row can legitimately have several issue annotations.
Test a shortfall fixture
Create a clearly labeled example with a requested target larger than admitted membership. Ensure the resulting summary says the target is unmet and does not pad the list, infer missing identities or label the admitted subset all available records.
Publish stage-aware counts
Attach count_basis and artifact_revision to every reported value. If the source supplies no supported total, leave available_population unknown rather than equating it with a page limit, a local cache size or the accepted set's current membership.
Keep the boundaries clear.
- Keep operational counts tied to distinct stages rather than treating one number as total available supply.
- Operational record: Define count stages. Context badges do not certify access.
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-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.