Companies Using Adobe Target

The most tightly coupled stack we measure

Most technology pages report co-occurrence as context. On Adobe Target it is the main finding. Adobe Experience Platform Launch appears on 82.14% of Adobe Target domains and Adobe Analytics on 68.83%. Both figures sit many times above their averages across our corpus, and together they describe a product that is almost never found alone.

The industry data says the same thing from another direction. Adobe Target's leading sectors are Retail at 16.38% and Motor Vehicle Manufacturing at 13.04%. Adobe Experience Manager's leading sectors are Retail and Motor Vehicle Manufacturing. Two products with different functions, sold separately, show the same customer shape because they are bought by the same organisations under the same commitment.

82.14% of Adobe Target deployments also run Adobe Launch. This is not a personalization tool competing on features; it is a component of an estate decision already made.

What that means commercially

For anyone using this list to sell, the practical consequence is that Adobe Target is a qualifier rather than a target in itself. A domain running Target is, with high reliability, an organisation that has already committed budget to Adobe Experience Cloud, has an implementation partner, and has a procurement process that has cleared enterprise software before.

The corollary matters for anyone selling against Adobe: displacing Target alone is unlikely, because the product is rarely the reason it is there. The 79.98% Google Tag Manager figure is the interesting crack in that wall. Most of these estates have not standardised on Adobe's own tag infrastructure, and run Google's alongside it.

Reading a fragmented category

Adobe Target ranks 4th of 50 in Website Personalization with 5.61% share, behind Zoho PageSense, Rebuy and Bold Commerce. That ordering deserves an explanation rather than a defence.

This category is unusually flat. No technology in it exceeds 8.3%, and it groups genuinely different things: enterprise personalization engines, Shopify ecommerce apps, and product-onboarding widgets all alter what a visitor sees, so all three sit in the same bucket. The tools above Adobe Target serve small and mid-market ecommerce, where install counts are naturally higher. The ranking measures how many sites run each tool, and comparing an enterprise engine to a Shopify app on that basis tells you about distribution, not capability.

An established, consumer-facing base

Companies founded before 1960 are the largest age group at 21.60%. Retail, automotive and hospitality together exceed 36% of matched customers. Organisations above 1,000 employees account for 15.10%, including 5.95% above 10,000 staff.

This is a portrait of large consumer brands with long histories and complex digital estates, which is precisely the buyer for whom personalization has measurable revenue consequences. The unusually strong Canadian share at 8.43% and Brazilian share at 4.26% are worth noting for anyone segmenting this list geographically, since both run ahead of what a default assumption about enterprise software adoption would predict.

Adobe Target and Adobe Experience Manager have almost the same industry profile. When two separately sold products show the same customer shape, the customer is buying the suite.

Why there is no migration section

We publish switching data only where we can show it is genuine, and Adobe Target produces almost none worth reporting. On our observation window we recorded a single domain arriving from a tracked category rival, which is not a basis for any claim about competitive movement.

That absence is itself consistent with everything else on this page. A product embedded in a suite commitment does not churn independently of that commitment, so the movement worth watching would be at the Adobe Experience Cloud level rather than between Target and a category neighbour. TechnologyChecker.io leaves the section empty rather than widening the window until numbers appear.

What this measurement cannot see

Detection requires the Target library to load on a page we crawled. Personalization deployed only inside authenticated areas, in mobile apps, or through server-side delivery will not register. The 11,160 figure is therefore a floor on live browser-facing deployments, and the growth from 8,806 in June reflects our detection reach widening across those months as much as any market change. July and August are nearly flat, which is the more honest read on the current trend.