A marketing director I worked with last quarter told me, with real confidence, that her team couldn't possibly be over-mailing anyone. "We have a HubSpot email frequency cap of four per week. It's not even possible." Two minutes into the portal audit, we found a contact who had received eleven emails from her domain in the previous five days. Every one of them was sent inside her HubSpot instance. Not one violated her cap.
This is the most common misunderstanding I see about the HubSpot email frequency cap — the assumption that it covers everything HubSpot sends. It doesn't. It covers one specific bucket, and most B2B portals send far more email outside that bucket than inside it.
The frequency cap setting lives in your Marketing Email settings. You set a number — "no more than N marketing emails per contact in a rolling window of X days" — and HubSpot enforces that limit on any marketing email sent through the Marketing Email tool. If a workflow tries to enroll a contact who's already at the limit, the send is suppressed. HubSpot's own documentation describes this as a guardrail for marketing email volume specifically — not a universal send cap.
That's it. That's the whole feature. It's a useful guardrail and I'd never tell you to turn it off. But the scope is narrow in three specific ways that matter once you understand what gets excluded.
Here's the list of things that look like marketing email to your recipients, but don't count against the frequency cap:
The honest summary: the frequency cap covers the channel HubSpot can see, not the volume the recipient receives. In most B2B portals I audit, the cap-protected channel is 30 to 50 percent of total volume to engaged contacts. Sometimes less.
Even within the marketing email bucket where the cap does apply, there's a subtler issue. A weekly cap is a volume limit, not a pacing rule. Four emails per seven days and four emails on Monday morning are the same number to HubSpot. They are absolutely not the same number to your contact, and they are absolutely not the same number to Gmail's filters, which Google's sender guidelines describe as engagement- and pattern-aware at the recipient level.
I've seen the "Big Brand Blaster" pattern enough times to name it: a portal where every workflow defaults to the same "send Tuesday at 10 AM" calendar choice, the frequency cap is conscientiously set, and every Tuesday morning a slice of the database gets three emails in a 90-minute window. The cap is satisfied. The inbox isn't. This is the textbook setup for an email collision problem.
This is the gap that pushed us to ship Campaign Orchestration in February 2026. The previous version of our scheduler optimized send time per campaign — pick the best window for this email and ship it. That's calendar-centric thinking, and it's the same shape of thinking the HubSpot cap is built around. The new orchestrator works the other way: it manages the flow of content per contact across all of your campaigns, deciding which email to release to which person at which moment based on what that person has already received. A cap says "stop after four." Orchestration says "spread the four."
If caps don't solve frequency, what does? In my experience, two principles cover most of the real-world work:
The question isn't "how many marketing emails does this contact get." The question is "how many emails total does this contact get from anyone at our company." That's the number the mailbox provider tracks. That's the number that determines whether the next send lands in the inbox or the promotions tab or worse. You need visibility into the whole picture, not just the slice your marketing automation can see — the kind of visibility that catches over-messaging before it shows up in your engagement metrics.
A contact who receives 5 emails spread across a week experiences your brand very differently than one who receives the same 5 emails in 24 hours. Same volume, completely different sender reputation impact. The pacing is the product. Recipient-centric scheduling beats calendar-centric scheduling at almost any cap level.
Run this in HubSpot. (If you want the full 15-minute version, the HubSpot email collision audit walks through the whole sequence.)
If the actual count is more than 50 percent above your cap, your cap is decorative. That's not a HubSpot failure — it's a feature scope misunderstanding, and the fix is to start thinking about frequency at the recipient level instead of the channel level. Then implement orchestration that actually works at that level.
None of this means turn the cap off. It's a real ceiling for the channel it covers, and it'll save you from the worst version of a runaway workflow. Set it. Tune it. But understand it as a backstop, not as your frequency strategy.
The actual strategy lives upstream: in how you stage your campaigns relative to each other, in whether your scheduling system is recipient-aware, and in whether you have visibility into the sends happening outside the marketing email tool.
The HubSpot email frequency cap is a setting in Marketing Email Settings that limits the number of marketing emails any one contact can receive in a rolling time window (typically per week). If a workflow tries to send an email that would exceed the cap, the send is suppressed for that contact. It only applies to emails sent through the Marketing Email tool.
No. Sales emails and Sequences are classified as one-to-one sends and are excluded from the marketing frequency cap. This is one of the largest gaps in cap coverage for B2B portals where sales is sending high volumes through HubSpot.
No. Transactional emails — password resets, receipts, expiration notices, and anything sent through the Transactional Email add-on or Transactional API — are exempt from the cap. Recipients still count them as emails from your company, but HubSpot does not.
There's no universal number, but for most B2B portals running an active nurture program, three to four marketing emails per contact per seven days is a common starting point. The more important question is what your total recipient-level frequency is across all channels — the cap is only one component of that.
If you want to see what your real recipient-level frequency looks like — across marketing, sales, and transactional sends — the free trial of Seventh Sense will surface it in about 15 minutes after you connect your portal. Most teams are surprised by the gap between their cap and their actual send pattern. The first time you see that chart is usually the moment frequency strategy starts to feel like a real lever instead of a setting you toggled in 2023 and forgot about.
Set the cap. Then design for the volume it doesn't see.