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.

Do deleted contacts still count toward this month's GetResponse bill?

They can. GetResponse assesses both the peak active subscriber count and the total contacts added during the billing month, even if some of those contacts are later deleted. Clearing a list before your invoice is calculated does not necessarily remove the effect of imports made earlier in the cycle.

In GetResponse's official billing example, an account with a 1,000-contact allowance replaces 900 existing contacts with 900 new ones and stays within the plan. But when it deletes that replacement batch and imports another 900 in the same month, it has added 1,800 contacts that month and moves above the purchased tier, despite the deletions. Actual charges depend on the account's plan, billing period, and applicable contact tier.

Before a migration or list cleanup: check both duplicate memberships across separate lists and the total number of contacts you expect to import during the same billing month. The calculator below estimates duplicate list memberships; it does not predict same-month add/delete billing or a final invoice. Confirm the live pricing tier before purchasing.

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.