runsonwhat

Sesc Pernambuco's tech stack

What does Sesc Pernambuco use?

Sesc Pernambuco (sescpe.org.br) uses at least 14 tools we can see from public records, including Google Analytics for analytics and WordPress for its website. Last checked .

Industry
Health, Wellness and Fitness
Size
1,001–5,000 employees
Based in
Recife, Brazil
Founded
1946
LinkedIn
Company page
Re-check liveVisit sescpe.org.br
Tools found
14
Categories
7
Layers
3 of 5
Last checked
Oct 2026

Sesc Pernambuco'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

7 tools, what the product is built with

Frontend

AI

Media & UI

Data & Observability

2 tools, what they measure and store

Analytics

Go-to-market

5 tools, how they find and keep customers

Website & CMS

Marketing

Ads & Pixels

Companies like Sesc Pernambuco also use

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

Companies with a stack like Sesc Pernambuco's

Ranked by shared tools, with rare tools counting more.

Sesc Pernambuco tech stack FAQ

What tools does Sesc Pernambuco use?

We've found 14 tools at Sesc Pernambuco (sescpe.org.br). Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and WordPress. Last checked October 3, 2026.

What analytics tools does Sesc Pernambuco use?

Sesc Pernambuco uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What CMS does Sesc Pernambuco use?

Sesc Pernambuco uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does Sesc Pernambuco use Google Analytics?

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

How does runsonwhat know what Sesc Pernambuco uses?

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