Does Eloqua have a built-in email frequency cap?

No. Eloqua Insight can report how many emails each contact was sent, but there is no instance-wide setting that limits how many emails a contact can receive in a given period. Teams that want a cap build one from shared lists, contact fields or shared filters, checked by a decision step before each email.

How do I limit how many emails a contact receives per week in Eloqua?

Create a shared filter for contacts who have already been sent your weekly maximum in the last seven days, then add a decision step before every email that holds or skips anyone in that filter. Every campaign needs the same step. The limit holds while campaigns send at different times, but not when several reach the same contact at once.

Why do Eloqua frequency caps stop working when campaigns send at the same time?

Each campaign checks a contact’s send history on its own. When two campaigns reach the same contact within a short window, both checks run before either email has gone out, so both pass and the contact receives both emails. The more campaigns run in parallel, the more often it happens.

Do the Email Governor caps also stop working when campaigns send at the same time?

No. The Email Governor keeps one count for each contact across every governed campaign, and releases a contact to the email step only when that email fits within their limit. Campaigns launching in the same minute draw on the same count, so the cap holds however many campaigns run at once.

Can Eloqua prioritize one email over another for the same contact?

Not on its own. A decision step can hold or skip a contact, but it can’t see what other campaigns are waiting to send them, so whichever campaign reaches the contact first sends first.

How does the Email Governor decide which email goes out first?

Each governed campaign has a priority. When more email is waiting for a contact than their limit allows, the Email Governor releases the highest-priority email first, and the rest wait in the queue until the contact has room under their limit again.

Can I exclude some emails from the Email Governor?

Yes. The Email Governor only governs campaigns that include its step. Leave the step out of a campaign, for transactional or legally required email for example, and that campaign’s emails send without being held or capped.

Does the Email Governor work with Eloqua Send Time Optimization?

It works with time-of-day optimization but not with day-of-week optimization. The Email Governor counts an email as sent when it releases the contact to the email step. Time-of-day optimization only moves the email to a better hour, so it still goes out close to when it was counted. Day-of-week optimization can hold the contact in the email step for days, long enough for them to be sent more email than the cap allows.

Does the Email Governor work with Eloqua deliverability scheduling?

Yes. The Email Governor mirrors your deliverability scheduling configuration, so you can keep using deliverability scheduling in governed campaigns alongside your frequency caps.

Eloqua email frequency limits: how to cap emails per contact

Eloqua can tell you how much email each contact receives, but it has no setting that stops them receiving more. Many teams build their own cap, and it holds until campaigns start sending at the same time.

What Eloqua does out of the box

Eloqua measures frequency well. The Email Frequency data in Insight shows how many emails each contact was sent by month and by email group, and a report built on it is the quickest way to find out whether you have a problem at all.

What Eloqua doesn’t have is a rule that acts on those numbers. There is no instance-wide setting for “no more than three emails a week.” Subscription management doesn’t fill the gap either: email groups let contacts choose which kinds of email they get, not how many.

Three ways teams build a cap

Teams that want a limit inside Eloqua usually build one of the following, or a mix of them.

A suppression list

Contacts go onto a shared list when they enter an important campaign and come off it when the campaign ends. Every other campaign checks the list with a decision step before it sends. It keeps a launch or an event from being drowned out, as long as every campaign adds, removes and checks contacts correctly.

A throttle field

A campaign sets a field on the contact record when it emails someone, then waits a few days and clears the field again with an update step. Other campaigns check the field before sending. Anyone looking at the record can see that a contact is resting, and so can sales if the field syncs to the CRM. Like the list, it depends on every campaign keeping it up to date.

An activity filter

A shared filter finds contacts who have been sent a set number of emails in the last few days, and a decision step in front of each email holds or skips anyone in it. Of the three, this comes closest to a real cap, because it counts what each contact has actually been sent. Change the filter and every campaign that uses it changes too, which is convenient until one team needs a different rule.

Where the workarounds stop holding

All three work the same way. A check inside each campaign looks at what a contact has already been sent and decides whether to send one more. For an instance running a handful of campaigns a week, that is enough.

It stops being enough when campaigns send at the same time. If two campaigns reach the same contact within a short window, each runs its check before the other’s email has gone out. Both checks pass, and the contact gets both emails. Customers with the busiest Eloqua instances found that their caps simply stopped working on heavy days, and the more campaigns they ran in parallel, the more email got through.

Two smaller gaps come with the approach. A campaign built without the check isn’t governed at all, and nothing flags it. And a check can only say yes or no, so when two emails are waiting for the same contact, the one that arrives first goes out, whether or not it is the one that matters more.

Eloqua’s decision steps are designed to evaluate one contact in one campaign, and they do that reliably. A frequency cap is a rule about every campaign at once, so it has to be enforced somewhere that can see all of them.

How the Email Governor enforces a cap

The Email Governor was built for this problem. Our customers run some of the largest Eloqua instances in the world, and they were watching their caps give way under load in a way no better filter could fix.

The Email Governor adds a step to the campaign canvas, just before the email step. Contacts wait there in queues you configure, and Email Governor releases each one to the email step only when that email fits within the contact’s limit. Every governed campaign in the instance draws on the same count, so two campaigns launching in the same minute can’t both get through. The cap holds however many campaigns you launch and however many emails you send.

You decide how many emails a contact can receive in a given period, with tighter limits for the segments that need them.

How the Email Governor prioritizes email

A cap means some email has to wait, which raises the harder question of which email. When a contact has room for one more email this week and three campaigns want to send it, something has to choose. In a native setup nothing does, and the campaign that reaches the contact first wins.

The Email Governor makes that choice with priorities. Each governed campaign has one, and when more email is waiting for a contact than their limit allows, the highest-priority email goes out first. The rest stay in the queue and go out in order as the contact has room under their limit again. A renewal notice or an event invitation goes out on time, and the newsletter that would have crowded it out waits a few days.

Because the order is set in one place, teams don’t have to negotiate each send with one another. Marketing operations decides once which kinds of email matter most, and every governed campaign follows that order.

Email frequency limits in Oracle Eloqua

In short