runsonwhat

Aoste.de's tech stack

What does Aoste.de use?

Aoste.de (campofrio.de) uses at least 16 tools we can see from public records, including Google Analytics for analytics, WordPress for its website and GlobalSign for security. Last checked .

Based in
Germany
Re-check liveVisit campofrio.de
Tools found
16
Categories
7
Layers
5 of 5
Last checked
Oct 2026

Aoste.de'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

3 tools, what the product is built with

Frontend

Media & UI

Data & Observability

3 tools, what they measure and store

Analytics

Go-to-market

6 tools, how they find and keep customers

Website & CMS

Ads & Pixels

Company Ops

3 tools, what the team runs on day to day

Security & Compliance

Companies like Aoste.de also use

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

Companies with a stack like Aoste.de's

Ranked by shared tools, with rare tools counting more.

Aoste.de tech stack FAQ

What tools does Aoste.de use?

We've found 16 tools at Aoste.de (campofrio.de). Edge & Hosting: Gandi. Application: jQuery, Google Maps and AddToAny. Data & Observability: Google Analytics, Google Tag Manager and etracker. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: GlobalSign, Cookiebot and Imperva. Last checked October 3, 2026.

What analytics tools does Aoste.de use?

Aoste.de uses Google Analytics, Google Tag Manager and etracker for analytics. We found Google Analytics through website code.

What CMS does Aoste.de use?

Aoste.de uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does Aoste.de use Google Analytics?

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

How does runsonwhat know what Aoste.de uses?

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