Download websites that use Braze

About Braze

Push notifications, lifecycle email and in-app messaging are usually thought of as work that happens after someone installs an app, out of sight of the public web. The reason a customer engagement platform turns up in a web technology index at all is the browser half of it, a script that recognises a returning visitor, records what they did on the site and feeds the same campaign logic that drives the mobile channels. As of October 2026 we record Braze on 90 sites, and the population is narrow by design, because the product is sold by Braze under a Proprietary licence to organisations that already run an audience across a site and an app at once.

The narrow count is the useful part rather than a weakness. A company that has bought a platform of this kind has already made several other decisions that show up in the same page source, including a tag manager, a consent tool, an analytics stack and often a session recorder. Reading those rows next to each other says more about how a marketing organisation is put together than any single vendor name does on its own.

Version data sharpens the picture. We hold 8 distinct versions of the browser SDK across that population, and the build we record most often is 5.1. Spread across many builds is informative for a hosted SDK, because the vendor expects the loader to keep itself current. When a range of older builds persists anyway, the usual explanation is that the bundle was pinned into a release pipeline and then left alone, which separates accounts with an active integration team from accounts that wired the tag up during a launch and moved on.

The product line goes back to 2011, so a site carrying the tag now may have been a customer for a long time or may have switched from a competitor last quarter, and page source alone will not say which. A per-domain lookup answers only whether one company is a customer. A downloadable list answers the question a research or sales team is actually asking, which is which companies in a segment run this, which of them run a competing engagement tool beside it, and which of them load it on account and checkout paths rather than only on a marketing page.

Two limits are worth stating plainly. Server to server messaging leaves nothing in a page, so any customer using the platform only for mobile or only through backend APIs is invisible to us. Injection through a tag manager container can also hide the script from a crawl that does not execute the container. Our figure is a floor, not a customer roster.