Normalize source links without collapsing distinct evidence objects — what should the operator record?
A source URL can contain identity-bearing path or query components as well as optional presentation information. Removing everything after a question mark is convenient but can merge distinct objects. Preserve the returned reference and define only the specific, justified normalization needed for the operational comparison being performed.
Preserve original URLs and justify each comparison-only normalization rule.
Keep returned_url unchanged and place any normalized comparison value in a distinct derived column. Record normalization_revision so a downstream table cannot mistake a locally shortened URL for the exact original link supplied by the response.
Describe the normalized field as a comparison aid for this workflow. Preserve original links for authorized verification, and do not claim that matching normalized URLs proves identical content, current accessibility or universal source identity across redirects.Separate raw and comparison URLs
Keep returned_url unchanged and place any normalized comparison value in a distinct derived column. Record normalization_revision so a downstream table cannot mistake a locally shortened URL for the exact original link supplied by the response.
Inspect component meaning
Identify which components actually distinguish source objects using current official behavior or inspectable references. If the role of a parameter is unknown, retain it rather than classifying it as disposable from its name or appearance alone.
Test noncollapsing behavior
Use labeled fixture URLs differing in a potentially identity-bearing component. Verify that the rule keeps them distinct unless a supported contract establishes equivalence, and include an unchanged original-reference assertion in the fixture output.
Review collisions explicitly
If several raw URLs map to one comparison value, list the affected permitted keys and assess the mapping before deduplicating anything. A collision can signal an overbroad rule rather than multiple references to one evidence object.
Publish scoped equivalence
Describe the normalized field as a comparison aid for this workflow. Preserve original links for authorized verification, and do not claim that matching normalized URLs proves identical content, current accessibility or universal source identity across redirects.
Keep the boundaries clear.
- Preserve original URLs and justify each comparison-only normalization rule.
- Operational record: Separate raw and comparison URLs. 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.