runsonwhat

Essentra's tech stack

What does Essentra use?

Essentra (essentraplc.com) uses at least 13 tools we can see from public records, including Netlify for hosting, Google Analytics for analytics, Storyblok for its website and Akamai mPulse for monitoring. Last checked .

Industry
Consumer Goods
Size
5,001–10,000 employees
Based in
Kidlington, United Kingdom
LinkedIn
Company page
Tools found
13
Categories
10
Layers
5 of 5
Last checked
Oct 2026

Essentra'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

3 tools, where the bytes are served from

Hosting & Cloud

CDN & Edge

Application

2 tools, what the product is built with

Data & Observability

4 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Website & CMS

Ads & Pixels

Company Ops

2 tools, what the team runs on day to day

Security & Compliance

Essentra tech stack FAQ

What tools does Essentra use?

We've found 13 tools at Essentra (essentraplc.com). Edge & Hosting: Akamai, Netlify and CSC. Application: YouTube and Next.js. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Google Ads and Storyblok. Company Ops: Proofpoint and OneTrust. Last checked October 3, 2026.

What cloud does Essentra run on?

Essentra uses Netlify for hosting. We found Netlify through website code.

What analytics tools does Essentra use?

Essentra uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.

What CMS does Essentra use?

Essentra uses Storyblok for its website. We found Storyblok through website code.

Does Essentra use Google Analytics?

Yes. We found Google Analytics at Essentra through website code. Google Analytics is used by 89,943 companies we track.

How does runsonwhat know what Essentra uses?

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