Namespace result identifiers before joining source tables — what should the operator record?
A native identifier can be unique within one context without being globally unique. Combining tables under a bare id column can merge unrelated rows and spread the error into exports. Define a context-qualified local key before joining, preserving the original identifier exactly as it was returned.
Prevent identical native strings from colliding across different source contexts.
List the actual native identifier and source context columns available in each input; leave undocumented identifier meanings explicitly unresolved. An id column in an account table and one in a post table may inhabit different namespaces even under the same platform label; inventory object type as well.
Tell downstream users which fields define identity and which remain descriptive, ensuring future imports apply the same namespace rule. Recipients should receive the namespace contract with the table, since a later convenience export that drops context can recreate the exact collision the current operation prevented.Inspect identity fields
List the actual native identifier and source context columns available in each input; leave undocumented identifier meanings explicitly unresolved. An id column in an account table and one in a post table may inhabit different namespaces even under the same platform label; inventory object type as well.
Define the qualified key
Use separate context and native_id fields, or an unambiguous encoded pair, rather than concatenating values with a separator that may already occur. Separate columns avoid ambiguous delimiter parsing; if encoding a composite key, document how embedded separator characters are escaped and tested through export and reimport.
Test collision fixtures
Create labeled examples with the same native string under two contexts and confirm the join keeps two distinct evidence objects. A fixture native_id 42 under context A and context B should remain two records, without implying that those fixture contexts represent actual retrieved evidence.
Review ambiguous joins
Inspect rows previously merged on bare identifiers and split unsupported matches through a documented correction revision. When correcting a collision, trace dependent joins and exports so splitting the primary table does not leave a false relationship preserved in a downstream artifact.
Publish the key contract
Tell downstream users which fields define identity and which remain descriptive, ensuring future imports apply the same namespace rule. Recipients should receive the namespace contract with the table, since a later convenience export that drops context can recreate the exact collision the current operation prevented.
Keep the boundaries clear.
- Prevent identical native strings from colliding across different source contexts.
- Operational record: Inspect identity fields. 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.