Magicbox's tech stack
What does Magicbox use?
Magicbox (magicboxint.com) uses at least 13 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .
- Industry
- Consumer Goods
- Size
- 51–200 employees
- Based in
- Barcelona, Spain
- Founded
- 1996
- Company page
- Tools found
- 13
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Magicbox'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
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
3 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Magicbox tech stack FAQ
What tools does Magicbox use?
We've found 13 tools at Magicbox (magicboxint.com). Edge & Hosting: GoDaddy. Application: jQuery, Vimeo and GSAP. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: WordPress, Google Ads and Yoast SEO. Company Ops: Microsoft 365 and Google Workspace. Last checked October 7, 2026.
What email provider does Magicbox use?
Magicbox uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does Magicbox use?
Magicbox uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.
What CMS does Magicbox use?
Magicbox uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does Magicbox use Microsoft 365?
Yes. We found Microsoft 365 at Magicbox through DNS verification records. Microsoft 365 is used by 685,713 companies we track.
How does runsonwhat know what Magicbox uses?
We read public traces only: Magicbox'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.