Primo Caredent Group's tech stack
What does Primo Caredent Group use?
Primo Caredent Group (primocaredentgroup.it) uses at least 12 tools we can see from public records, including Google Analytics for analytics, WordPress for its website, Mailgun for email delivery and reCAPTCHA for security. Last checked .
- Industry
- Healthcare
- Size
- 1,001–5,000 employees
- Based in
- Turin, Italy
- Founded
- 2012
- Company page
- Tools found
- 12
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Primo Caredent Group'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
2 tools, what they measure and store
Go-to-market
3 tools, how they find and keep customers
Company Ops
3 tools, what the team runs on day to day
Email Delivery
Security & Compliance
Primo Caredent Group tech stack FAQ
What tools does Primo Caredent Group use?
We've found 12 tools at Primo Caredent Group (primocaredentgroup.it). Edge & Hosting: Amazon Route 53. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads and WordPress. Company Ops: reCAPTCHA, Mailgun and Cookiebot. Last checked October 3, 2026.
What analytics tools does Primo Caredent Group use?
Primo Caredent Group uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Primo Caredent Group use?
Primo Caredent Group uses WordPress for its website. We found WordPress through website code.
Does Primo Caredent Group use Google Analytics?
Yes. We found Google Analytics at Primo Caredent Group through website code. Google Analytics is used by 89,943 companies we track.
How does runsonwhat know what Primo Caredent Group uses?
We read public traces only: Primo Caredent Group'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.