Ferring Pharmaceuticals (Finland)'s tech stack
What does Ferring Pharmaceuticals (Finland) use?
Ferring Pharmaceuticals (Finland) (ferring.fi) uses at least 7 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, SendGrid for email delivery and OneTrust for security. Last checked .
- Based in
- Finland
- Founded
- 1950
- Company page
- Tools found
- 7
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Ferring Pharmaceuticals (Finland)'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
1 tool, what the product is built with
Frontend
Data & Observability
1 tool, 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
Ferring Pharmaceuticals (Finland) tech stack FAQ
What tools does Ferring Pharmaceuticals (Finland) use?
We've found 7 tools at Ferring Pharmaceuticals (Finland) (ferring.fi). Application: jQuery. Data & Observability: Google Analytics. Go-to-market: Google Ads. Company Ops: Microsoft 365, SendGrid and OneTrust. Last checked October 3, 2026.
What email provider does Ferring Pharmaceuticals (Finland) use?
Ferring Pharmaceuticals (Finland) uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does Ferring Pharmaceuticals (Finland) use?
Ferring Pharmaceuticals (Finland) uses Google Analytics for analytics. We found Google Analytics through website code.
Does Ferring Pharmaceuticals (Finland) use Microsoft 365?
Yes. We found Microsoft 365 at Ferring Pharmaceuticals (Finland) through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Ferring Pharmaceuticals (Finland) uses?
We read public traces only: Ferring Pharmaceuticals (Finland)'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.