Aalborg University's tech stack
What does Aalborg University use?
Aalborg University (ucpbl.net) uses at least 9 tools we can see from public records, including Azure Monitor for analytics and Cookie Information for security. Last checked .
- Industry
- Research
- Size
- 11–50 employees
- Based in
- Aalborg East - Denmark, Denmark
- Founded
- 2014
- Company page
- Tools found
- 9
- Categories
- 6
- Layers
- 4 of 5
- Last checked
- Nov 2026
Aalborg University's stack, layer by layer
Of 9 tools, 9 came from website code. Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
3 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
Aalborg University tech stack FAQ
What tools does Aalborg University use?
As of November 2026, runsonwhat has found 9 tools at Aalborg University (ucpbl.net) in public records. Application: Vimeo, Adobe Fonts and Next.js. Data & Observability: Google Analytics, Google Tag Manager and Azure Monitor. Go-to-market: Google Ads. Company Ops: Cookie Information. Last checked November 5, 2026.
What analytics tools does Aalborg University use?
Aalborg University uses Google Analytics for analytics, alongside Google Tag Manager and Azure Monitor, according to runsonwhat (November 2026). runsonwhat found Google Analytics through Google Analytics code on ucpbl.net. Google Analytics is used by 903,930 companies runsonwhat tracks.
Does Aalborg University use Google Ads?
Yes. runsonwhat found Google Ads at Aalborg University through Google Ads code on ucpbl.net. Google Ads is a Ads & Pixels tool used by 540,547 companies runsonwhat tracks.
How does runsonwhat know what Aalborg University uses?
runsonwhat reads public records only. Of the 9 tools at Aalborg University, 9 were found through code on ucpbl.net. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and ucpbl.net about 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.