Skip to content

Account for overlap when combining returned evidence sets

Report union membership and duplicate overlap without adding page or branch counts as independent supply.

Guides

Account for overlap when combining returned evidence sets — what should the operator record?

Two returned tables may overlap heavily even when they come from different query branches or receipts. Adding their row counts can overstate the unique evidence retained. Build a qualified-key union and preserve branch membership flags so overlap remains visible without claiming that the union covers everything available on either source.

Practical operations check
Report union membership and duplicate overlap without adding page or branch counts as independent supply.
Record input revisions, identity grain and branch labels before combining rows. Keep each branch's requested scope and returned coverage, since equal schema does not mean the evidence came from comparable questions or had equivalent access conditions.
State that the union contains admitted records from the named returned sets. Do not describe a larger union as evidence of source population growth or a complete enumeration unless current authoritative evidence independently supports that stronger claim.
01 / Guides

Name the union inputs

Record input revisions, identity grain and branch labels before combining rows. Keep each branch's requested scope and returned coverage, since equal schema does not mean the evidence came from comparable questions or had equivalent access conditions.

02 / Guides

Construct membership flags

For each valid qualified key, retain present_in_left and present_in_right or an explicit branch list. Descriptive field conflicts need separate observations or a reviewed choice, not an arbitrary overwrite that loses which receipt supplied each value.

03 / Guides

Test overlapping fixtures

Use labeled inputs with shared and exclusive keys plus an invalid identifier. Check union membership and overlap separately, keeping the invalid row unresolved rather than assigning it to another key to make a neat combined table.

04 / Guides

Reconcile actual union size

Compare valid unique membership against the inputs and inspect duplicates within each branch. The sum of physical rows is not the union size, especially if repeated observations or flattened child links occur in either source representation.

05 / Guides

Publish bounded coverage

State that the union contains admitted records from the named returned sets. Do not describe a larger union as evidence of source population growth or a complete enumeration unless current authoritative evidence independently supports that stronger claim.

Keep the boundaries clear.

  • Report union membership and duplicate overlap without adding page or branch counts as independent supply.
  • Operational record: Name the union inputs. 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.

Know what social media shows about you.
Start with a question.

Get started
montage