An other category needs a reason and a review path
Use an additional intake category deliberately and retain enough context to understand the record. Putting every unfamiliar source into one bucket prevents meaningful source review.
A miscellaneous intake category can preserve legitimate records that do not fit a current source type. If left unexplained, it can also hide broken mapping, imported duplicates or weak definitions. Review it rather than treating it as a permanent catch-all.
A worked example
A hypothetical report places 30 records in other. Inspection finds event inquiries, a new form integration and test submissions. These require different classification and treatment; the total alone cannot describe a coherent acquisition channel.
How to apply it
- Record the available source provenance and why classification is unresolved.
- Separate tests, duplicates and legitimate new source types.
- Update mapping rules where justified while preserving original records.
What the result can establish
Do not force uncertain records into a preferred campaign to improve attribution. Explain material classification changes in comparisons. A smaller other category is useful when it reflects better understanding, not hidden exclusions.
Reference: Google Analytics: recommended events.
Supporting documentation
Google Analytics: recommended eventsGoogle Analytics: campaign URL parametersGoogle Analytics: measurement documentation