runsonwhat

Sigma Foods's tech stack

What does Sigma Foods use?

Sigma Foods (campofriofoodgroup.com) uses at least 8 tools we can see from public records, including Google Analytics for analytics and WordPress for its website. Last checked .

Industry
Food Processing
Size
5,001–10,000 employees
Based in
Alcobendas, Spain
Founded
2008
LinkedIn
Company page
Re-check liveVisit campofriofoodgroup.com
Tools found
8
Categories
6
Layers
4 of 5
Last checked
Oct 2026

Sigma Foods'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

DNS

Application

4 tools, what the product is built with

Frontend

AI

Media & UI

Data & Observability

1 tool, what they measure and store

Analytics

Go-to-market

2 tools, how they find and keep customers

Website & CMS

Companies like Sigma Foods also use

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

Companies with a stack like Sigma Foods's

Ranked by shared tools, with rare tools counting more.

Sigma Foods tech stack FAQ

What tools does Sigma Foods use?

We've found 8 tools at Sigma Foods (campofriofoodgroup.com). Edge & Hosting: Gandi. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics. Go-to-market: WordPress and Yoast SEO. Last checked October 2, 2026.

What analytics tools does Sigma Foods use?

Sigma Foods uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does Sigma Foods use?

Sigma Foods uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does Sigma Foods use Google Analytics?

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

How does runsonwhat know what Sigma Foods uses?

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