runsonwhat

LEGO.tr's tech stack

What does LEGO.tr use?

LEGO.tr (lego.tr) uses at least 10 tools we can see from public records, including Google Analytics for analytics and Cloudflare for content delivery. Last checked .

“LEGO oyuncak yapım parçasının ürünlere, oyunlara, videolara, LEGO® Mağazasına, LEGO tarihine, hayran tasarımlarına ve yardım merkezimize bağlantılar”

Based in
Türkiye
Tools found
10
Categories
7
Layers
4 of 5
Last checked
Nov 2026

LEGO.tr's stack, layer by layer

Of 10 tools, 7 came from website code, 1 from DNS verification records, 1 from DNS records and 1 from other records. 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

1 tool, where the bytes are served from

CDN & Edge

Application

3 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

4 tools, how they find and keep customers

LEGO.tr tech stack FAQ

What tools does LEGO.tr use?

As of November 2026, runsonwhat has found 10 tools at LEGO.tr (lego.tr) in public records. Edge & Hosting: Cloudflare. Application: Google Fonts and Vue.js. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads, Meta Pixel and Criteo. Last checked November 15, 2026.

What analytics tools does LEGO.tr use?

LEGO.tr uses Google Analytics for analytics, alongside Google Tag Manager, according to runsonwhat (November 2026). runsonwhat found Google Analytics through Google Analytics code on lego.tr. Google Analytics is used by 902,650 companies runsonwhat tracks.

Does LEGO.tr use Google Fonts?

Yes. runsonwhat found Google Fonts at LEGO.tr through Google Fonts code on lego.tr. Google Fonts is a Media & UI tool used by 825,765 companies runsonwhat tracks.

How does runsonwhat know what LEGO.tr uses?

runsonwhat reads public records only. Of the 10 tools at LEGO.tr, 7 were found through code on lego.tr, 2 through DNS records and 1 through website configuration files. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and lego.tr 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.