runsonwhat

a&m impact's tech stack

What does a&m impact use?

a&m impact (ihub.nl) uses at least 8 tools we can see from public records, including Microsoft 365 for email and documents, TOPdesk for customer support, Google Analytics for analytics and SendGrid for email delivery. Last checked .

Industry
Healthcare
Size
1,001–5,000 employees
Based in
Rotterdam, Netherlands
LinkedIn
Company page
Tools found
8
Categories
7
Layers
3 of 5
Last checked
Oct 2026

a&m impact'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.

Data & Observability

2 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Ads & Pixels

Support & Docs

Company Ops

4 tools, what the team runs on day to day

Email Delivery

Finance & Legal

Security & Compliance

a&m impact tech stack FAQ

What tools does a&m impact use?

We've found 8 tools at a&m impact (ihub.nl). Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads and TOPdesk. Company Ops: Microsoft 365, SendGrid and Cookiebot. Last checked October 3, 2026.

What email provider does a&m impact use?

a&m impact uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What does a&m impact use for customer support?

a&m impact uses TOPdesk for customer support. We found TOPdesk through email records.

What analytics tools does a&m impact use?

a&m impact uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

Does a&m impact use Microsoft 365?

Yes. We found Microsoft 365 at a&m impact through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what a&m impact uses?

We read public traces only: a&m impact'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.