FLZ.de's tech stack
What does FLZ.de use?
FLZ.de (flz.de) uses at least 10 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Mailjet for email delivery and consentmanager for security. Last checked .
- Industry
- Newspapers
- Size
- 51–200 employees
- Based in
- Ansbach, Germany
- Founded
- 1946
- Company page
- Tools found
- 10
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
FLZ.de'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
3 tools, what the product is built with
Data & Observability
2 tools, what they measure and store
Analytics
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
FLZ.de tech stack FAQ
What tools does FLZ.de use?
As of October 2026, runsonwhat has found 10 tools at FLZ.de (flz.de) in public records. Application: jQuery, Vue.js and Angular. Data & Observability: Google Analytics and Matomo. Go-to-market: Meta Pixel. Company Ops: Microsoft 365, Mailjet and consentmanager. Last checked October 20, 2026.
What email provider does FLZ.de use?
FLZ.de uses Microsoft 365 for email and office software, according to runsonwhat (October 2026). runsonwhat found Microsoft 365 through a DNS verification record for Microsoft 365. Microsoft 365 is used by 710,129 companies runsonwhat tracks.
What analytics tools does FLZ.de use?
FLZ.de uses Google Analytics for analytics, alongside Matomo, according to runsonwhat (October 2026). runsonwhat found Google Analytics through Google Analytics code on flz.de. Google Analytics is used by 878,682 companies runsonwhat tracks.
Does FLZ.de use jQuery?
Yes. runsonwhat found jQuery at FLZ.de through jQuery code on flz.de. jQuery is a Frontend tool used by 914,870 companies runsonwhat tracks.
How does runsonwhat know what FLZ.de uses?
runsonwhat reads public records only. Of the 10 tools at FLZ.de, 6 were found through code on flz.de, 3 through DNS records and 1 through email records. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and flz.de about 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.