Reconcile export membership against its authorized input — what should the operator record?
A successful download proves that a file arrived, not that its rows match the intended table. Reconcile membership using actual identifiers, allowing for documented access-related omissions. The result should explain every difference without padding the export or restoring evidence that the current recipient is not allowed to receive.
Compare exported identifiers with the permitted source table before approving a research handoff.
Build an expected_key list from the currently authorized source table and record its revision, not a screenshot's approximate visible count. Expected membership must reflect current withholding decisions; otherwise reconciliation can wrongly label a deliberately absent identity as a download failure requiring restoration.
Record the checked output revision and actual accepted membership count; unresolved exceptions keep the handoff blocked or explicitly partial. Store the signoff beside the exact checked artifact reference so a recipient cannot mistake a later unvalidated download for the version that passed reconciliation.Declare expected membership
Build an expected_key list from the currently authorized source table and record its revision, not a screenshot's approximate visible count. Expected membership must reflect current withholding decisions; otherwise reconciliation can wrongly label a deliberately absent identity as a download failure requiring restoration.
Inspect the exported schema
Identify the actual exported key column and its platform context; do not assume every format preserves the same column spelling. If exported identifiers use a documented composite representation, preserve both native key and context when constructing comparison keys rather than stripping everything down to digits.
Compute set differences
Produce missing_keys, extra_keys and duplicate_keys as separate exception classes while preserving the original export for authorized inspection. Use set differences for membership and a separate multiplicity check for duplicates; equal file row counts can hide one missing key and one unintended extra.
Resolve omissions responsibly
Compare missing keys with returned access or withdrawal states before deciding whether another authorized export is appropriate. An omission explained by a supported withdrawal should remain withheld, with a nonidentifying operational reference when permitted, rather than reexported from an older cached file.
Sign off the exact file
Record the checked output revision and actual accepted membership count; unresolved exceptions keep the handoff blocked or explicitly partial. Store the signoff beside the exact checked artifact reference so a recipient cannot mistake a later unvalidated download for the version that passed reconciliation.
Keep the boundaries clear.
- Compare exported identifiers with the permitted source table before approving a research handoff.
- Operational record: Declare expected membership. 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.