runsonwhat

Unicaja's tech stack

What does Unicaja use?

Unicaja (unicajabanco.es) uses at least 17 tools we can see from public records, including Google Cloud for hosting, Google Analytics for analytics, Adobe Edge Delivery Services for its website and Akamai for content delivery. Last checked .

Industry
Economics of Banking
Size
5,001–10,000 employees
Based in
Spain
Founded
2011
LinkedIn
Company page
Tools found
17
Categories
10
Layers
5 of 5
Last checked
Oct 2026

Unicaja'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

2 tools, where the bytes are served from

Hosting & Cloud

CDN & Edge

Application

1 tool, what the product is built with

Data & Observability

4 tools, what they measure and store

Go-to-market

6 tools, how they find and keep customers

Company Ops

4 tools, what the team runs on day to day

Unicaja tech stack FAQ

What tools does Unicaja use?

We've found 17 tools at Unicaja (unicajabanco.es). Edge & Hosting: Google Cloud and Akamai. Application: jQuery. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and TikTok Pixel. Company Ops: SendGrid, GlobalSign and Proofpoint. Last checked October 3, 2026.

What cloud does Unicaja run on?

Unicaja uses Google Cloud for hosting. We found Google Cloud through custom domain.

What analytics tools does Unicaja use?

Unicaja uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.

What CMS does Unicaja use?

Unicaja uses Adobe Edge Delivery Services for its website. We found Adobe Edge Delivery Services through website code.

Does Unicaja use Google Analytics?

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

How does runsonwhat know what Unicaja uses?

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