runsonwhat

dogado.de's tech stack

What does dogado.de use?

dogado.de (robhost.de) uses at least 17 tools we can see from public records, including Microsoft 365 for email and documents, Dealfront for sales, Zendesk for customer support and Google Analytics for analytics. Last checked .

Industry
Internet
Size
201–1,000 employees
Based in
Dortmund, Germany
Founded
2001
LinkedIn
Company page
Tools found
17
Categories
10
Layers
4 of 5
Last checked
Oct 2026

dogado.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.

Application

1 tool, what the product is built with

Media & UI

Data & Observability

2 tools, what they measure and store

Company Ops

5 tools, what the team runs on day to day

Email Delivery

Dev Tools

Security & Compliance

dogado.de tech stack FAQ

What tools does dogado.de use?

We've found 17 tools at dogado.de (robhost.de). Application: Lottie. Data & Observability: Google Analytics and Hotjar. Go-to-market: Google Ads, Meta Pixel and Microsoft Ads. Company Ops: Microsoft 365, Apple Business and Atlassian. Last checked October 6, 2026.

What CRM does dogado.de use?

dogado.de uses Dealfront for sales and CRM. We found Dealfront through website code.

What email provider does dogado.de use?

dogado.de uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records.

What does dogado.de use for customer support?

dogado.de uses Zendesk for customer support. We found Zendesk through custom domain and email records.

What analytics tools does dogado.de use?

dogado.de uses Google Analytics and Hotjar for analytics. We found Google Analytics through website code.

Does dogado.de use Google Analytics?

Yes. We found Google Analytics at dogado.de through website code. Google Analytics is used by 726,379 companies we track.

How does runsonwhat know what dogado.de uses?

We read public traces only: dogado.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.