How to Handle Duplicate Giveaway Entries
Choose a consistent identity key and apply the published entry rules before selection.
Published · Reviewed
How to Handle Duplicate Giveaway Entries
Follow the promotion’s stated rule: one entry per person, multiple permitted entries, or one per qualifying action. Apply that rule using a reliable identifier and keep an exception log rather than making ad hoc decisions from names alone.
Recommended process
- Identify the permitted entry frequency.
- Choose the most reliable available identity key.
- Normalize formatting without changing meaningful values.
- Review ambiguous collisions manually before the list is frozen.
Worked example
A promotion permits one entry per account. Two rows with the same display name but different account IDs remain separate; three rows with the same account ID are reduced to one according to the published rule.
What to check before using the result
- Names alone are weak identity keys.
- Do not invent a duplicate rule after entries close.
- Document how ambiguous records were handled.
How the random step is handled
Random Picker Tools uses window.crypto.getRandomValues() for browser-based selection. Integer results use rejection sampling to avoid modulo bias, and complete list orders use a Fisher–Yates shuffle. This addresses the software selection step; the organizer still controls eligibility, duplicate rules, consent, accessibility and any legal requirements.
Privacy note
Normal picking and shuffling happen in the browser. Use initials or non-sensitive identifiers when possible, avoid storing unnecessary source data, and create a share link only when temporary server storage is appropriate for the people represented in the list.