An active contact is not a universal marketing-industry status. It is a platform-specific label whose definition can combine deliverability, suppression, eligibility or billing rules.
Active contactActive contact
That is why “we have 10,000 contacts” can produce different plan sizes in different products. The safest way to read the term is: ask the platform what “active” controls. Do not assume it means “subscribed,” “recently engaged,” or “currently billable.”
Active
A vendor-defined eligibility/status label. Its exact meaning belongs to that vendor.
Subscribed
The person has a positive permission/subscription state for a channel or purpose. A subscribed contact can still be excluded for another reason, such as suppression or a temporary sending policy.
Suppressed
The platform should not send the applicable marketing messages to the contact. Suppression can result from opt-out, hard-bounce handling, complaint handling or other policy.
Recently engaged
The person has recently shown behavior such as opening, clicking, purchasing or visiting. Engagement is behavioral. It does not create consent by itself.
Billable
The record counts toward a vendor’s pricing calculation. Billing can overlap with active status, but it is not conceptually the same thing. Treat these as separate dimensions even when one vendor maps several of them together.
A billing example: the same database can produce different counts
One product may count contacts subscribed to a topic, another may count stored records that are not archived, and a third may charge by messages sent. Those are different populations even when they are calculated from the same customer database.
That model shows why cross-platform plan comparisons are tricky. A merchant can migrate the same records and see a different billable-contact number even though no customer was added or removed. Keep the provider rule and the canonical customer state separate so a pricing change does not rewrite consent history.
One profile can have a state vector
Consider an ecommerce customer with this profile:
- marketing email: unsubscribed
- SMS: subscribed
- email deliverability: valid
- last purchase: 5 days ago
- last email click: 180 days ago
- profile stored in CRM: yes
Is that contact active? There is no neutral yes/no answer without a product definition. They are a recent buyer, an SMS subscriber, an email non-subscriber and a valid stored profile at the same time. A better internal representation is a state vector, not one overloaded label.
Why this matters for billing
Suppose Vendor A charges for active email profiles, Vendor B charges for all stored marketing contacts except archived/cleaned records, and Vendor C charges by messages sent. A store with “10,000 contacts” may have:
- 7,200 email-subscribed contacts
- 8,600 vendor-defined active profiles
- 9,400 billable stored contacts
- 3,100 recently engaged contacts
None of these numbers is inherently the “true contact count.” They answer different questions. When comparing platforms, request the billing definition and calculate it against your own data. Do not compare price tiers by headline contact limits alone.
Migration rule: preserve source states
When importing from another platform, map source states explicitly:
- source subscription status
- source suppression reason
- consent timestamp/source where available
- deliverability status
- engagement timestamps
- target vendor’s active/billable definition
Do not turn every exported row into “active subscriber” because the source file was called contacts.csv.
Separate product vocabulary from your canonical customer model
If your own platform integrates several ESPs, do not import each vendor’s label directly into one status field. Maintain canonical states such as channel permission, suppression reason and recent engagement, then map each vendor’s active or billable concept at the integration boundary. This makes migrations reversible and prevents one vendor’s pricing vocabulary from redefining the customer’s actual consent state.
What does this page teach beyond a generic glossary definition?
It teaches active, subscribed, suppressed, engaged and billable as separate axes. Vendor documentation can then map those axes into its own terminology. This is the only reliable way to explain why identical customer databases produce different “active contact” and pricing counts across platforms.
A platform example: active does not mean subscribed
An email platform can define an active contact as one that is eligible for a particular send, while keeping subscription preferences as a separate topic or channel state. A contact list may retain the record even after the person opts out of one topic, and an address can be valid for delivery without being eligible for marketing.
The practical lesson is not a universal definition. It is a data-model boundary: ask which event changes the active label, which scope it covers, and whether the label controls delivery, reporting, or billing. Do not copy a platform's label into a neutral glossary as if every product uses the same rule.
Active contact checklist
- When a pricing page says “up to 10,000 contacts,” ask:
- Which contact states are counted?
- Is counting per channel or profile?
- Are suppressed/unsubscribed records included?
- When is the count sampled for billing?
- Without those answers, 2 $100 plans with the same headline contact allowance are not comparable
Every app on every plan. Connect your store and switch on the flows in an evening.