JTB総合研究所's tech stack
What does JTB総合研究所 use?
JTB総合研究所 (tourism.jp) uses at least 11 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Fastly for content delivery. Last checked .
- Industry
- Marketing and Advertising
- Size
- 1–10 employees
- Based in
- Japan
- Company page
- Tools found
- 11
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
JTB総合研究所'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
2 tools, where the bytes are served from
Hosting & Cloud
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
Marketing
Ads & Pixels
Company Ops
3 tools, what the team runs on day to day
Email Delivery
JTB総合研究所 tech stack FAQ
What tools does JTB総合研究所 use?
We've found 11 tools at JTB総合研究所 (tourism.jp). Edge & Hosting: Google Cloud and Fastly. Application: GSAP and Next.js. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads. Company Ops: Microsoft 365, Google Workspace and SendGrid. Last checked October 4, 2026.
What cloud does JTB総合研究所 run on?
JTB総合研究所 uses Google Cloud for hosting. We found Google Cloud through website code.
What email provider does JTB総合研究所 use?
JTB総合研究所 uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does JTB総合研究所 use?
JTB総合研究所 uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does JTB総合研究所 use Microsoft 365?
Yes. We found Microsoft 365 at JTB総合研究所 through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what JTB総合研究所 uses?
We read public traces only: JTB総合研究所'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.