runsonwhat

プルデンシャル生命保険's tech stack

What does プルデンシャル生命保険 use?

プルデンシャル生命保険 (prudential.co.jp) uses at least 18 tools we can see from public records, including Microsoft 365 for email and documents, Salesforce for sales, Google Analytics for analytics and GlobalSign for security. Last checked .

Industry
Insurance
Size
5,001–10,000 employees
Based in
Tokyo, Japan
Founded
1987
LinkedIn
Company page
Tools found
18
Categories
9
Layers
4 of 5
Last checked
Oct 2026

プルデンシャル生命保険'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

Data & Observability

3 tools, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Company Ops

10 tools, what the team runs on day to day

プルデンシャル生命保険 tech stack FAQ

What tools does プルデンシャル生命保険 use?

We've found 18 tools at プルデンシャル生命保険 (prudential.co.jp). Application: jQuery. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and Salesforce. Company Ops: Microsoft 365, Atlassian and GlobalSign. Last checked October 3, 2026.

What CRM does プルデンシャル生命保険 use?

プルデンシャル生命保険 uses Salesforce for sales and CRM. We found Salesforce through email records.

What email provider does プルデンシャル生命保険 use?

プルデンシャル生命保険 uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does プルデンシャル生命保険 use?

プルデンシャル生命保険 uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.

Does プルデンシャル生命保険 use Microsoft 365?

Yes. We found Microsoft 365 at プルデンシャル生命保険 through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what プルデンシャル生命保険 uses?

We read public traces only: プルデンシャル生命保険'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.