runsonwhat

マガジンワールド's tech stack

What does マガジンワールド use?

マガジンワールド (magazineworld.jp) uses at least 16 tools we can see from public records, including Google Analytics for analytics, WordPress for its website, Marketo for marketing and Amazon CloudFront for content delivery. Last checked .

Industry
Publishing
Size
1–10 employees
Based in
Tokyo, Japan
Founded
1945
LinkedIn
Company page
Tools found
16
Categories
9
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

2 tools, where the bytes are served from

Application

2 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Company Ops

1 tool, what the team runs on day to day

Security & Compliance

マガジンワールド tech stack FAQ

What tools does マガジンワールド use?

We've found 16 tools at マガジンワールド (magazineworld.jp). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: jQuery and Google Fonts. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: reCAPTCHA. Last checked October 3, 2026.

What analytics tools does マガジンワールド use?

マガジンワールド uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What CMS does マガジンワールド use?

マガジンワールド uses WordPress for its website. We found WordPress through website code.

What marketing software does マガジンワールド use?

マガジンワールド uses Marketo for marketing. We found Marketo through email records and website code.

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.