Removing duplicates is a data-deletion decision. Decide what makes two records equivalent and which record should survive before using the cleanup command.
Define the duplicate key
Select the full record range and identify the columns that establish identity. Two purchases by the same customer are not duplicates merely because their customer IDs match.
Keep a recoverable copy and review duplicate candidates first. Include timestamps, versions, and status fields in that review when they determine which record is authoritative.
Use the intended columns
On a computer, choose Data > Data cleanup > Remove duplicates. Specify the columns to compare and whether the data has headers. Confirm the selection before applying the change.
Google notes that identical values with different letter case, formatting, or formulas can be treated as duplicates. Do not assume this operation enforces a case-sensitive identifier policy or preserves distinctions based only on presentation.
Verify the surviving records
Compare before-and-after counts and inspect each conflicting group that matters. Do not assume a generic duplicate-removal command implements a newest-record or most-complete-record policy. Establish that policy explicitly in your preparation.
Check associated fields and downstream totals after removal. If duplicates represented valid repeated events, restore them from the retained source rather than accepting a lower count as proof of cleanup success. Keep a removal log or reviewed candidate list when the process needs an audit trail. For recurring feeds, correct the source or import key policy so the next refresh does not recreate duplicates or erase valid history using an overly broad identity rule.
References
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.