runsonwhat

多慶屋 公式サイト's tech stack

What does 多慶屋 公式サイト use?

多慶屋 公式サイト (takeya.co.jp) uses at least 13 tools we can see from public records, including Google Workspace for email and documents, Google Analytics for analytics, WordPress for its website and New Relic for monitoring. Last checked .

Industry
Retail
Size
1–10 employees
Based in
Daihigashi, Japan
Founded
1951
LinkedIn
Company page
Tools found
13
Categories
8
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

4 tools, what they measure and store

Go-to-market

6 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

多慶屋 公式サイト tech stack FAQ

What tools does 多慶屋 公式サイト use?

We've found 13 tools at 多慶屋 公式サイト (takeya.co.jp). Application: jQuery. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Google Workspace and reCAPTCHA. Last checked October 3, 2026.

What email provider does 多慶屋 公式サイト use?

多慶屋 公式サイト uses Google Workspace for email and documents. We found Google Workspace 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 WordPress for its website. We found WordPress through website code.

Does 多慶屋 公式サイト use Google Workspace?

Yes. We found Google Workspace at 多慶屋 公式サイト through email records. Google Workspace is used by 126,364 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.