Companies Using Adobe Experience Manager

Reading a domain count that is not a customer count

Adobe Experience Manager produces one of the more misleading raw numbers in our corpus, and the reason is structural. We detect AEM on 55,969 domains. That is not 55,969 customers. AEM exists to run large website estates, and a single organisation routinely operates it across dozens of separate domains: one per brand, one per market, one per campaign, plus microsites that live and die on a marketing calendar.

The size distribution makes the effect visible. Companies of 1 to 10 employees appear as the largest bucket at 47.52%, which is not a plausible description of who licenses an enterprise content platform. What it actually captures is that a regional or brand domain often resolves to a small local entity in company records, even when it belongs to a multinational. Organisations above 1,000 employees account for 10.23% of matched domains, and that figure is closer to where the purchasing decision sits.

AEM's 47.52% micro-business bucket is an artefact of estate structure, not a customer segment. Large organisations run many small domains, and each one counts once.

The industry mix is physical, not digital

Retail leads at 5.34% of matched domains, followed by Motor Vehicle Manufacturing at 4.23%. Adding Restaurants at 3.53% and Hospitality at 3.10% puts consumer and physical-goods businesses at 16.2% of the base. Financial Services, Insurance and Banking add a further 10.59%.

This is a different profile from most content management platforms, which skew toward software, agencies and media. What unites AEM's leading sectors is the shape of their web presence rather than their industry: a car manufacturer runs separate sites per model, market and language; a restaurant group runs sites per brand and country; a retailer runs campaign sites alongside the main storefront. Managing that sprawl centrally, with shared assets and governed templates, is the specific problem AEM is sold to solve. The industry mix is really an estate-complexity mix.

Germany and India both run hot

The United States accounts for 10,951 matched companies, with Germany (2,247) and the United Kingdom (2,170) close behind, then India (984). Both the German and Indian shares run above what our corpus average would predict.

The German result follows the industry data directly: European automotive and industrial manufacturers are among the heaviest users of multi-market content estates, and they appear throughout this list. The Indian result has a different cause. India hosts a large concentration of Adobe implementation partners and systems integrators, and the top of the named list reflects it, with Tata Sons, Tata Consultancy Services, Infosys, Cognizant and Wipro all present. Some of those detections are the integrators' own properties rather than client work, which is worth knowing before using the list for prospecting.

The WordPress corridor is real

The most commercially interesting movement on this page is the exchange with WordPress, and it runs in AEM's favour. On our current observation window, 3,079 domains now running AEM had previously been detected on WordPress, while 876 domains that dropped AEM are now on WordPress.

A migration claim like that deserves scrutiny, because a domain can appear to switch when it simply runs both platforms on different hosts. We tested for it: of the 3,079 domains counted as arriving from WordPress, only 120 still show WordPress anywhere on the domain, or 3.9%. That is low enough to treat the corridor as genuine replacement rather than coexistence. The direction is consistent with what the size and industry data imply, which is organisations consolidating scattered WordPress properties into a single governed estate.

Only 3.9% of the domains we count as moving from WordPress to AEM still run WordPress anywhere on the domain. This corridor is replacement, not coexistence.

AEM is a proxy for the whole Adobe stack

Adobe Experience Platform Launch appears on 66.54% of AEM domains and Adobe Analytics on 21.53%. Both sit far above their averages across our corpus. In practical terms, finding AEM on a domain is a strong predictor that the organisation has committed to Adobe's wider experience stack, which is a larger and stickier commercial relationship than a content platform alone.

The corollary is equally useful: Google Tag Manager still appears on 65.84% of AEM domains and Google Analytics on 58.79%. Most AEM estates run Adobe and Google measurement side by side rather than standardising on one. Anyone selling analytics, consent, or tag governance into this list should assume a dual-vendor environment rather than an Adobe monoculture.

What this measurement cannot tell you

AEM detections come from signatures the platform emits when it renders a page, including component wrappers, JCR paths and client library directories. That makes a positive detection reliable. It also means the count only sees pages we crawled, so estates behind authentication, and sites served through heavy edge rewriting that strips the signatures, will be undercounted. TechnologyChecker.io publishes 55,969 as a floor on AEM's web-visible footprint, and the growth from 32,204 in June to 55,969 in August reflects our detection reach widening across those months as much as any change in the market.