Which Technologies Are Commonly Used Alongside Magento?

Cloudflare, PayPal, Braintree, Adobe Marketing Cloud, Klaviyo, and WordPress are among the most common technology labels in our BuiltWith Magento dataset.

But a list of names only tells part of the story.

When we bought BuiltWith's All Live Magento Sites export, our first question was how many Magento sites were still around. The file contained 151,428 unique root domains.

For this article, we looked beyond the platform itself. We wanted to understand what surrounds it: the payment services, marketing tools, content systems, infrastructure, and frontend technologies that appear on the same domains.

The result is a useful picture of Magento's wider ecosystem. It also shows why a technology report needs to be read carefully. Two labels can describe the same group of sites. A payment logo is not a processing contract. A Cloudflare signal does not tell us where the Magento application runs.

A quick view of the surrounding stack

These are selected leading labels across the main categories in the export.

The percentages describe presence in this particular export. They are not vendor market shares, and the rows should not add up to 100%. A single domain can appear in several rows.

We use BuiltWith's labels as supplied. They describe detected signals, not a verified inventory of each merchant's active services.

Payments are one of the most visible parts of the ecosystem

PayPal was the most common label in the Payment Platforms field, appearing on 60,363 domains. Braintree and CardinalCommerce followed.

Other frequent labels included:

This field mixes different parts of a payment system. Card networks, wallets, processors, and authentication services are not interchangeable products. For example, CardinalCommerce provides 3-D Secure authentication services. CardinalCommerce service description

We also checked how often PayPal and Braintree appeared together.

34,845 domains had both labels. Counting either label produced 64,597 distinct domains, not the 99,442 we would get by adding the two totals.

That overlap tells us more than either number alone. The payment stack often contains several related signals, so this data should not be presented as a contest in which every merchant chooses exactly one provider.

It also cannot tell us whether a merchant currently processes transactions through a detected service. The 21,229 Wirecard labels, for example, are records to validate before treating them as current customer relationships. A visible library, old integration, or other detectable reference may remain without proving active use.

For product research, the next question is which combinations actually appear in working checkouts—and which integration problems those merchants face.

Marketing has three large visible groups

The Marketing Automation Platform field had three clear leaders by recorded label count:

Klaviyo is a useful example of how the dataset can guide further research. It appears on roughly one in five domains in the export, and Klaviyo documents a Magento 2 integration. There is a real integration path to investigate, not just a name that happens to appear in the table. Klaviyo Magento 2 documentation

That does not establish that all 30,994 domains use the integration, have paid accounts, or run effective marketing campaigns.

Likewise, the broad Adobe Marketing Cloud label does not identify every Adobe product in use. It also does not mean the merchant has an Adobe Commerce license.

The commercial questions come after detection: is customer data syncing correctly, are product feeds complete, and do events behave consistently across stores? The export can help identify a sample for that research. It cannot answer those operational questions by itself.

CRM is less visible, and some labels repeat

Only 12,558 domains, or 8.3%, had a value in the CRM Platform field.

Brevo, Salesforce, Salesforce Web to Lead, Hubspot, and dotdigital were the leading labels. Several also appeared in the marketing field.

That creates another counting trap. A Brevo label in two columns is not two customers or two separate integrations.

Within the CRM field, all 2,152 Salesforce Web to Lead domains were already included among the 2,972 Salesforce domains. The combined group therefore contains 2,972 domains, not 5,124.

A blank CRM field also does not establish that the merchant has no CRM. Internal tools and server-side connections may leave little evidence in the public pages captured by a technology detector.

This is particularly important when researching ERP, warehouse, and other operational integrations. The visible website is only part of the business system.

Cloudflare leads the infrastructure labels, but it is not an origin-hosting ranking

The Hosting Provider field was populated on 128,510 domains. Its largest label was Cloudflare Hosting, at 72,284 domains.

Other common infrastructure labels included:

Cloudflare can sit in front of a separate origin server, routing requests through its network. A visible Cloudflare signal therefore does not establish that Cloudflare hosts the Magento application itself. Cloudflare proxy documentation

The same site can have a hosting provider, a CDN, and other infrastructure services. Comparing these labels as if each represented an exclusive hosting choice would be misleading.

Fastly provides a concrete example of overlapping labels. The export contains 4,672 Fastly Hosted detections and 4,672 Fastly Load Balancer detections. Our domain-level check found that they occur on exactly the same set of domains.

Together, they still describe 4,672 domains.

We also kept labels such as Amazon, AWS Global Accelerator, Google, and Google Cloud separate. Combining them into vendor totals would require checking their domain-level overlap and deciding what each total is intended to measure.

WordPress shows that commerce and content can coexist

WordPress appeared on 24,480 domains, or 16.2% of the full export. Adobe Experience Manager appeared on 5,629, or 3.7%.

One possible explanation is that a business uses Magento for its store and another system for a blog or corporate website. Different applications may also run on different subdomains.

These are plausible arrangements, not architectures we have confirmed for every domain. Mixed labels can also reflect old pages, migration activity, or detection errors.

The export includes both general WordPress labels and version-specific labels. We counted the exact WordPress label for the figure above; we did not add its version counts to it.

The research opportunity is to understand how merchants manage content across those systems: navigation, search, analytics, and the handoff between editorial pages and the store.

Hyvä is a visible frontend choice

The Hyva Themes label appeared on 5,124 domains, or 3.4% of the export. Hyvä describes its product suite as built for Magento 2 and Adobe Commerce. Hyvä documentation

That makes it a more specific frontend signal than the generic Magento label. It can help define a group for research into theme compatibility, checkout behavior, and performance work.

However, 3.4% is not a verified share of all Magento 2 stores. The denominator here includes every domain in the general Magento export, and detection may be incomplete.

A single snapshot also does not tell us how quickly Hyvä adoption is growing or whether any particular store became faster after installing it.

Other ecommerce platforms are signals to investigate

The file also contained 7,350 Shopify labels. Of those, 7,013 appeared on domains that also had an explicit Magento label.

That is evidence of co-detection, not evidence that 7,013 merchants migrated from Magento to Shopify.

Possible explanations include separate storefronts, different applications under one domain, migration in either direction, or stale signals. A dated technology history and a site review would be needed to distinguish them.

This matters because a migration story can sound convincing even when the dataset only shows two names in the same row.

What the surrounding technologies tell us

The strongest pattern is that the Magento footprint contains many other visible technology layers. Payments, marketing, infrastructure, content, and frontend tools all have substantial representation.

For agencies and software vendors, this suggests research beyond the core platform: which combinations are common among active merchants, where compatibility problems occur, and where data fails to move reliably between services.

But frequency is only a starting point. A common label does not prove demand for another tool. A rare label does not prove that the corresponding business function is absent.

The next useful step is to compare these combinations by country, Magento version, traffic, and business scale, then validate a sample of working stores. That would turn a list of detected technologies into a clearer understanding of how merchants actually operate.

Data and methodology

We analyzed the purchased All Live Magento Sites — 2026-08-24 CSV, containing 151,428 unique root domains. We split the technology fields on semicolons, trimmed labels, and counted each exact label at most once per domain within its field.

All percentages in this article use the full 151,428-domain export as the denominator. We preserved the export's categories and labels rather than treating them as a standardized taxonomy of products. Counts across categories and related labels can overlap.

As a consistency check, we repeated selected counts using only the 142,976 rows with an explicit Magento label. This retained 67,317 Cloudflare Hosting detections, 59,354 PayPal detections, 30,850 Klaviyo detections, 21,779 WordPress detections, and 5,112 Hyva Themes detections. These signals therefore remain substantial under that narrower filter.

The export is not a complete software inventory. It does not include dedicated fields for every possible technology category, such as analytics or search, and blank fields do not prove non-use. We have not manually verified every site, its active subscriptions, or its integration architecture.

BuiltWith's Magento report and export field descriptions provide context for the source data. The figures here describe our dated export, not the current totals on its public pages.