ヤクルト本社's tech stack
What does ヤクルト本社 use?
ヤクルト本社 (yakult.co.jp) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Shopify for its website and SendGrid for email delivery. Last checked .
- Industry
- Food Production
- Size
- 1,001–5,000 employees
- Based in
- Japan
- Founded
- 1955
- Company page
- Tools found
- 11
- Categories
- 7
- Layers
- 5 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
Application
1 tool, what the product is built with
Frontend
Data & Observability
3 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
ヤクルト本社 tech stack FAQ
What tools does ヤクルト本社 use?
We've found 11 tools at ヤクルト本社 (yakult.co.jp). Edge & Hosting: Amazon Route 53. Application: jQuery. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and Shopify. Company Ops: Microsoft 365 and SendGrid. Last checked October 3, 2026.
What email provider does ヤクルト本社 use?
ヤクルト本社 uses Microsoft 365 for email and documents. We found Microsoft 365 through 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.
What CMS does ヤクルト本社 use?
ヤクルト本社 uses Shopify for its website. We found Shopify through email records.
Does ヤクルト本社 use Microsoft 365?
Yes. We found Microsoft 365 at ヤクルト本社 through 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.