Voluum Pricing in 2026: Plan Limits, Total Cost and Alternatives

The short answer: Voluum is a cloud tracker priced as a subscription plus a usage model. On the public price page checked on 10 July 2026, its annual-billing view starts at $119/month for Profit (1M included events) and $299/month for Scale (5M included events). The published business tiers go to $7,999/month billed annually for Executive (500M events). A visit, lander click, conversion, and—at a ten-to-one rate—an impression can all consume the event allowance. If that allowance is exceeded, Voluum says tracking continues and the account is charged for overages. Voluum pricing · What Voluum counts as an event

That makes the real buying question more useful than “what is Voluum per month?”: what will this particular traffic path record, which plan limits will it touch, and which work still happens outside the tracker? This guide explains the published terms, shows how to make a defensible forecast, and gives a due-diligence path that does not pretend a feature grid is a migration plan.

Pricing and product terms were checked on 10 July 2026. Prices, quotas, add-ons, and eligibility can change. Verify the live Voluum pricing page and your own order summary before paying or moving production traffic.

Voluum pricing at a glance

The figures below are Voluum’s published USD plan rates on the date above. “Annual view” is the per-month figure displayed when the website’s yearly selector is active; it is billed annually, so calculate and approve the upfront commitment, not only the monthly-looking number. The current page describes all plans as cloud-based tracking. Voluum pricing and plan matrix

The same public cards show Corporate at $4,999/mo or $3,999/mo billed annually with 200M events, and Executive at $9,999/mo or $7,999/mo billed annually with 500M events. Those are contact-led plans: confirm the complete commercial scope, support, API, user, workspace, and overage terms in writing rather than extrapolating from a smaller tier. Voluum pricing

The table is a snapshot, not a recommendation. For example, a team can be under an event allowance while still outgrowing its active-campaign, domain, retention, report, workspace, automation, or access boundary. A procurement sheet should list every constraint the team actually uses—not just the first quota that appears in a sales card.

What Voluum means by an event

Voluum’s own documentation defines the billable actions as:

• Impression: an ad view; 10 impressions count as one billable event.
• Visit: a click on the campaign URL that successfully passes visit information to Voluum.
• Click: a visitor activating a CTA link or button on a landing page.
• Conversion: an offer-side result successfully sent back to Voluum through a postback URL or tracking pixel.

The important implication is that a paid-source click is not necessarily the whole meter. A landing-page funnel can create both a visit and a CTA click; a conversion adds another recorded event; impression tracking can add its own volume. The documentation says overage events are applied to the invoice at the end of a billing cycle. Voluum event definitions and overages

Do not treat this as a reason to avoid landing pages, conversion tracking, or impressions. Those are operating choices. It is a reason to forecast the full path rather than multiplying outbound traffic-source clicks by a plan price.

Build an event forecast before choosing a plan

Use a representative 30-day window from the system that currently carries spend. Separate direct-to-offer traffic from landing-page funnels, then record the actions Voluum will actually receive after your intended implementation.

forecast billable events
  = visits recorded by Voluum
  + landing-page CTA clicks recorded by Voluum
  + conversions returned to Voluum
  + (impressions recorded by Voluum ÷ 10)

This is a planning model based on Voluum’s public event definition, not a substitute for the account’s billing view. Ask Voluum to confirm treatment of your exact setup, especially if it includes impression pixels, multiple conversion types, retries, server-to-server callbacks, or a non-standard direct-tracking path. Read the official event definition

A practical worksheet

For every meaningful traffic flow, collect these inputs for a normal month, a launch month, and a high-variance month:

The page’s own FAQ puts the underlying rule plainly: every redirect through Voluum’s infrastructure or HTTP request to Voluum is an event. That makes instrumentation part of commercial diligence, not just an implementation detail. Voluum pricing FAQ

Calculate overage openly

For the tiers that publish overage rates, use a simple sensitivity calculation:

event overage = max(0, forecast events − included events)
                ÷ 1,000 × published plan overage rate

monthly cost before tax = plan price for the selected billing cadence
                          + expected event overage
                          + confirmed add-ons

For example, do not pick Profit merely because a quiet month is under 1M. Run the formula for a launch month where landing clicks, conversions, and impressions are all active. Then compare that result with Scale’s current price, its 5M allowance, its $0.05/1,000 published event overage rate, and its non-event limits. The correct answer can be either plan; it depends on the workload and the boundaries the team needs. Current plan limits and overage rates

Voluum’s billing documentation says annual plans are paid upfront, while overages still apply and are calculated monthly. It also says an upgrade begins a new billing cycle immediately; review the invoice and written terms before making an in-cycle change. Voluum billing and upgrade documentation

The costs that can sit beside the base plan

An accurate total cost is not a universal number. It is a short, documented list of terms your workflow actually needs.

Automizer deserves its own line item

Voluum’s pricing page separately lists Voluum Automizer Pricing. Its published tracked-ad-spend tiers are Free up to $1,000/month, then $375/month up to $50,000, $550 up to $100,000, $1,175 up to $250,000, $1,650 up to $500,000, and $2,380 up to $1,000,000, followed by a custom tier. The page says an Automizer subscription is upgraded in the Voluum panel on top of the regular Voluum plan and states a 1% overage charge when its Automizer limit is exceeded. Voluum Automizer pricing

The main plan matrix also shows plan-specific automation, integration, and included-ad-spend surfaces. Do not combine those two sets of numbers by assumption. Ask Voluum to identify, for your account and traffic-source connection:

1. which automation and source-control function is included in the base plan;
2. whether Automizer is required for the action your team wants;
3. which tracked ad spend counts to the Automizer meter;
4. the exact included allowance, overage, and billing cadence; and
5. what happens when spend crosses a tier boundary.

That is not a gotcha. It is the minimum information needed to convert a marketing page into an accountable operating budget.

Plan limits are also costs

Voluum publishes limits beyond events: active campaigns, landing pages, offers, traffic sources, affiliate networks, campaign flows, custom and dedicated domains, data retention, workspaces, users, report entitlements, support response time, and API level. Some automation and reporting capabilities are also differentiated by plan. Voluum’s current comparison matrix

For each one, write an answer to three questions:

• What will we use on day one? Count live entities and named people, not a vague number of “accounts.”
• What will a launch add? New GEOs and verticals often add domains, offers, landers, sources, and reporting needs at once.
• What happens when we hit it? Confirm whether the path is an upgrade, an add-on, an overage, a support request, or a hard operational stop.

The cost model is healthy only when the finance owner can rerun it from the real 30-day data and a written vendor quote. Avoid invented totals that silently assume a specific plan, event mix, domain count, integration, and support arrangement.

Which Voluum plan fits which team?

The following are starting points for a trial, not promises that a plan will fit. The public price page is the commercial source of truth; the proof campaign is the operating source of truth.

Profit: a bounded first production workflow

Profit is the logical first evaluation if one workflow can stay inside its published 1M events, 20 active campaigns, three custom domains, and six-month retention period. It is a weak fit if the team needs long-horizon reporting, has a heavy landing-page and conversion-event mix, or expects to use its first month as a launch month. Profit plan terms

Use the evaluation to test one source, one real routing rule, a lander or direct path, a valid conversion callback, the report used to move spend, and the account’s event view. A low-traffic demo that never fires a CTA click or conversion cannot validate the meter that will matter later.

Scale: a growing team that can forecast usage

Scale makes more sense when the business needs the published 5M allowance, 60 campaigns, five custom domains, 12-month retention, and its listed support and workspace surface. The primary test is still not the dashboard: reproduce the flow that carries margin and prove that cost, identifier, payout, status, and report dimensions agree with the external systems that own them. Scale plan terms

Start-up and Agency: a team with more operational surface

Start-up and Agency publish 10M and 25M events respectively, with larger campaign, domain, retention, workspace, automation, and access entitlements. They belong in the conversation when those are genuine operating requirements—not because a bigger card feels safer. Include a named owner for source integrations, permissions, quotas, and outbound postbacks in the trial plan. Start-up and Agency plan terms

Enterprise and contact-led plans: validate collaboration and data contracts

Enterprise’s published 60M-event allowance, longer retention, additional users, and account-management features can match a larger buying operation. Corporate and Executive list 200M and 500M events and more extensive workspace and user allowances. At this scale, event volume is rarely the only decision: API access, report delivery, permission design, support response, source integration, finance reconciliation, and data-export requirements should be written into the evaluation. Enterprise, Corporate, and Executive terms

Do not move to a higher tier only to hide an unexplained spike. First determine whether the spike is expected growth, a new tracked event, an impression path, a callback retry issue, or an implementation error. The correct remediation may be a different plan; it may also be fixing the data path.

Fair alternatives by operating model

There is no fair “best Voluum alternative” list without an operating constraint. A self-hosted tracker, a managed event-metered tracker, and a connected campaign-operations platform solve different problems. Start from ownership and workflow, then test the same labelled traffic path in every serious finalist.

The fairest comparison method is repeatable: take one production-like campaign, use the same source parameters and offer contract, create the same return event, ask every vendor how it meters that flow, and compare outputs on the same timezone and attribution window. That protects the buyer from both a misleading “unlimited” claim and a misleading “events included” claim.

A due-diligence and migration checklist

Do not make a full tracker cutover the first test. Pricing, identifiers, routes, postbacks, and reports are connected; a campaign that opens in a new UI is not evidence that it is safe to redirect paid traffic.

Before trial or purchase

1. Freeze a billing snapshot. Save the pricing URL, plan name, billing cadence, quoted invoice total, renewal date, event allowance, overage rate, included domains, users, retention, support, API, and any add-on term. Have the vendor correct ambiguities in writing.
2. Inventory the live data path. Export traffic sources, campaign URLs, source macros, domains, landers, offers, routes, caps, schedules, postbacks, conversion definitions, payout and cost fields, report dimensions, APIs, and access roles.
3. Write the metric dictionary. Define what your team calls a visit, click, lead, approved event, sale, deposit, rejection, cost, payout, revenue, and profit. Also record timezone, currency, attribution window, and late-conversion policy.
4. Forecast the meter. Use the full event model above for a normal, launch, and high-variance month. Include landing clicks, conversion callbacks, and impressions where they will be tracked.
5. Name owners. Assign responsibility for domains and DNS, traffic-source setup, partner callbacks, Voluum administration, usage monitoring, finance reconciliation, and rollback. Shared credentials are not an ownership model.
6. Set proof criteria. For example: a labelled visit carries the intended fields; a conversion arrives exactly once with the correct ID, status, amount, and timestamp; cost is shown on the right campaign; usage matches the forecast tolerance; and the required report exports cleanly.

During a controlled proof

1. Build one low-risk production-like campaign, including a route or fallback that actually matters. Do not validate only the happy path.
2. Send labelled test visits from the traffic source and check every parameter at the destination and in the report.
3. If a landing page is part of the funnel, activate a real CTA link and verify the recorded click separately from the campaign visit.
4. Trigger the partner-approved test conversion through the intended postback or pixel mechanism. Confirm it appears once with the expected relationship, payout or revenue field, and conversion definition.
5. Validate cost collection and reporting using the operating timezone and attribution window—not screenshots taken at convenient times.
6. Check the event/usage view against the model. Investigate a material mismatch before expanding traffic; do not assume a source-side click counter is the billable count.
7. Test the access model with the roles your buyers, analysts, finance colleagues, or partners will actually hold.

Voluum’s price page says all plans include automatic campaign migration from an old tracker. Its FAQ also says CSV import can bring landers and offers into Voluum but cannot import a new campaign because of how Voluum structures campaigns. Treat both as useful vendor capabilities, then ask exactly which objects, fields, and history will move in your migration. Rebuild and test the decisive campaign path regardless. Voluum pricing and migration FAQ

Before moving meaningful spend

• Run a small parallel or staged slice where your traffic-source agreements allow it, and reconcile visits, clicks, conversions, cost, payout/revenue, and source parameters.
• Keep the incumbent links, domain/DNS access, postback details, export, and a named rollback owner available until the late-conversion window that matters to the business has closed.
• Move budgets gradually. Do not combine the tracker migration with unrelated landing, offer, source, or routing changes that make a discrepancy impossible to isolate.
• Recheck the plan and add-on terms immediately before the spend increase. A plan page can change between a trial and a purchase order.
• Document every mapping and exception. The next operator should be able to explain why a conversion is in a report without rediscovering macros or status logic from old chat messages.

Where DarkCore fits—and where it does not

DarkCore is not an automatic alternative to Voluum. If the core requirement is Voluum’s cloud tracker, its specific event model, a particular source integration, or an existing reporting workflow, evaluate those requirements directly and prove them in Voluum.

DarkCore becomes relevant when the costly problem is not only attribution. It is built for media-buying teams that need campaign routing, PWA and Direct Link delivery, custom conversion statuses, analytics, and finance to operate on the same campaign context. Streams provide priority routing and weighted splits. The PWA Tracker connects PWA and Direct Link activity to one analytics and CRM layer. Conversion Statuses let the team use the events its vertical actually buys and gets paid on across postbacks, pixels, push, analytics, caps, and CRM. Finance keeps ledger and campaign-finance work close to the operating data.

That is a materially different promise from “another tracker with a lower price.” The right way to evaluate it is to choose one live flow and map its route, PWA or Direct Link stage, conversion statuses, postbacks, cost inputs, payout or revenue, finance fields, and decision owners. Then decide what should remain in Voluum, what should connect to DarkCore, and which manual handoff can disappear only after the reports reconcile.

If your team currently tracks in one tool but manages delivery, statuses, and finance in separate dashboards and spreadsheets, map that one workflow with DarkCore. If you only need to choose a tracking subscription, keep the evaluation honestly focused on the tracker.

FAQ

How much does Voluum cost in 2026?

On 10 July 2026, Voluum’s public monthly view showed Profit at $149, Scale at $349, Start-up at $599, Agency at $999, Enterprise at $1,999, Corporate at $4,999, and Executive at $9,999 per month. The annual view showed effective monthly prices of $119, $299, $539, $799, $1,599, $3,999, and $7,999 respectively, billed annually. Recheck the live page before purchase. Voluum pricing

What counts as a Voluum event?

Voluum bills visits, landing-page CTA clicks, conversions, and impressions; ten impressions count as one billable event. The vendor documents how each action is recorded, so model the events your own setup will send rather than using a traffic-source click total alone. Voluum event documentation

Does Voluum stop tracking after the event limit?

No. Voluum’s pricing FAQ says events continue to be tracked after the plan limit and the account pays the applicable overages. Its pricing matrix publishes per-1,000-event overage rates for the public tiers. Voluum pricing FAQ

Are overages charged on annual plans?

Yes. Voluum’s documentation says annual plans are paid upfront and overage charges still apply; it says overages are calculated monthly. Confirm the exact account term before relying on a forecast. Voluum billing documentation

Is Voluum Automizer included in the tracker price?

The price page shows plan-linked automation and integration allowances and also presents separate Automizer subscription tiers that are upgraded on top of a regular Voluum plan. Confirm the exact function, tracked-ad-spend allowance, and billing model that applies to your account before treating it as included. Voluum pricing

Should we replace Voluum with DarkCore?

Only if the problem is broader than tracker selection. Evaluate DarkCore when campaign routing, PWA or Direct Link delivery, custom conversion statuses, analytics, and finance need to run as one operating workflow. Prove one real flow and keep the existing tracker available until the numbers and responsibilities are clear. Explore DarkCore

Sources and update policy

This article uses first-party pricing, terms, product, and documentation pages for time-sensitive claims. It was checked on 10 July 2026. Do not use it as a quote: verify every commercial term in the live checkout, on the vendor page, or in a written order before committing spend.

• Voluum pricing, plan matrix, Automizer terms, and migration FAQ
• Voluum: what is an event?
• Voluum billing and upgrading documentation
• Voluum Terms and Conditions
• RedTrack pricing
• Binom pricing and installation requirements
• Keitaro installation documentation
• DarkCore product workflow

Review cadence: review this page by 10 October 2026, and immediately when Voluum changes a plan name, price, billing cadence, event definition, overage, retention term, domain/user limit, API entitlement, support term, automation allowance, or Automizer tier. Update updatedDate, the affected statement, and its source together.

Continue the evaluation

• Read Voluum alternatives for a workflow-first shortlist rather than a generic ranking.
• Compare a managed quota model with a self-hosted operating model in Binom vs Voluum.
• If your tracker data later needs to meet a CRM and finance process, see Tracker vs CRM for media buying.