Tagawa Sangyo Co., Ltd. (Japan)'s tech stack
What does Tagawa Sangyo Co., Ltd. (Japan) use?
Tagawa Sangyo Co., Ltd. (Japan) (shikkui.com) uses at least 7 tools we can see from public records, including Google Analytics for analytics, HubSpot CMS for its website and Cloudflare for content delivery. Last checked .
- Industry
- Building Materials
- Size
- 1–10 employees
- Based in
- Tagawa Shi, Japan
- Founded
- 1924
- Company page
- Tools found
- 7
- Categories
- 6
- Layers
- 4 of 5
- Last checked
- Oct 2026
Tagawa Sangyo Co., Ltd. (Japan)'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
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Ads & Pixels
Tagawa Sangyo Co., Ltd. (Japan) tech stack FAQ
What tools does Tagawa Sangyo Co., Ltd. (Japan) use?
We've found 7 tools at Tagawa Sangyo Co., Ltd. (Japan) (shikkui.com). Edge & Hosting: Cloudflare. Application: jQuery and Google Fonts. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads and HubSpot CMS. Last checked October 4, 2026.
What analytics tools does Tagawa Sangyo Co., Ltd. (Japan) use?
Tagawa Sangyo Co., Ltd. (Japan) uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Tagawa Sangyo Co., Ltd. (Japan) use?
Tagawa Sangyo Co., Ltd. (Japan) uses HubSpot CMS for its website. We found HubSpot CMS through custom domain and website code.
Does Tagawa Sangyo Co., Ltd. (Japan) use Cloudflare?
Yes. We found Cloudflare at Tagawa Sangyo Co., Ltd. (Japan) through website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Tagawa Sangyo Co., Ltd. (Japan) uses?
We read public traces only: Tagawa Sangyo Co., Ltd. (Japan)'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.