runsonwhat

SWE Energie's tech stack

What does SWE Energie use?

SWE Energie (swe-energie.de) uses at least 9 tools we can see from public records, including Google Analytics for analytics, LinkedIn for marketing and Usercentrics for security. Last checked .

Industry
Public Utility
Based in
Germany
Re-check liveVisit swe-energie.de
Tools found
9
Categories
5
Layers
4 of 5
Last checked
Oct 2026

SWE Energie'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

1 tool, what the product is built with

Frontend

Data & Observability

3 tools, what they measure and store

Analytics

Go-to-market

4 tools, how they find and keep customers

Marketing

Ads & Pixels

Company Ops

1 tool, what the team runs on day to day

Security & Compliance

Companies like SWE Energie also use

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

Companies with a stack like SWE Energie's

Ranked by shared tools, with rare tools counting more.

More Public Utility companies

Other Public Utility companies we've checked.

SWE Energie tech stack FAQ

What tools does SWE Energie use?

We've found 9 tools at SWE Energie (swe-energie.de). Application: jQuery. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Meta Pixel, Google Ads and LinkedIn. Company Ops: Usercentrics. Last checked October 4, 2026.

What analytics tools does SWE Energie use?

SWE Energie uses Google Analytics, Google Tag Manager and Hotjar for analytics. We found Google Analytics through website code.

What marketing software does SWE Energie use?

SWE Energie uses LinkedIn for marketing. We found LinkedIn through DNS verification records.

Does SWE Energie use Google Analytics?

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

How does runsonwhat know what SWE Energie uses?

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