GetResponse duplicate contacts: where they cost money and where sends are deduplicated

Billing and sending are different questions

GetResponse treats each list independently for contact counting. The same email address in three separate lists can therefore occupy three contact positions. That billing behavior does not mean every newsletter is necessarily sent three times.

Newsletter sends can be deduplicated

GetResponse documents that a newsletter sent to multiple lists can avoid duplicate delivery to the same address. This protects the recipient experience, but it does not automatically remove the duplicate list memberships that affect contact counting.

Automation can behave differently

Automation and autoresponder behavior depends on contact identity within a list and workflow conditions. Do not assume that newsletter deduplication means every workflow treats duplicate list memberships as one record.

How to reduce duplicate-contact pressure

1. Export or inspect contacts across lists.
2. Find addresses that appear in more than one list.
3. Decide whether separate lists are operationally necessary.
4. Use tags or segments when one contact record can serve the same purpose.
5. Recheck the counted contact total before selecting a tier.

Migration warning

A direct migration that preserves every legacy list can reproduce years of duplicate structure. Clean the list model before estimating the new subscription cost.