Browse all articles tagged with #imports.
A developer's sample address appears in a real campaign audience. It might be harmless, or it might belong to somebody outside your team. Treat test data as a source that needs clear boundaries.
An old contact file is uploaded for a new campaign, and previously unsubscribed addresses become active. The import treated list membership as a fresh subscription decision.
Two addresses look identical on screen, but one fails validation. Before blaming the verifier, inspect the characters around the address rather than only the visible letters.
Your list contains an address called Email or Email Address. That is a useful warning that the importer did not agree with the file about its header row.
One contact has a company name containing a comma. After import, their email appears in the next column and every field after it is wrong. The list is not necessarily corrupt; the parser may be too simple.
The address column imports correctly, but names arrive as broken characters. Do not run a global find-and-replace on the contact list. First establish how the file was encoded and how it was opened.