Billing

Plans, trials, event allowances, and what a subscription actually buys.

Pivolio bills on event volume. There is no free tier and no enterprise tier — three plans, and the only thing that separates them is how many events you send.

Plans

PlanEvents / monthMonthlyAnnual (per month)
Starter500,000$49$39
Growth3,000,000$149$119
Scale15,000,000$349$279

Volume is the only lever. Every plan carries an identical feature list — the same destinations, the same identity resolution, the same attribution models, the same traffic-quality scoring. Nothing is gated behind a higher tier, so you never have to upgrade to unlock a capability. You upgrade because you outgrew the allowance.

What a subscription buys

This is the part worth reading carefully, because it isn’t what most tools do:

A workspace without a subscription still tracks, stores and reports every event. It just doesn’t deliver them to your ad platforms. Delivery is the paid part.

So while you’re unsubscribed, events still arrive at the collector, still resolve to a person, still build your identity graph and attribution history, and still show up in reporting and the Live Debugger. What doesn’t happen is the dispatch to Meta, Google Ads, TikTok and Reddit.

The practical consequence: nothing is lost while you’re unsubscribed. You can instrument your site, verify events look right, and confirm identity resolution is working before you pay anything. When you subscribe, delivery starts from that point forward — historical events are not backfilled to the platforms.

The 14-day trial

Every plan includes a 14-day free trial. A card is collected at checkout, which means the subscription is created immediately in the trialing state — and the dispatch gate treats trialing exactly like active. Delivery works from the first minute of the trial, not after it.

Because a card is on file, the trial converts to a paid subscription automatically when the 14 days are up. Cancel before then if you don’t want to be charged.

Annual billing

The annual price in the table is the per-month equivalent — you’re billed for the year. Annual plans also change how the allowance is counted: instead of a monthly bucket, you get included_events × 12 for the whole billing period.

Growth annual, for example, is 36,000,000 events across the year rather than 3,000,000 per month. If your business is seasonal — a retailer whose December is five times its March — this matters. A monthly plan meters you against your peak month; an annual plan lets the quiet months pay for the loud one.

Going over the allowance

What happens depends on the automatic upgrades setting and whether you’re still in a trial:

UsageAutomatic upgrades onAutomatic upgrades off, or trialing
90% of capWarningWarning
100% of capDelivery continuesDelivery pauses
110% of capMoved to the smallest plan that covers youDelivery pauses

With automatic upgrades on and a paid subscription, you’re moved up rather than cut off — the alternative would starve your campaigns of conversion data at exactly the moment you’re getting the most traffic. A surprise line item is recoverable; a week of unoptimized bidding during a launch is not.

A trial always pauses at the cap, even with automatic upgrades on. So does any workspace with automatic upgrades turned off. Delivery resumes when the billing period renews, or immediately if you upgrade.

Events keep being tracked, stored and reported throughout — only delivery stops. If your destinations go quiet unexpectedly, check your usage against the cap before debugging the destination itself.

Subscription statuses

  • trialing — inside the 14-day trial. Delivery is on.
  • active — paid and current. Delivery is on.
  • past_due — a payment failed and is being retried. Resolve the payment method before the retries are exhausted.
  • canceled — no active subscription. Events are still tracked, stored and reported; they are no longer delivered.

If destinations look silent

If the Live Debugger shows events arriving but your destinations report nothing, check the subscription status first. It’s the most common explanation, and it looks identical to a broken destination from the outside — the events are there, they simply were never offered to the platform.

  • Team and roles — only owners and the billing role can see or change the plan.
  • Destinations — what delivery actually does once it’s enabled.