Ask a team that has been running Adobe Campaign Classic for five years which build they are on. You will get an approximate version, usually the one from the go-live project, and almost never a build number. That is not carelessness. Nobody ever explained what the number is for.
It is for three things: knowing whether your platform still receives fixes, knowing which third party systems are genuinely supported on your installation, and knowing whether the incident you are chasing has already been fixed elsewhere. The vocabulary and the gestures fit on one page.
Adobe separates two operations, and confusing them causes a good deal of misunderstanding in steering committees.
A build upgrade is a change of build within the same version. The example in Adobe's own documentation is moving from v7 build 9026 to build 9032. A version upgrade is a change of major version. One point matters above the rest: each build is cumulative. Applying the latest one gives you everything that came before it, so there is no need to step through intermediate builds. Source: the Build upgrade FAQ in the Adobe Campaign Classic documentation, updated 12 October 2026.
The full version reads across three components, and the build number is the one you deal with day to day. In "7.4.5 build 9420", it is the 9420 that tells you whether you are current. The package names Adobe ships carry that same number: nlserver6-v7-XXXX.rpm, nlserver6-v7-XXXX-amd64_debX.deb and setup-client-6.XXXX.exe.
One rule is strict: the server and the client console must be on the same version. The documentation states it without qualification, and the compatibility matrix repeats it among its own reading rules.
This part is less widely known: since version 19.2, every published build carries a status. That status decides whether Adobe deploys it, fixes it, or expects you to move off it. Source: the Campaign Classic release notes overview, updated 15 October 2026.
| Status | What Adobe says | What you do with it |
|---|---|---|
| General Availability | Latest stable build, recommended | This is your target. Nothing to justify. |
| Limited Availability | Deployed on request | It will not reach you on its own. You have to ask for it, so you need a reason. |
| Deprecated | No longer deployed, no further fixes, upgrade required | You are frozen with no safety net. Treat it as a work item, not a footnote. |
One detail prevents a misreading: General Availability does not necessarily point to a single build. On 15 October 2026, two builds held that status at the same time, 7.4.5 build 9420 and 7.4.4 build 9403. Ten builds were published between March and October 2026. Being "on GA" is therefore not the same as being on the latest build.
⚠️ A build marked Deprecated receives no further fixes: Adobe no longer deploys it and asks you to upgrade. If your reading lands on that status, the subject stops being technical and becomes a planning item.
On the console it takes a second: the Help menu, then About. The screen shows both the console version and the server version, which lets you check the alignment rule above at a glance.
On the server, the command to use is nlserver pdump. It returns the full version and the build date:
nlserver pdump
7.X YY.R build XXX@SHA1
<build date>
The fragment after the at sign is a SHA1 hash. You do not need it to make a decision, but it helps when support asks you to identify precisely what you are running. Source: the Adobe Campaign upgrade page, updated 27 June 2026.
Take that reading on every environment, not just production. A pre-production trailing six builds behind production is a trap waiting for your next acceptance cycle.
💡 A useful habit: record each environment's build in the same table, with the date of the reading. At the next incident you will know within ten seconds whether pre-production and production are running the same code.
The v7 release notes are organised as one page for the current release plus a history by year. Read end to end, they are indigestible. Read with an intention, they take ten minutes.
The v7 context frames that reading. The 2025 and 2026 builds contain almost nothing but fixes and security fixes, with one notable exception, build 9400, which brings the move to the Adobe Analytics 2.0 API. So you are not looking for new features in these notes. You are looking for two specific things: a fix that matches an incident you already know about, and an announced removal that touches your scope. Sources: the latest release page, updated 15 October 2026, and the 2025 release history.
On removals, the dedicated page is short and worth bookmarking. As of 5 October 2026 it carried a single dated removal: the Netsize SMPP connector, targeted for January 2027. If you use it, that is a planning item rather than a watch item. Source: the Campaign Classic deprecated features page.
One habit gets forgotten: the compatibility matrix describes the systems supported for the latest build, not for the version in general. Moving up a build can therefore change what is supported on your installation, in either direction. Do not read the release notes without the matrix open beside them.
The answer depends entirely on your deployment model, and this is the question that stalls plans most often.
| Deployment model | Who runs it | How it starts |
|---|---|---|
| Hosted | Adobe | Adobe performs the upgrade. Critical security patches are applied without prior notice. |
| Managed Services | Adobe, through Customer Care | You raise a request with Customer Care. |
| Hybrid | Adobe, through Customer Care | Same route, through Customer Care. |
| On-premise | You | You download the latest General Availability build and apply it yourself. |
Specific hotfixes go through Customer Care in every case. On timing, production upgrade windows run Monday to Thursday, with Friday reserved for non-production. On cadence, Adobe commits to a version upgrade at least once a year: if your platform has not moved in three years, Adobe's rhythm is not the reason.
The term still turns up in specifications, meeting notes and supplier proposals. It no longer points to anything current.
Gold Standard was a maintenance series for version 19.1, with 9032@... builds published between August 2019 and September 2021. All of its builds are marked deprecated. The old Adobe page redirects to the release notes overview, and the term no longer appears in current documentation. Source: the Gold Standard page in the Campaign Classic documentation, checked 22 January 2026.
In practice: anyone advising you today to "stay on Gold Standard" is advising you to stay on a deprecated build of a 2019 version. The question is not whether you are on Gold Standard, it is whether your build is in General Availability. To place that decision in the wider product lifecycle, see Adobe Campaign Classic v7: versions, support and what Adobe actually says, which covers the 31 December 2030 core support date and the gap between the end of life matrix and the product documentation.
Version 8 does not carry this vocabulary over. It uses a major, minor, patch scheme on a two to three month cadence. The latest documented version is 8.9.4, dated 15 October 2026. Source: the Campaign v8 upgrades page, updated 1 September 2026.
More to the point, the v8 documentation does not describe build statuses equivalent to the three in v7. So you cannot transpose the question "is my build still recommended" from one version to the other: in v7 it has a documented answer, in v8 it has to be asked differently, through the version number and its date.
If you keep one routine from this: run nlserver pdump on every environment, note the build number, check its status on the release notes overview, and compare the console version with the server version through Help then About. Four pieces of information, a quarter of an hour, and you finally know where you stand.
I take a real reading of your Adobe Campaign environments, build statuses, gaps between production and pre-production, and tell you whether a build upgrade is warranted.
Let us talk about your platform