Bots, prefetch and internal traffic made up 10 to 25 percent of the counted server calls, and the contract already excludes them, which is why the opening overage claim ran 2 to 5 times the settlement
An overage notice arrives as arithmetic and reads as fact. It is a measurement, and the measurement counts traffic the agreement says should never have been billed.
Prepared by Redress Compliance · August 18, 2026 · Adobe advisory. 20 to 30 Adobe disputes advised, 2024 to 2025.
Executive summary
Bot and prefetch noise made up 10 to 25 percent of counted calls. Bots, prefetch requests and internal traffic that the contract excludes, counted anyway, across the disputes advised.
The opening overage notice ran 200 to 500 percent above the settled figure once double counting was removed. That is a measurement gap, not a negotiation win.
Scope creep lifted billable calls 15 to 30 percent with no change in usage. eVar and prop expansion across report suites raises the count on its own.
The twelve month rolling window is what turns a busy quarter into an annual breach. Adobe sums server calls across twelve months against the annual entitlement, so one spike stays in the number for a year.
What actually triggers an Adobe Analytics audit?
A server call overage notice, in most cases. Adobe monitors monthly server call volume against contract entitlement automatically, and sums it across a rolling twelve months before comparing to the annual number.
The measurement basis is set out in Adobe's own server call usage documentation, which is the first document to read and the one most buyers see for the first time after the notice arrives.
| Trigger | What Adobe measures | Where the buyer defense sits |
|---|---|---|
| Server call overage | Monthly volume per report suite, rolled over twelve months | Accounting accuracy, which is this brief |
| Multi suite scope drift | Report suites beyond the contracted count | Scope discipline at the suite boundary |
| Customer attribute ingestion | Attribute uploads at scale | Contract language on what ingestion counts as |
The rolling window keeps a spike alive for a year
One heavy quarter stays inside the twelve month sum until it ages out. That is why a campaign, a migration or a bot wave shows up as an annual entitlement breach months after the traffic has gone.
What is in the count that should not be?
Bots, prefetch requests and internal traffic. Across the disputes advised they made up 10 to 25 percent of counted calls, and the contract already excludes them, which means removing them is enforcement rather than negotiation.
The same pass usually finds double counting: the same interaction billed twice through overlapping implementations. Together those two corrections are most of the distance between the opening claim and the settlement.
An overage notice is a measurement, not a finding. It arrives as arithmetic, which makes it feel settled. The arithmetic is only as good as the exclusions applied before it, and those are the buyer's to check.
The Adobe compliance and audit brief
What Adobe measures, the exclusions the contract already grants, the scope boundary between report suites, and the settlement arithmetic.
Get the brief →What 20 to 30 Adobe disputes showed
Across roughly 20 to 30 Adobe disputes Morten Andersen advised on between 2024 and 2025, the opening server call overage claim ran 2 to 5 times the eventual settlement.
The first claim was inflated in a specific and repeatable way. Once double counting was removed, the notice sat 200 to 500 percent above the figure both sides eventually agreed.
Bot and prefetch noise accounted for 10 to 25 percent of counted calls on its own. This is traffic the contract excludes, counted because nobody had configured the exclusions or checked that they were working.
Scope creep did the rest. eVar and prop expansion across report suites lifted billable calls 15 to 30 percent with no change in what the business was actually measuring.
None of those three corrections is an argument about price. All three are arguments about what was counted, which is why the evidence has to be assembled before the response goes back.
- Your agreements decoded into plain English, with the exclusions the contract already grants
- Coverage grid: liability caps, audit rights and tolerances checked in one pass
- A defensible position paper generated in minutes rather than weeks
Where does scope quietly expand the bill?
At the report suite boundary. Additional suites beyond the contracted count are scope expansion, and eVar and prop growth inside them raises billable calls without anyone deciding to spend more.
- Count the live report suites against the contracted number, because suites are created quickly and retired slowly.
- Track eVar and prop growth as a cost line, since it lifted billable calls 15 to 30 percent with no usage change.
- Watch the Customer Journey Analytics boundary, which bills on events ingested rather than server calls, so the metric changes as workloads move.
The wider Adobe position sits in our Experience Cloud licensing guide, the ETLA negotiation guide, and the compliance audit risk guide.
The 2026 letters narrowed the tolerance
Renewal letters have tightened the prior overage tolerance and added explicit removal of the audit cap. That makes the accounting work more valuable, not less, because there is less contractual slack to absorb a miscount.
How is the settlement actually reached?
By rebuilding the count and pricing what survives. The default settlement is the price file plus the overage rate, and that default moves where the buyer brings reporting discipline evidence rather than an objection.
Adobe documents the platform and its measurement on the Adobe Analytics product pages, and the contract sits on top of that. Both are needed to answer a notice.
Evidence beats objection
A disputed number without a reconstruction is an opinion. A reconstruction that shows the excluded traffic, the double counting and the suite boundary is what took the claim from 2 to 5 times down to the settled figure.
What the disputes measured, 2024 to 2025
Two cuts of the engagement file frame the size of the opening position.
The overage notice as issued, against the figure both sides agreed once the count had been rebuilt.
Bots, prefetch and internal traffic already excluded by the contract, counted because the exclusions were not verified.
Both numbers describe the same thing from two directions: the notice measures more traffic than the agreement says is billable.
Watch the briefing · 5:12Right Sizing Your Adobe Estate Before You NegotiateThe estate work that decides the renewal, done before the conversation about rate begins.
Your first five moves
- Rebuild the count before responding to the notice, because the opening claim ran 2 to 5 times the settled figure across the disputes advised.
- Verify the bot and prefetch exclusions are configured and working, since that traffic was 10 to 25 percent of counted calls.
- Find the double counting from overlapping implementations, which is the correction that moves the number furthest.
- Reconcile live report suites against the contracted count, and track eVar and prop growth as a cost line rather than a configuration detail.
- Read the 2026 renewal language before signing it. The Adobe practice rebuilds the count before the response goes back, which is the only version of this that settles low.
Frequently asked questions
How inflated is a typical Adobe Analytics overage claim?
The opening claim ran 2 to 5 times the eventual settlement across the disputes advised, sitting 200 to 500 percent above the agreed figure once double counting had been removed.
Do bots count as server calls?
The contract excludes them, but they were counted anyway in the disputes advised. Bots, prefetch and internal traffic made up 10 to 25 percent of counted calls.
What is the twelve month rolling window?
Adobe sums server calls across twelve months and compares that total against the annual entitlement, so a single heavy quarter stays inside the number until it ages out.
How does scope creep raise the bill?
eVar and prop expansion across report suites lifted billable calls 15 to 30 percent with no change in usage. Additional suites beyond the contracted count are scope expansion in their own right.
What triggers an audit in the first place?
Server call overage is the most common trigger, followed by multi suite scope drift and customer attribute ingestion at scale.
Is the settlement negotiable?
Yes. The default is the price file plus the overage rate, and it moves where the buyer brings a rebuilt count and reporting discipline evidence rather than an objection.
What changed in the 2026 contract language?
Renewal letters narrowed the prior overage tolerance and added explicit removal of the audit cap, which makes accurate accounting more valuable rather than less.
Does Customer Journey Analytics use the same metric?
No. CJA bills on events ingested rather than server calls, so the metric changes as workloads move between the two and the crossover needs planning.
What is the first thing to do on receiving a notice?
Rebuild the count. Verify the exclusions, find the double counting, and reconcile the report suites before any response goes back.
Is this a compliance problem or a measurement problem?
Usually a measurement problem. The notice arrives as arithmetic, and the arithmetic is only as good as the exclusions applied before it.
