Oracle Eloqua pricing in 2026. What the contact band and the edition cost you.

Eloqua bills on the contacts you store, not the emails you send, priced by contact band inside the Basic, Standard or Enterprise edition. Clean the database, reset the band and cap the uplift before you sign.

How is Oracle Eloqua priced in 2026?

Oracle Eloqua is priced on the edition you hold (Basic, Standard or Enterprise) and on the contact band your stored database falls into. Add on lines for sales tools, extra users, test environments and other channels sit on top. Each band carries one monthly price, and a count between two bands is rounded up to the next one.

Eloqua is the marketing automation product in the Oracle CX portfolio, and its meter is the one buyers misread most often. What you store drives the bill, while what you send barely touches it. For how Eloqua sits beside the sales, service and advertising lines in the same suite, see our Oracle CX licensing map.

What does Oracle's published price list show?

Oracle publishes Eloqua list prices in its Marketing Cloud Global Price List. The edition we checked, dated June 12, 2025, prices the three editions across 59 contact bands, from 10,000 contacts up to 100,000,000. The table shows a selection of those bands.

In every band shown, Standard lists at twice Basic and Enterprise at twice Standard. Enterprise carries no list price below the 500,000 contact band. Price also climbs far more slowly than contacts: going from 100,000 to 200,000 contacts raises Standard from $9,000 to $10,000 a month.

Why is the list price only a starting point?

The list is where Oracle's quote begins. Your discount, your term and your renewal language decide what you pay, and your order document and current quote are the only prices that bind you. Figures on third party review sites are usually someone's old quote and rarely say which edition or band they describe.

How does the Eloqua contact meter work?

Eloqua bills on the number of contact records stored, in the band set by your ordering document. Oracle's price list defines a contact as one record in the contact table, and the band as the most contacts that table may hold at any one time. Cost follows data accumulation, and campaign activity barely affects it.

That definition shapes everything else on this page. Two customers with identical campaign volume can sit two price bands apart on database discipline alone.

Which records count toward the priced base?

By default, every record in the contact table is a record on the meter. That includes contacts your campaigns can never legally touch again. Unsubscribes cause the most surprise, because a contact who opts out usually stays in the platform for suppression, keeps occupying a slot and keeps costing money at renewal.

• Counted by default. Active, unengaged, unsubscribed and duplicate records sitting in the database.
• Worth arguing over. Hard bounces, suppression only records and archived data, depending on your order language.
• Never counted. Records you actually delete. Deletion lowers the count; suppression leaves it where it was.

Do not take the definition from a sales deck. Pull your order document, check the metric definitions Oracle publishes through its cloud contracts library, and get the counted record states confirmed in writing.

Does deleting an unsubscribed contact lose the opt out?

No. Oracle's Eloqua documentation says that after a contact is deleted, the platform keeps its global subscription status, email address status, bounceback history and email group subscriptions indefinitely. If that person returns through a form or an upload, the new record inherits the unsubscribe or bounce, and someone has to reset it deliberately before emailing them.

That removes the usual objection to deleting opted out contacts. You do not need to keep a full record occupying a slot on the meter just to remember that someone said no. Agree the approach with your privacy team, since Eloqua keeps form submission data for 760 days unless it is excluded from reporting first.

Why does the contact count only go up?

Contact databases grow every month unless someone stops them. Form fills, list imports, event uploads and the CRM sync add records daily, and nothing in normal operation removes one. Sends are missing from that list, so a program that goes quiet for six months still climbs toward the next band while the CRM sync stays on.

The engaged audience grew 13 percent in three years, the stored database more than doubled, and the bill followed the database. Once a renewal signs at the higher band, that price becomes the base for every later uplift. Getting back down takes a full negotiation cycle and evidence Oracle has no obligation to accept.

Event season speeds this up. Two conference list imports of 20,000 records each can push a database across a band in one quarter, and those records are usually the least engaged data in the platform. The CRM adds a second risk, since Oracle warns that a deleted contact still present in the CRM is recreated on the next auto synch.

How much can contact cleanup save on Eloqua?

At list prices, a cleanup that drops you one band is worth a few thousand dollars a year on a small program and tens of thousands on a large one. It is the fastest saving because Oracle does not have to agree to it. It also lowers the base for every future uplift.

What does a band reset and a cap save in practice?

Take the hypothetical program from the table above in year three: 190,000 stored contacts on Standard, facing an uncapped renewal. After a census and a deletion pass, 96,000 marketable records remain. Say uncapped renewals run at 8 percent a year and you win a 3 percent cap. Every figure below is a list price before discount.

The band reset alone saves $12,000 in year one, or 10 percent. The cap widens the gap every year, and across three years the difference reaches $55,751, about 14 percent of the uncapped total. Your net prices will differ, but with the same discount on both paths the percentages stay the same.

How does the answer change with database size?

The band curve flattens as it rises, so the size of your database decides whether cleanup or the edition is the bigger number. The table applies a cleanup to three hypothetical programs and compares it with dropping one edition at the cleaned band.

For a small program, cleanup barely changes the list price and the edition question dwarfs it. For a large one, a 30 percent cleanup is worth $84,000 a year alone. Run the cleanup first in both cases: it sets the band you negotiate from, and an edition change is easier to argue once the count is settled.

How do you run the contact census?

The census is a four number report, dated, with the query logic written down and the extract kept. Eloqua's Contact Database Health dashboard supplies most of it: Total Contacts as of the last full calendar day, Total Active Contacts over a number of past months you choose, and Total Reachable Contacts.

• Total stored. Total Contacts from the dashboard, checked against the maximum in your order's band.
• Active in the last 12 months. The dashboard counts an email open, a clickthrough, a form submission or a page view. Add any scored sales touch you record in the CRM, and set the dashboard window to 12 months.
• Duplicates. Records that collapse under your merge rule, usually matched on email address.
• Unmailable. Hard bounces and global unsubscribes, which the dashboard treats as unreachable.

Use the same definition of active every time. A census built on a definition you cannot explain collapses the first time Oracle questions it. The census also sizes the renewal request and becomes the baseline for the next cleanup, which is what turns a single purge into a standing policy.

How do you delete contacts in Eloqua?

You can delete single records from Audience > Contacts, upload a file with the import purpose set to Delete contacts, or build a segment with filters such as not opened any emails or globally unsubscribed and delete its members in bulk. Oracle also documents deletion through the Program Canvas and data imports, which suits a recurring cadence.

Hygiene needs to be a policy with an owner. Set an inactivity window, a duplicate merge rule and a quarterly deletion cadence, have legal approve it, and make marketing operations own the number. Update the CRM in the same pass, or the auto synch will bring the deleted records back.

Where are the real boundaries between Basic, Standard and Enterprise?

The editions gate features, user seats and platform depth, while the contact band prices the database inside whichever edition you hold. Most programs we review need Standard, hold something else, and cannot name the feature that justifies the difference. Where both editions are listed, each costs twice the one below it, so the edition choice often outweighs the band.

Basic

Basic covers core email campaigns and landing pages for a contained program. It suits a single team running simple campaigns without deep platform integration.

Standard

Standard adds richer segmentation, lead scoring and reporting, and it is where most mid sized B2B programs belong. Scoring depth and campaign orchestration are the practical boundary with Basic.

Enterprise

Enterprise adds advanced security options, additional sandboxes, higher integration throughput and room for multi brand complexity. On the June 2025 list it is priced only from the 500,000 contact band upward. Oracle describes the platform on its Eloqua marketing automation page and in the Eloqua documentation.

Which four questions test an edition change?

Before paying for an edition step, make the case pass four questions.

1. Which named feature forces the jump? If no one on the marketing operations team can name it, you are paying for a label.
2. Who uses it? One admin needing integration headroom is a different problem from a program rebuild, and often a cheaper one.
3. Is there an add on path? Some capability sells as a separate line for less than the edition step.
4. What does the jump do at renewal? A higher edition raises the base that every future uplift compounds on.

Edition changes work in both directions, and buyers forget the downward one. If Enterprise was bought for a project that shipped two years ago, use the renewal to requote the program on Standard and make Oracle price the difference.

What should you check on the Eloqua order document?

Five lines on the ordering document decide your cost path, and most buyers read only the first. Pull the current order before any renewal conversation and answer each of these in writing.

• The metric definition. Which record states count toward the band, and whether suppression only records are named.
• The band and the overage. What happens the day the database crosses the line: an automatic step, a true up or a repriced quote.
• The measurement moment. Whether the count is checked continuously, at the anniversary or on demand.
• The uplift language. Whether renewal pricing refers to your prior price or to the list in force at the time.
• The add on schedule. Every line beyond the edition, each with its own quantity and renewal behavior.

Read the overage clause most closely. Under Oracle's standard definition a breach can in principle happen on any day, because the band caps the contact table at any one time. A contract that steps you up at the moment of breach behaves very differently from one that waits for the anniversary, and that difference sets your cleanup deadline.

What contract wording should you ask for?

• Anniversary measurement with a cure period. The count is taken at the anniversary, and you get time to delete records before any band step applies. A surprise overage becomes a scheduled task.
• A named renewal ceiling. The renewal price is your prior price plus no more than a stated percentage. Without the number written in, the cap does not exist.
• The next band priced now. If growth does push you up, the step is priced today at your current discount.
• Reduction rights at renewal. You may lower the band, drop an edition and remove add on lines without the remaining lines being repriced.
• A written list of counted states. Hard bounces and suppression only records are either excluded or listed, so the count is not open to interpretation later.

Oracle will not grant all of these, and some have to be traded for term length. Our guide to Oracle price holds and uplift caps covers the clause language in more detail.

Which add on lines surprise Eloqua buyers?

The surprise on a mature Eloqua order is rarely the edition line. It is the stack of add ons that built up across three renewals, each small when it was attached and none with an exit plan.

Watch the moments when lines get attached. Add ons arrive with a new campaign, a new region or a renewal sweetener, so the order grows exactly when no one is auditing it. Before every renewal, ask two things of each line: who used it in the last two quarters, and what breaks if it lapses.

Dead add ons are also renewal currency. Dropping two unused lines funds the concession you want most, the contact band reset. For the wider Oracle picture across a full contract cycle, our Oracle CIO white paper sets out a five year plan to control Oracle spend.

What have we seen in recent Eloqua renewals?

Across roughly 15 to 25 Oracle Eloqua renewals and reviews we advised on in 2024 and 2025, the contact base was almost always larger than the marketing program needed. Inactive and duplicate contacts inflated the band by 20 to 40 percent above the addressable audience. Three patterns came up again and again.

• Edition mismatch. Buyers held Enterprise for one or two features while the rest of the program fit Standard.
• Uplift drove lifetime cost. Uncapped renewals drifted up at high single digit percentages that compounded across the term.
• Hygiene paid first. Cleaning inactive contacts before the renewal reset the band and the price in one step, usually by one full band.

Why we advise against sizing Eloqua to the whole database

The common advice is to size Eloqua to your total database so you never hit an overage. We think that gets the order wrong. In roughly two thirds of the Eloqua programs we reviewed, a large share of the contact base was inactive or duplicate, so the customer paid for a band its real audience never used.

Sizing to the total database means sizing to your worst data. The better course is to clean down to marketable, engaged records before the renewal, reset the band to the smaller base and cap the uplift. Buy headroom on purpose by agreeing the price of the next band now, in writing, and step up only when real growth needs it.

Eloqua charges for the contacts you keep. A cleaned database, a dated census and a written cap will do more for the bill than any discount conversation.

How should you run an Eloqua renewal?

Two terms carry most of the money on an Eloqua renewal: the contact band and the uplift cap. Settle both first, in that order, and treat term length, add ons and edition as what you trade for them. Our Oracle renewal negotiation checklist covers the terms common to every Oracle cloud order.

How do you reset the contact band?

If the cleaned database sits below your current band, renew at the band that matches it. Oracle will not offer the reduction, so you put it on the table with evidence: a dated census showing total records, engaged records, deletions executed and the resulting count. Send it before the renewal quote is cut.

How do you cap the uplift?

An uncapped uplift compounds across every future renewal, and it compounds on whatever band you renew at. Write the cap into the order document at signature as a named ceiling. Paired with a band reset, a capped increase on a lower band is how a growing program keeps a flat bill.

What is the timeline for an Eloqua renewal?

The sequence matters more than any single request. The count must be clean before you put it forward, and term length stays off the table until the band and the cap are settled.

What will the Oracle account team say, and how should you answer?

Oracle's side of an Eloqua renewal follows a familiar pattern, so prepare your answers. These exchanges come up in almost every renewal we support.

• Band reset. You say the census shows 96,000 marketable records after cleanup, so you will renew at the band that covers 100,000. You will hear that the current band protects you against growth. Answer that growth is your decision to buy when it happens, at a price agreed now.
• Uplift cap. You ask for a written ceiling on future increases. You will hear that increases reflect product investment. Answer that in that case the ceiling costs Oracle nothing unless an increase exceeds it.
• Add on removal. You say two add on lines had no logins for two quarters and will not renew. You will hear that removing them changes the discount structure. Ask Oracle to requote the whole order, which you will compare with your alternative platform estimate.
• Longer term. You will hear that a three year term earns a better discount. Reply that term is open once the band and the cap are agreed, and that every year of a multi year price must carry the cap.
• Edition upsell. You will hear that Enterprise includes security and sandbox capacity you will need. Ask which named feature, who will use it and what the add on price is, then compare that with the edition step.

None of this is aggressive. It is a customer reading its own contract and its own data, which is what a vendor expects from a well run account.

Why put an alternative platform on file?

A documented alternative strengthens every request above. Marketing automation migrations are real projects, but they are routine ones, and renewal pricing changes when the account stops looking captive. Our notes on Salesforce Marketing Cloud licensing and HubSpot Enterprise negotiation cover two common comparisons.

The file needs three items to be credible: a market estimate for a comparable platform, a migration effort range from a partner or your own team, and a date by which switching is still feasible before the renewal. It never needs a threat.

What to do next

1. This month. Run a contact census for inactive, duplicate and unengaged records, starting from the Contact Database Health dashboard.
2. Before you share the census. Confirm in writing which record states Oracle counts toward the priced base.
3. At least 120 days out. Carry out the deletion policy well ahead of the renewal date, and clean the CRM in the same pass.
4. With the census in hand. Match the edition to the features in use, and test every add on line against two quarters of logins.
5. In the renewal. Negotiate the contact band down to the cleaned base.
6. At signature. Cap the renewal uplift in the order document.
7. Before the quote arrives. Bring in independent Oracle advisory ahead of the Eloqua renewal.

Frequently asked questions