(株)日本政策金融公庫's tech stack
What does (株)日本政策金融公庫 use?
(株)日本政策金融公庫 (jfc.go.jp) uses at least 12 tools we can see from public records, including Salesforce for sales, Google Analytics for analytics, Pardot for marketing and Akamai for content delivery. Last checked .
- Industry
- Banking
- Size
- 5,001–10,000 employees
- Based in
- Otemachi, Japan
- Company page
- Tools found
- 12
- Categories
- 7
- 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.
Edge & Hosting
1 tool, where the bytes are served from
CDN & Edge
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
6 tools, how they find and keep customers
Ads & Pixels
Sales & CRM
(株)日本政策金融公庫 tech stack FAQ
What tools does (株)日本政策金融公庫 use?
We've found 12 tools at (株)日本政策金融公庫 (jfc.go.jp). Edge & Hosting: Akamai. Application: jQuery, Vimeo and YouTube. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and Salesforce. Last checked October 3, 2026.
What CRM does (株)日本政策金融公庫 use?
(株)日本政策金融公庫 uses Salesforce for sales and CRM. We found Salesforce through email records.
What analytics tools does (株)日本政策金融公庫 use?
(株)日本政策金融公庫 uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What marketing software does (株)日本政策金融公庫 use?
(株)日本政策金融公庫 uses Pardot and Salesforce Marketing Cloud for marketing. We found Pardot through DNS verification records and email records.
Does (株)日本政策金融公庫 use Google Analytics?
Yes. We found Google Analytics at (株)日本政策金融公庫 through website code. Google Analytics is used by 89,943 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.