Understanding Your Bill

CustomerLabs uses usage-based (metered) billing. Your bill has two parts:

• Plan fee — a fixed monthly amount for the plan you are on.
• Usage beyond your plan’s allowance — charged only if you exceed it.

Every plan includes a monthly usage allowance. If your consumption stays within the allowance, you pay only the plan fee. Consumption beyond the allowance is billed in fixed-size blocks called Usage Unit Packs.

The sections below explain how usage is measured and billed.

The Usage Unit model

CustomerLabs performs four kinds of work on your data, each measured on its own scale:

• Collecting your data
• Delivering it to your ad and analytics tools
• Computing over it (audience refreshes, reports)
• Storing it

Billing each separately would require four meters, four allowances, and four line items on your invoice. Instead, all four are converted into a single shared unit — the Usage Unit (UU).

A Usage Unit is a common measure of platform usage: one allowance to track and one overage calculation, regardless of which kind of work produced the usage.

The four usage components

Component	Definition	Driving Factors
Ingestion	Data coming in — from your website, mobile app, CRM, or any connected source.	The volume of traffic and events your sources send.
Activation	Data going out — every event delivered to a connected destination (ad platforms, analytics, data lakes). Counted once per destination.	The number of connected destinations. One event sent to 10 destinations counts 10 times.
Scanning	Data processed when computing over your stored events — audience refreshes, identity resolution, reporting queries. Measured in GB (often TB on larger accounts).	Audience refresh frequency and how heavily reports and the app are used.
Storage	Data kept — the total volume of your event and profile data held in CustomerLabs. Measured in GB (often TB), as a point-in-time snapshot.	The amount of history the account has accumulated.

Activation is counted per destination

Connecting more destinations increases your usage.

If one event flows to 1 destination, that is 1 activation. If the same event flows to 20 destinations, that is 20 activations — 20 separate deliveries take place. Two accounts with identical traffic can have significantly different bills if one delivers to more destinations.

Usage Unit rates

Each component is multiplied by a conversion rate^* to arrive at the Usage Unit scale.

Important

^* All pricing and conversion rates on this page — plan fees, Usage Unit rates, pack prices, and add-on prices — are current as of August 2026 and may be subject to change. Any revision will be communicated to your registered email address.

Component	Rate
Ingestion	0.40 UU per event ingested
Activation	0.20 UU per event delivered
Scanning	750 UU per GB scanned
Storage	1,700 UU per GB stored, per month

The sum of the four values is your Usage Unit consumption for the billing period.

Usage Units =  (ingested events   × 0.40) +
               (delivered events  × 0.20) +
               (GB scanned        × 750) +
               (GB stored         × 1,700)

Interpreting the rates

The rates apply to different units and are not directly comparable. Event volumes are typically in the millions, while scanned and stored volumes are measured in GB — which is why the per-GB rates are much larger.

Two comparisons are meaningful:

• An ingested event consumes about twice as many Usage Units as a delivered event.
• A GB in storage consumes more Usage Units than a GB scanned — stored data is held for the entire month, while a scan happens once.

The rates are identical for every account, so your Usage Unit consumption depends only on how much you ingest, deliver, scan, and store.

Usage Units within the Plan

Every plan includes a monthly Usage Unit allowance at no extra cost:

Plan	Included Usage Units per month
Growth	500,000 UU
Agency Lite	2,500,000 UU
Agency Premium	5,000,000 UU

If your consumption stays within the allowance, you pay only the plan fee.

No feature caps

This model places no limits on the number of sources, destinations, or segments you can create. Billing is based on what you consume, not on how many items you configure.

Overage billing

Overage is billed in whole Usage Unit Packs. A pack is 500,000 UU. The pack size and price are the same on every plan — only the included allowance differs by plan.

Currency	Price per 500,000 UU pack
USD	$27.25
INR	₹2,499

Overage        = Usage Units consumed − included allowance
Packs charged  = Overage ÷ pack size, rounded UP to the next whole pack
Amount         = Packs charged × pack price

Packs are whole units

A partly used pack is billed as a full pack — exceeding a pack boundary by 10 UU costs the same as exceeding it by 499,990 UU.

Important

All pricing and conversion rates on this page — plan fees, Usage Unit rates, pack prices, and add-on prices — are current as of August 2026 and may be subject to change. Any revision will be communicated to your registered email address.

Example calculation

Consider a Growth account (500,000 UU included) with the following usage in one month:

• Sources send 4 million events.
• 5 destinations are connected, and every event goes to all five — 20 million events are delivered.
• The account holds 1.5 TB of accumulated event and profile data.
• Audiences refresh daily, scanning 1 TB over the month.

Converting to Usage Units (1 TB = 1,024 GB):

Component	Usage	In GB	Rate	Usage Units
Ingestion	4,000,000 events	—	× 0.40	1,600,000 UU
Activation	20,000,000 events	—	× 0.20	4,000,000 UU
Scanning	1 TB	1,024 GB	× 750	768,000 UU
Storage	1.5 TB	1,536 GB	× 1,700	2,611,200 UU
Total				8,979,200 UU

Applying the overage in invoice calculation

Usage Units consumed   = 8,979,200 UU
Included allowance (-) =   500,000 UU
Overage                = 8,479,200 UU

Packs = roundup(8,479,200 ÷ 500,000) = roundup(16.96) = 17 packs
Amount = 17 × $27.25 = $463.25      (or 17 × ₹2,499 = ₹42,483)

Total Invoice Value = $129 (Fixed Plan) + $463.25 (Overage)
                    = $ 592.25

Note

The 17th pack is only 96% used, but it bills as a full pack.

Interpreting the breakdown

The contribution of each component in this example:

Component	Share of total
Activation	45%
Storage	29%
Ingestion	18%
Scanning	9%

Activation is the largest component — larger than Ingestion solely because of the 5 connected destinations. The same 4 million events delivered to 1 destination instead of 5 would produce 800,000 Activation UU instead of 4,000,000, reducing the month’s overage by roughly 6.5 packs (about $177).

Storage is the second-largest component and the only one that grows without any activity in the month — it reflects accumulated history rather than current traffic.

Review the breakdown before attempting to reduce usage. Ingestion is often assumed to be the largest component; in this example it is third.

Important

All pricing and conversion rates on this page — plan fees, Usage Unit rates, pack prices, and add-on prices — are current as of August 2026 and may be subject to change. Any revision will be communicated to your registered email address.

Billing cycle

Billing runs on calendar months. Every cycle starts on the 1st, and the renewal invoice is dated the 1st.

• The usage counter resets to zero at the start of each cycle.
• At the end of the cycle, the four measurements are finalised, converted to Usage Units, compared against the allowance, and any overage is added to that invoice.

Mid-month sign-ups are prorated: the first invoice covers the partial month. Sign-ups within 5 days of the 1st are combined with the next full month into a single invoice.

Viewing your usage

Account Settings

Usage is shown under Account Settings. This view includes:

• Usage Units consumed so far in the current period, against the allowance
• A day-by-day chart, colour-coded by the four components
• A breakdown of each component’s contribution
• Current charges for the period

Figures are month-to-date and update as usage is recorded.

Invoices

The invoice shows overage as a single total. The View overage breakdown link next to it opens the detail for that invoice: the allowance, the total, the overage, and each component’s contribution with its share as a percentage.

On agency plans, the breakdown also splits usage by sub-account.

Viewing the breakdown requires signing in — the page is tied to your account and is not accessible to recipients outside your team.

Managing your usage

Setting your audience limit

Audience refreshes are the largest part of Scanning under your direct control, and they can be capped. Set the audience limit on the Audience screen.

• Default: 5,000,000 UU per billing period
• Minimum: 2,000,000 UU
• The limit can be set higher than the default if more headroom is needed.

When the limit is reached, audience operations pause for the rest of the period. The following stop: saving an audience, editing one, viewing contacts, exporting CSV, instant sync, and scheduled syncs. An inline message appears on the action, and paused scheduled syncs are marked with the reason.

The limit resets automatically at the start of the next billing period. It can also be raised at any time, and operations resume immediately — nothing needs to be cleared or re-enabled. The limit cannot be set below the amount already used in the current period.

On agency plans, the agency admin sets each sub-account’s limit from the agency console. Sub-account users can see their limit but not change it. The limit is not shown on trial plans.

Data collection and delivery never stop

Ingestion and Activation are never paused, even when you exceed your allowance. Interrupting data collection or destination delivery would disrupt live campaigns, so the pipeline keeps running and the excess is billed.

Exceeding your allowance results in additional charges — never in lost data.

Reducing usage

The levers with the most impact, based on where usage accumulates:

Lever	Effect
Review your destinations	The largest lever. Every additional destination multiplies Activation usage. Removing destinations you no longer act on reduces it proportionally.
Reduce audience refresh frequency	Audiences that refresh hourly when daily is sufficient are usually the largest avoidable share of Scanning.
Filter at the source	Events that are never activated or reported on still consume Ingestion, Storage, and Scanning. Excluding them at the source removes all three.
Delete old data	Storage is billed per GB every month, so removing history you no longer need reduces it directly — and the saving repeats every month thereafter. A smaller stored volume also lowers Scanning, since audience refreshes and reports compute over less data.

Add-ons

Optional capabilities, priced separately from your plan and your usage:

Add-on	What it gives you	USD / month	INR / month
1P Domain Tracking	First-party tracking — events collected from your own domain (same domain tracking)	$29	₹2,999
Accounts Pack (for Agency plans)	Adds 5 accounts per unit	$99	₹8,999
Solution Engineer Support	A dedicated solution engineer	$250	₹22,500

Add-ons are charged on the same cycle as your plan, prorated from the date they are added. They do not affect the Usage Unit allowance or consumption.

Important

The add-on prices are current as of August 2026 and may be subject to change. Any revision will be communicated to your registered email address.

Frequently asked questions

What is a Usage Unit?
A single unit that covers all four kinds of usage, so there is one allowance to track instead of four.

Do unused Usage Units carry over?
No. The counter resets to zero on the 1st of each month.

Will data collection stop if I exceed my allowance?
No. Data continues to flow; the excess is billed instead.

What usually contributes the most?
Destinations. Every additional destination multiplies Activation usage.

Why did my bill go up when my traffic didn’t?
Usually a new destination, more frequent audience refreshes, or growing stored data. The usage view in Account Settings shows which.

How does this work on an agency plan?
One allowance covers the whole agency. All sub-accounts count toward it, and the breakdown shows the split.

Can usage be capped?
Audience refreshes can be capped — see Managing your usage. Data collection and delivery cannot be capped.

---

Pricing is subject to change

All pricing and conversion rates on this page — plan fees, Usage Unit rates, pack prices, and add-on prices — are current as of August 2026 and may be subject to change. Any revision will be communicated to your registered email address.