Livraria Escolar Editora (Portugal)'s tech stack
What does Livraria Escolar Editora (Portugal) use?
Livraria Escolar Editora (Portugal) (escolareditora.com) uses at least 8 tools we can see from public records, including Google Analytics for analytics, Brevo for marketing and reCAPTCHA for security. Last checked .
- Based in
- Portugal
- Tools found
- 8
- Categories
- 6
- Layers
- 4 of 5
- Last checked
- Oct 2026
Livraria Escolar Editora (Portugal)'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
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
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
Livraria Escolar Editora (Portugal) tech stack FAQ
What tools does Livraria Escolar Editora (Portugal) use?
We've found 8 tools at Livraria Escolar Editora (Portugal) (escolareditora.com). Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads and Brevo. Company Ops: reCAPTCHA. Last checked October 4, 2026.
What analytics tools does Livraria Escolar Editora (Portugal) use?
Livraria Escolar Editora (Portugal) uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What marketing software does Livraria Escolar Editora (Portugal) use?
Livraria Escolar Editora (Portugal) uses Brevo for marketing. We found Brevo through DNS verification records.
Does Livraria Escolar Editora (Portugal) use Google Analytics?
Yes. We found Google Analytics at Livraria Escolar Editora (Portugal) through website code. Google Analytics is used by 89,943 companies we track.
How does runsonwhat know what Livraria Escolar Editora (Portugal) uses?
We read public traces only: Livraria Escolar Editora (Portugal)'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.