runsonwhat

Crédit Agricole du Maroc's tech stack

What does Crédit Agricole du Maroc use?

Crédit Agricole du Maroc (creditagricole.ma) uses at least 8 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Microsoft Entra ID for sign-in and SendGrid for email delivery. Last checked .

Industry
Banking
Size
1,001–5,000 employees
Based in
Mie Du Maroc, Morocco
Founded
1961
LinkedIn
Company page
Tools found
8
Categories
6
Layers
4 of 5
Last checked
Oct 2026

Crédit Agricole du Maroc'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

Data & Observability

3 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Email Delivery

Crédit Agricole du Maroc tech stack FAQ

What tools does Crédit Agricole du Maroc use?

We've found 8 tools at Crédit Agricole du Maroc (creditagricole.ma). Application: Microsoft Entra ID. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Google Ads. Company Ops: Microsoft 365 and SendGrid. Last checked October 3, 2026.

What email provider does Crédit Agricole du Maroc use?

Crédit Agricole du Maroc uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does Crédit Agricole du Maroc use?

Crédit Agricole du Maroc uses Google Analytics, Google Tag Manager and Hotjar for analytics. We found Google Analytics through website code.

Does Crédit Agricole du Maroc use Microsoft 365?

Yes. We found Microsoft 365 at Crédit Agricole du Maroc through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Crédit Agricole du Maroc uses?

We read public traces only: Crédit Agricole du Maroc'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.