Summary

  • Mailchimp's current monthly Marketing plans count subscribed, unsubscribed and non-subscribed contacts towards the contact limit. Archived contacts are excluded.
  • Billing remembers the period's highest contact total. Archiving later cannot lower that recorded peak, and an import can bring contacts back without bringing back permission to market to them.

The reader has left. The email team has respected the decision. The finance team may still be paying for a place at the table.

That is a perfectly possible outcome under Mailchimp's contact rules. The unsubscribe button can work exactly as intended while the person's record remains in the population counted for billing. Permission to send a campaign and the price of keeping a contact available are separate products of the same database.

Mailchimp sells contact management as well as delivery. Its official guide to contact types includes subscribed, unsubscribed and non-subscribed contacts in the monthly limit. The last two groups cannot receive marketing emails or texts. Cleaned, pending and archived contacts do not count. The rules examined here concern current monthly Marketing plans; legacy paid plans dating from before May 15, 2019 have separate arrangements.

The distinction is plain once written down. Inside a company, it is easy to lose. A marketer says the reader has gone. An administrator sees a useful historical record. A budget holder hears that the list has been cleaned. All three statements can be reasonable while the billable population barely moves.

A memory with a monthly seat

Keeping a former subscriber's history can serve a purpose. An earlier purchase, a recorded preference or a past interaction may still matter to the business. The useful question is who can name that purpose, and why the record needs its present operating status.

“Keep it in case” is an unusually durable purchasing instruction. It has no expiry date, rarely names a budget owner and sounds prudent because nothing is being destroyed. A company can buy a great deal of indecision that way.

Mailchimp's archiving instructions describe a more deliberate choice. A contact moves out of the ordinary table into a separate archive, retaining data, including identifiable information in email and SMS reports. While archived, the contact cannot be edited or sent marketing, and is excluded from the monthly contact count.

Permanent deletion does something else: it irreversibly removes personal data. Asking someone simply to “make the list smaller” leaves a serious choice hidden inside a tidy operational request. A lower counter can accompany either preserved history or lost information.

There is also a boundary between audiences. A contact present in several audiences must be archived in each. Completing the task in one team's list does not complete it across the account. Departmental ownership can make a local success look like a global clean-up.

Those details give list maintenance an economic shape. The company is choosing which records it needs in an editable, current state, which histories can sit in the archive, and which data it intends to remove. A database administrator can execute the choice. The business still has to make it.

The bill has a better memory than the dashboard

Timing adds the sting. Mailchimp's additional-charges documentation bases monthly billing on the peak contact total during the billing period, the feature plan and the contact tier. Exceeding the contact or email-send limit can incur additional contact blocks. Block sizes, prices and associated sends depend on the plan and tier.

Take a deliberately hypothetical account. It reaches 10,000 contacts, then archives 4,000. The current population is 6,000. The peak for that period remains 10,000. Both numbers are correct; only one describes what is sitting in the list today.

The guide to removing inactive contacts explicitly says that archiving does not reduce an already established peak for the current period, although it can help with future billing. Even then, the plan, tier and subsequent usage determine the bill. A 40% reduction in contacts is not an automatic 40% reduction in money.

This makes the familiar instruction to clean up at month-end less powerful than it sounds. By then, the event that mattered may have happened. Importing an old file in full and deciding later which contacts to keep can establish the maximum before the selection is finished.

The operator thinks the data migration is still in progress. The billing rule has already observed a fact.

Moving the decision ahead of a large import changes what the same work can achieve. It can influence the next population peak instead of documenting why the previous one was unnecessary. The difference lies in the order of operations, not in how diligently someone performs the eventual clean-up.

Growth incentives tend to favour the expensive order. New contacts receive a launch date and a slide in the campaign presentation. Old contacts receive a task marked “when there is time”. The meter faithfully remembers the point at which the enthusiasm was greatest.

Import permission can also be spending permission

Archiving is reversible. Mailchimp allows contacts to return through an operator action or an import. It also describes contacts unarchiving themselves through a signup form or an interaction with a connected store.

The most recent email or SMS subscription status survives that return. Previously unsubscribed contacts cannot be imported as subscribed. A restored record can therefore rejoin the billable population without adding anyone to the audience that can receive marketing.

That gives the import button a second job. It changes data availability, and it can change the cost population. The person using it may have no purchasing title at all.

A marketing team can ask for a complete history, an integration administrator can supply it, and finance can later encounter the larger count. Each team has fulfilled its narrow brief. The economic decision to keep those records in their current state has slipped between them.

Quantifying avoidable spending would require an actual account's contact-state history, import logs, contracted tier and invoices. The documented rules already establish the management problem: reachable marketing subscribers, currently counted contacts and the period's maximum are three different numbers.

Mailchimp can provide something worth buying in the continued availability of a customer's history. A company should be able to explain that purchase. A record that remains solely because nobody has dealt with it is not made more valuable by calling it part of the customer base.

The reader has completed their part of the transaction. The sender still needs to decide who is buying the record's continuing place, and what work that place is supposed to do.