Adobe Analytics
Measured in server calls per month. Overusage is evaluated over an annual cycle and billed monthly in arrears as incurred.
Customer Journey Analytics
Measured in rows of data per year, with a separate quarterly overusage methodology and its own ingestion limits.
Extended Data Capacity
Separately licensed rows that support analysis of data beyond the standard 13-month CJA window.
How to read the periods
Monthly usage-to-commit comparisons are monitoring views. Adobe Analytics overusage is evaluated over an annual cycle; CJA row overusage uses a quarterly methodology; and CJA ingestion is measured against the applicable annual ingestion limit. A month showing above 100% is not, by itself, an overage.
Where consumption stands today
Select a product to see monthly usage against the contracted commitment. Bars in yellow are within the commitment for that month; bars in red exceed it. The dashed line steps up when your commitment increased.
Adobe Analytics — server calls
The monthly commitment increased from 975M to 2.650B server calls effective May 1, 2026. Since that increase, monthly consumption has remained below the entitlement — 91%, 88% and 84% in May, June and July.
CJA Prime — rows of data
Prime entitlement rose to 28.5B rows annually under the current agreement. Earlier months reflect the historical 12.8B commitment. Row overusage is evaluated quarterly, not by any single month.
Extended Data Capacity
EDC of 7.125B rows annually was added beginning May 2026 to support analysis beyond the standard CJA window.
Total CJA capacity
Combining CJA Prime and Extended Data Capacity, total licensed capacity is 35.625B rows annually today.
Ingestion vs. annual entitlement
Your annual ingestion entitlement equals three times licensed CJA capacity — 106.875B rows today. The monthly percentages shown are for reference only; the entitlement is measured against the cumulative annual allowance.
Reading the channel columns
“Primary” and “secondary” describe how a call is classified; “browser” and “mobile” describe the channel that generated it. Browser and mobile are components of the primary/secondary totals — they are not added on top. Dollar General reported zero secondary calls in every month shown, so total usage equals primary usage throughout.
How Adobe Analytics is measured and billed
The questions your team raised, answered against the executed Sales Order and applicable product terms.
Metrics & definitions
What is the primary billing metric for Adobe Analytics?
The primary metric is server calls per month. Dollar General currently licenses 2.650 billion server calls per month under Analytics Evolution Prime to CJA, effective May 1, 2026 through April 30, 2028.
Is billing based on server calls, payload size, data volume, or unique visitors?
For Adobe Analytics, the contractual metric is server calls. Payload size, data volume, unique visitors and the number of variables in a hit are not separate billing metrics. CJA is licensed separately, in rows of data per year.
How does Adobe define a billable server call?
A server call — also called a hit or image request — is a data-collection request sent to Adobe Analytics collection servers from a website, application, SDK or supported ingestion method. Each qualifying tagged request or imported offline row is described as a Primary Server Call.
Which activities generate billable server calls?
Qualifying activity can include page views, custom events, custom or tracked links, file downloads, exit links, campaign container requests, mobile SDK events, Data Insertion API requests and rows imported from offline sources. Each qualifying request or imported row is generally counted as one Primary Server Call.
Do all server-call types have the same billing weight?
Yes. Each qualifying event type is counted as one Primary Server Call — event types are not weighted differently.
Dollar General’s current reporting shows consumption recorded almost entirely as primary server-call usage, so all reported Analytics consumption is effectively measured against the contracted entitlement using the same counting methodology.
Do extra eVars, props, dimensions, or a larger payload affect billing?
No. Consumption is measured by server-call volume, not payload complexity. Variable quantities define configuration capacity; server calls remain the consumption metric.
Populating more licensed variables within a single qualifying hit does not create an additional server-call charge, provided the implementation stays within the configuration limits.
Storage, retention & measurement
Are there charges for data storage, processing volume, or retention beyond server calls?
Adobe Analytics includes 25 months of data storage from collection or receipt. Retention beyond that requires separately licensed Adobe Analytics Storage. The reviewed Sales Order does not establish a separate charge based solely on processing volume.
What is the usage measurement period?
The license metric is stated per month, but Adobe Analytics overusage is evaluated over an annual overusage cycle. Monthly licensed quantities are totaled over that cycle, and any overusage is billed monthly in arrears as incurred.
Are there additional charges for retention, storage, processing, or exports?
Additional retention beyond 25 months requires separate storage licensing. There are no separate export-based or processing-volume charges.
What server-call entitlement is included today?
The current Analytics Evolution Prime to CJA entitlement is 2.650 billion server calls per month, from May 1, 2026 through April 30, 2028. This replaced the 975 million monthly commitment in place from January through April 2026.
Server-call types
What are the contracted limits for primary, secondary, and mobile server calls?
The Sales Order provides one consolidated commitment of 2.650 billion server calls per month. It does not set separate contracted quantities for primary, secondary, browser or mobile calls — all categories count equally toward the total.
Total usage is the sum of primary and secondary calls; browser and mobile are channel-level breakdowns of those totals. Because reporting shows zero secondary calls, total usage equals primary usage for every month.
How are secondary server calls treated?
Secondary calls are treated the same as primary calls under your contract, and Dollar General is not currently reporting any secondary calls.
Do multi-suite tagging implementations generate additional billable calls?
Adobe documentation generally describes the first report-suite request as the primary call, with copies delivered to additional report suites through multi-suite tagging classified as secondary calls. The Sales Order does not state separate contract-specific billing treatment for those secondary calls.
Do VISTA rules create additional billable calls?
Adobe documentation generally identifies copies created or moved through certain VISTA processing as secondary server calls. The reviewed Sales Order does not establish a separate VISTA-specific entitlement or rate.
Overages & evaluation
How are Adobe Analytics charges calculated and reported?
Usage is measured against the monthly commitment and evaluated across the annual overusage cycle. The contracted overusage rate is $41.20 per million server calls, billed monthly in arrears as incurred. Operational reporting provides monthly consumption views.
What happens if we exceed our contracted server-call limits?
If consumption exceeds the committed quantity after the annual overusage methodology is applied, overusage fees apply under the Sales Order at $41.20 per million server calls, billed monthly in arrears as incurred.
What are the overage rates across products?
Adobe Analytics: $41.20 per million server calls (annual evaluation). CJA Prime: $24.29 per million rows (quarterly). CJA Extended Data Capacity: $5.00 per million rows (quarterly).
Are overages evaluated monthly, quarterly, or annually?
Adobe Analytics overusage is evaluated annually (though the metric is stated per month and billed monthly in arrears). CJA Prime and EDC overusage are evaluated quarterly. CJA ingestion is governed by the applicable annual ingestion limit.
Are Adobe Analytics calls billed separately from other Experience Cloud products?
Yes. Adobe Analytics and CJA appear as separate product lines with different license metrics — server calls for Analytics, rows per year for CJA Prime and EDC — each with its own overusage provisions.
July 2026 usage by report suite
Adobe can provide server-call reporting at the individual report-suite level. In July, usage was concentrated in the dollargeneralglobal-production suite, which accounted for nearly all activity — predominantly from mobile app traffic — with no secondary calls reported across any suite.
| Report suite (RSID) | Primary calls | Browser primary | Mobile primary |
|---|---|---|---|
| dollargeneralglobal-production | 2,228,690,564 | 275,581,385 | 1,953,109,179 |
| dollargeneralglobal-nonproduction | 1,120,967 | 774,141 | 346,826 |
| dollargeneralapp | 96,141 | 0 | 96,141 |
| dollargeneralapp-development | 10,143 | 0 | 10,143 |
| dollarpopshelf-global-production | 7,310,778 | 4,938,919 | 2,371,859 |
| dollarpopshelfglobal-nonproduction | 62,808 | 51,014 | 11,794 |
| dollarpopshelf-production | 3,201 | 3,201 | 0 |
| dollargeneral-production | 69 | 69 | 0 |
| dollargeneral-development | 14 | 14 | 0 |
| Total | 2,237,294,685 | 281,348,743 | 1,955,945,942 |
Secondary server calls were zero across every report suite. Mobile calls represented the majority of total server-call volume.
Your contracted growth path
The current agreement was structured to support migration to CJA while providing significantly greater analytics and ingestion capacity — growing to 45B CJA rows and 135B ingestion rows annually by 2029.
| Contract period | AA server calls | CJA Prime rows | EDC rows | Total CJA | Annual ingestion* |
|---|---|---|---|---|---|
| Through Apr 30, 2026 | 975M / mo | 12.8B | Included | 12.8B | 38.4B |
| May 1, 2026 – Jan 31, 2027 Current | 2.650B / mo | 28.500B | 7.125B | 35.625B | 106.875B |
| Feb 1, 2027 – Jan 31, 2028 | 2.650B / mo | 32.000B | 8.000B | 40.000B | 120.000B |
| Feb 1, 2028 – Jan 31, 2029 | 2.650B / mo | 34.000B | 8.500B | 42.500B | 127.500B |
| Feb 1, 2029 – Sep 30, 2029 | 2.650B / mo | 36.000B | 9.000B | 45.000B | 135.000B |
*Annual ingestion entitlement is calculated as 3× licensed CJA capacity, consistent with the CJA licensing model.
Adobe Analytics
2.650B server calls / month · overage $41.20 / million · annual evaluation · 25-month retention.
CJA Prime
28.500B rows / year · overage $24.29 / million · quarterly evaluation · standard 13-month data window.
Extended Data Capacity
7.125B rows / year · overage $5.00 / million · supports analysis beyond the standard CJA window.
Adobe Analytics configuration capacity
Variable quantities define configuration capacity — they do not change the server-call consumption metric.
| Configuration component | Entitlement |
|---|---|
| Conversion variables (eVars) | 250 |
| Traffic variables (props) | 75 |
| Custom events | 1,000 |
| List variables | 3 |
| Segments | 500 |
| Calculated metrics | 500 |
| Classification rule sets | 50 |
| Processing rules | Included |
| Virtual report suites | Included |
Illustrative overage examples
A step-by-step walkthrough of how overage is evaluated under each methodology, so the numbers earlier in this summary are easy to interpret.
Adobe Analytics — annual cumulative method
Adobe does not evaluate a single month in isolation. It compares total consumption across the annual overusage cycle to the total committed quantity available over that same period. At 2.650B server calls per month, the annual entitlement is 2.650B × 12 = 31.8B server calls, with overage billed at $41.20 per million.
High and low months are fine — until the annual bucket is exhausted
Months 8 and 9 individually exceed the 2.650B monthly commitment, yet no overage applies because cumulative usage is still under the 31.8B annual entitlement. The overage is only triggered when the running total crosses that line in Month 10.
| Month | Monthly usage | Cumulative usage | Annual entitlement |
|---|---|---|---|
| Month 1 | 2.1B | 2.1B | 31.8B |
| Month 2 | 2.2B | 4.3B | 31.8B |
| Month 3 | 2.3B | 6.6B | 31.8B |
| Month 4 | 2.4B | 9.0B | 31.8B |
| Month 5 | 2.5B | 11.5B | 31.8B |
| Month 6 | 2.6B | 14.1B | 31.8B |
| Month 7 | 2.7B | 16.8B | 31.8B |
| Month 8 | 2.9B | 19.7B | 31.8B |
| Month 9 | 3.1B | 22.8B | 31.8B |
| Month 10 Over | 9.5B | 32.3B | 31.8B |
Customer Journey Analytics — quarterly average method
CJA is licensed in rows of data and evaluated on a quarterly average, not any single month. CJA Prime is 28.500B rows and Extended Data Capacity (EDC) is 7.125B rows — 35.625B total. A single high month does not, by itself, create an overage; the quarterly average is what matters.
February runs high, but the quarterly average stays under the Prime commitment
| Month (Q1) | Prime rows |
|---|---|
| January | 25B |
| February | 30B |
| March | 27B |
Every month in the quarter runs high, so the average exceeds the Prime commitment
| Month (Q2) | Prime rows |
|---|---|
| April | 31B |
| May | 32B |
| June | 34B |
EDC is evaluated the same way, against its own 7.125B entitlement
In plain language
A yearly bucket
Adobe Analytics is a bucket of server calls for the year — 2.650B per month, 31.8B annually. High and low months are expected; overage begins only when cumulative usage passes the total annual allowance.
A quarterly average
CJA looks at the average Prime and EDC rows across the quarter. If that average exceeds licensed capacity, overage applies to the excess. One high month alone does not create an overage.
A separate guardrail
Ingestion is evaluated on its own against the annual allowance — 3× licensed capacity, or 106.875B rows today — separately from Prime and EDC row utilization.
Bill Conaway
Data and Insights Specialist