First-party lists: bilingual collisions worth fixing first

Exports often contain the same person twice with different romanization paths. The duplication inflates frequency caps and embarrasses creative teams when messages double-send.

We prioritize deterministic normalization rules your ESP already supports, then layer fuzzy matching only where legal approves. The ordering matters: deterministic first reduces false merges.

We document edge cases—married name changes, corporate email aliases, and student seasonal addresses—so analysts know when to stop automating.

The output is a short collision log attached to each launch, proving the list was reviewed with named owners. That artifact helps when downstream teams question reach drops.