Oracle Eloqua bills on stored contacts across three editions, so the database, not the campaign calendar, sets the cost. How the meter ratchets, where the edition boundaries sit, and the levers that reset the band at renewal.
Oracle Eloqua bills on the contacts you store, not the emails you send, across Basic, Standard, and Enterprise editions with add on lines layered on the order. This page maps the meter, the edition boundaries, and the renewal levers that reset the band.
Oracle Eloqua is the marketing automation product in the Oracle CX portfolio, and it carries the portfolio's most misunderstood meter. You do not pay for what you send. You pay for what you store.
This page goes deep on that one contract. For how the Eloqua meter sits alongside the sales, service, and advertising meters in the same suite, read the Oracle CX licensing map.
Eloqua bills on the number of contact records stored in the platform, in bands set by your ordering document. The meter is the database, so cost tracks data accumulation, not marketing activity.
That distinction decides everything else on this page. Two customers with identical campaign volume can sit two price bands apart on database discipline alone.
By default, a record in the database is a record on the meter. That includes contacts your campaigns can never legally touch again.
Unsubscribes are the sharp edge. A contact who opts out stays in the platform for suppression, keeps occupying a slot, and keeps costing money at renewal.
Do not take the definition from a sales deck. Oracle defines what it counts in the ordering paperwork, so pull your order document, check the metric definitions Oracle publishes through its cloud contracts library, and confirm the counted record states in writing.
Contact databases grow monotonically unless someone forces them not to. Form fills, list imports, event uploads, and the CRM sync add records every day, and nothing in normal operation ever removes one.
Notice what is missing from that list: sends. A program that goes quiet for six months still climbs toward the next band if the CRM sync stays on.
How a stable program still climbs bands (illustrative volumes)
| Year | Engaged audience | Stored database | What happened |
|---|---|---|---|
| Year one | 60,000 | 90,000 | Signed with comfortable headroom above the engaged base |
| Year two | 65,000 | 140,000 | CRM sync imported dormant accounts, two events added lists |
| Year three | 68,000 | 190,000 | Band breached at renewal while the audience barely moved |
The marketing program grew 13 percent in three years. The bill followed the database, which more than doubled. That is the growth trap: the meter measures your data discipline, not your marketing success.
The cost of being wrong here is a band you cannot retreat from. Once a renewal signs at the higher band, that price becomes the baseline for every uplift that follows, and recovering it takes a full negotiation cycle with evidence Oracle has no obligation to accept.
Event season is the classic accelerant. Two conference list imports of 20,000 records each can push a database across a band in one quarter, and the records that came with them are usually the least engaged data in the platform.
Cleaning inactive, duplicate, and unmailable records ahead of a renewal is the fastest Eloqua saving available. In the estates we reviewed, 20 to 40 percent of stored records added no marketing value.
Hygiene has to be a policy, not a one time purge. Set an inactivity window, a duplicate merge rule, and a quarterly deletion cadence, and make marketing operations own the number.
The census is a four number report: total stored records, records active in the last 12 months, duplicates by merge rule, and records that are unmailable for legal or deliverability reasons. Date it, name the query logic, and keep the extract.
Define active honestly and consistently: an open, a click, a form submit, or a scored sales touch inside the window. A census built on a definition you cannot defend collapses the first time Oracle questions it.
The census does double duty. It sizes the renewal ask, and it becomes the baseline the next cleanup is measured against, which is what turns a purge into a policy.
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.
Basic covers core email campaigns and landing pages for a contained program. It suits a single team running straightforward campaigns without deep platform integration.
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 adds advanced security options, additional sandboxes, higher integration throughput, and room for multi brand complexity. Oracle documents the platform on its Eloqua marketing automation page and in the Eloqua documentation.
Before paying an edition step, make the case survive four questions.
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 question below in writing.
We do not publish Eloqua price points on this page for a reason: Oracle does not maintain a stable public list for these lines, and any number you read elsewhere is somebody's old quote. Your order document and your quote are the only prices that exist for you.
The overage clause deserves the closest read. A contract that quietly steps you to the next band on a breach behaves very differently from one that waits for anniversary, and the difference decides when your cleanup work must land.
Edition moves work in both directions, and the down move is the forgotten one. If Enterprise was bought for a project that shipped two years ago, the renewal is the moment to requote the program on Standard and make Oracle price the difference.
The surprise on a mature Eloqua order is rarely the edition line. It is the stack of add ons that accumulated across three renewals, each small when attached, none carrying an exit plan.
Common Eloqua order lines beyond the edition
| Order line | What it is | What to watch |
|---|---|---|
| Sales enablement tools | Profiler and Engage seats for the sales team | Seat counts drift above the sellers actually logging in |
| Intelligence modules | Advanced scoring, attribution, and insight capability | Sold on promised value, renewed on inertia, verify use annually |
| Deliverability lines | Dedicated IP addresses and deliverability services | Sensible for high volume senders, dead weight for the rest |
| Additional sandboxes | Extra test and development environments | Attached for one project and never detached afterward |
| Channel extensions | SMS and other channels wired into campaigns | Metered on message volume, a different meter than contacts |
Watch the attach moments. Add ons arrive with a new campaign, a new region, or a renewal sweetener, which means the order grows at exactly the moments nobody is auditing it.
Audit the stack before every renewal with one question per line: who used this 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 actually want, which is the contact band reset.
Two levers move the money on an Eloqua renewal: the contact band reset and the uplift cap. Everything else on the order is supporting cast.
If the cleaned database sits below your current band, renew at the band that matches it, not the band you hold. Oracle will not volunteer the reduction. You table it, with evidence.
The evidence is a dated database census: total records, engaged records, deletions executed, and the resulting count. Send it before the renewal quote is cut, not after.
An uncapped Eloqua uplift compounds across every future renewal, and it compounds on whatever band you renew at. Cap it at signature, in the order document, as a named ceiling.
Pair the cap with the reset. A capped increase on a lower band is how a growing program holds a flat bill.
The sequence matters more than the asks. Clean before you count, count before you negotiate, and never discuss term length until the band and the cap are settled.
The renewal conversation follows a script on Oracle's side, so it helps to have one on yours. Three exchanges recur in almost every Eloqua renewal we have supported.
None of this is aggressive. It is a customer reading its own contract and its own data, which is precisely what a marketing automation vendor expects a well run account to do.
The standard advice is to size Eloqua to your total database so you never hit an overage. We disagree. In roughly two thirds of the Eloqua estates Fredrik Filipsson reviewed, 20 to 40 percent of the contact base was inactive or duplicate, so the buyer paid for a tier the real audience never used. The buyer side move is to clean the database to marketable, engaged records before the renewal, reset the contact tier to match the smaller base, and cap the renewal uplift. Sizing to the total database is sizing to your worst data, not your marketing program.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Eloqua charges for the contacts you keep, not the ones you reach. Clean the base and the renewal negotiates itself down a tier.
Five moves, ordered by speed to value. The first funds the rest.
Remove inactive, duplicate, and unmailable records before the renewal date, under a documented deletion policy that legal has approved.
Match Basic, Standard, or Enterprise to the features in actual use, and price the add on path before accepting an edition step.
Negotiate the band down to the cleaned base rather than renewing at the old level. Bring the census as evidence.
Lock a renewal ceiling in the order document to stop compounding increases across the term.
Kill the lines nobody used in two quarters, and trade the survivors for the band reset you want.
A documented alternative platform strengthens every move above. Marketing automation migrations are real projects, but they are routine ones, and renewal pricing changes when the account stops looking captive.
The file needs three artifacts 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 remains feasible before the renewal. It never needs a threat.
If Eloqua renews alongside sales or service lines from the same suite, read the anniversary and co term mechanics in the Oracle CX licensing map before conceding anything on this line alone.
Eloqua prices on the edition you hold, from Basic through Standard to Enterprise, and the contact band your stored database falls into. Add on lines for sales tools, intelligence, deliverability, and sandboxes layer on top of both.
No, the priced meter is the stored contact database, not sending activity. Send volume matters operationally and can appear as allowances in some orders, so check your ordering document, but the bill tracks what you store.
Yes, by default an unsubscribed record still sits in the database for suppression and still counts toward the band. Only deletion removes a record from the meter, which is why the deletion policy is a pricing decision.
Eloqua sells in Basic, Standard, and Enterprise editions. Basic covers core campaigns and landing pages, Standard adds segmentation, scoring, and reporting depth, and Enterprise adds advanced security, sandboxes, and integration headroom.
Clean the database to marketable records, reset the contact band to the cleaned count, right tier the edition, audit the add on stack, and cap the uplift. Hygiene is usually the fastest single saving because the meter follows the data.
Yes, the uplift is a commercial term and a ceiling can be written into the order document at signature. Uncapped, increases compound on top of whatever band you renew at, so the cap and the band reset belong in the same negotiation.
Review sales enablement seats, intelligence and attribution modules, dedicated IP and deliverability lines, extra sandboxes, and channel extensions such as SMS. For each, confirm who used it in the last two quarters before renewing it.
No. Sizing to the total database means paying for inactive and duplicate records the program never uses. Clean the base first, then size the band to the marketable, engaged population and keep headroom deliberate, not accidental.
The governance, renewal and negotiation moves that hold Oracle cost across a five year horizon.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Oracle Eloqua prices the database you keep, not the audience you reach. The buyer who cleans the contact base before renewal controls both the tier and the uplift.
