Preserve context without collecting unnecessary personal data
Keep original capture source and relevant campaign context alongside the inquiry where available. Overwriting source with the last interaction can erase useful discovery evidence.
Useful intake context can include the source category, relevant campaign or landing page, time and the request itself. Collect what supports routing and measurement under the business’s privacy practices. More fields do not automatically create better intelligence.
A worked example
A hypothetical inquiry arrives with a campaign label but loses the requested service during a handoff. The team can attribute a visit but cannot route the request confidently. Preserving the selected service is more useful than adding unrelated enrichment fields.
How to apply it
- Identify the minimum context required for response and reliable source interpretation.
- Test field mapping across the actual intake path.
- Keep personal details out of public URLs and ordinary analytics parameters.
What the result can establish
Maintain source provenance and unknown values. Do not infer a precise acquisition history from one final-touch label. Retention and access decisions require the business’s own approved policies.
Reference: Google Analytics: campaign URL parameters.
Supporting documentation
Google Analytics: campaign URL parametersW3C WAI: validating formsNIST: AI Risk Management FrameworkGoogle Analytics: measurement documentation