runsonwhat

Pentia DXP's tech stack

What does Pentia DXP use?

Pentia DXP (sjaellandsuniversitetshospital.dk) uses at least 11 tools we can see from public records, including Google Tag Manager for analytics and Cookiebot for security. Last checked .

Industry
Healthcare
Size
1,001–5,000 employees
Based in
Køge, Denmark
LinkedIn
Company page
Re-check liveVisit sjaellandsuniversitetshospital.dk
Tools found
11
Categories
7
Layers
4 of 5
Last checked
Oct 2026

Pentia DXP'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

6 tools, what the product is built with

Frontend

Search

Media & UI

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

1 tool, what the team runs on day to day

Security & Compliance

Companies like Pentia DXP also use

Tools common among companies with a similar stack that we haven't found at Pentia DXP.

Companies with a stack like Pentia DXP's

Ranked by shared tools, with rare tools counting more.

More Healthcare companies

Other Healthcare companies we've checked.

Pentia DXP tech stack FAQ

What tools does Pentia DXP use?

We've found 11 tools at Pentia DXP (sjaellandsuniversitetshospital.dk). Application: Google Fonts, Next.js and Google Maps. Data & Observability: Google Tag Manager and Siteimprove. Go-to-market: Meta Pixel. Company Ops: Cookiebot. Last checked October 3, 2026.

What analytics tools does Pentia DXP use?

Pentia DXP uses Google Tag Manager and Siteimprove for analytics. We found Google Tag Manager through website code.

Does Pentia DXP use Meta Pixel?

Yes. We found Meta Pixel at Pentia DXP through website code. Meta Pixel is used by 63,585 companies we track.

How does runsonwhat know what Pentia DXP uses?

We read public traces only: Pentia DXP'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.