runsonwhat

BNP Paribas's tech stack

What does BNP Paribas use?

BNP Paribas (bnpparibas.jp) uses at least 9 tools we can see from public records, including Google Analytics for analytics, WordPress for its website and dmarcian for security. Last checked .

Based in
Japan
Founded
1987
LinkedIn
Company page
Re-check liveVisit bnpparibas.jp
Tools found
9
Categories
6
Layers
4 of 5
Last checked
Oct 2026

BNP Paribas's stack, layer by layer

Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.

Application

1 tool, what the product is built with

Frontend

Data & Observability

3 tools, what they measure and store

Analytics

Go-to-market

4 tools, how they find and keep customers

Website & CMS

Marketing

Ads & Pixels

Company Ops

1 tool, what the team runs on day to day

Security & Compliance

Companies like BNP Paribas also use

Tools common among companies with a similar stack that we haven't found at BNP Paribas.

Companies with a stack like BNP Paribas's

Ranked by shared tools, with rare tools counting more.

BNP Paribas tech stack FAQ

What tools does BNP Paribas use?

We've found 9 tools at BNP Paribas (bnpparibas.jp). Application: jQuery. Data & Observability: Google Analytics, Google Tag Manager and Matomo. Go-to-market: Google Ads, WordPress and Yoast SEO. Company Ops: dmarcian. Last checked October 4, 2026.

What analytics tools does BNP Paribas use?

BNP Paribas uses Google Analytics, Google Tag Manager and Matomo for analytics. We found Google Analytics through website code.

What CMS does BNP Paribas use?

BNP Paribas uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does BNP Paribas use Google Analytics?

Yes. We found Google Analytics at BNP Paribas through website code. Google Analytics is used by 89,943 companies we track.

How does runsonwhat know what BNP Paribas uses?

We read public traces only: BNP Paribas's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.

We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.