Karstadt Sports GmbH's tech stack
What does Karstadt Sports GmbH use?
Karstadt Sports GmbH (karstadtsports.de) uses at least 13 tools we can see from public records, including Google Analytics for analytics, Salesforce Commerce Cloud for its website, Cloudflare for content delivery and Cookiebot for security. Last checked .
- Industry
- Retail
- Size
- 10,000+ employees
- Based in
- Berlin, Germany
- Founded
- 1881
- Company page
- Tools found
- 13
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
Karstadt Sports GmbH'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
CDN & Edge
Application
1 tool, what the product is built with
Media & UI
Data & Observability
3 tools, what they measure and store
Go-to-market
7 tools, how they find and keep customers
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
Karstadt Sports GmbH tech stack FAQ
What tools does Karstadt Sports GmbH use?
We've found 13 tools at Karstadt Sports GmbH (karstadtsports.de). Edge & Hosting: Cloudflare. Application: YouTube. Data & Observability: Google Analytics, Google Tag Manager and Crazy Egg. Go-to-market: Meta Pixel, Google Ads and Microsoft Ads. Company Ops: Cookiebot. Last checked October 3, 2026.
What analytics tools does Karstadt Sports GmbH use?
Karstadt Sports GmbH uses Google Analytics, Google Tag Manager and Crazy Egg for analytics. We found Google Analytics through website code.
What CMS does Karstadt Sports GmbH use?
Karstadt Sports GmbH uses Salesforce Commerce Cloud for its website. We found Salesforce Commerce Cloud through website code.
Does Karstadt Sports GmbH use Cloudflare?
Yes. We found Cloudflare at Karstadt Sports GmbH through DNS records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Karstadt Sports GmbH uses?
We read public traces only: Karstadt Sports GmbH'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.