Türkiye Emlak Katılım Bankası's tech stack
What does Türkiye Emlak Katılım Bankası use?
Türkiye Emlak Katılım Bankası (emlakkatilim.com.tr) uses at least 8 tools we can see from public records, including Apple Business for email and documents, Google Analytics for analytics and GlobalSign for security. Last checked .
- Industry
- Banking
- Size
- 1,001–5,000 employees
- Based in
- Yenisahra, Turkey
- Founded
- 1926
- Company page
- Tools found
- 8
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Türkiye Emlak Katılım Bankası'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
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
Türkiye Emlak Katılım Bankası tech stack FAQ
What tools does Türkiye Emlak Katılım Bankası use?
We've found 8 tools at Türkiye Emlak Katılım Bankası (emlakkatilim.com.tr). Application: Vimeo, YouTube and Next.js. Data & Observability: Google Analytics. Go-to-market: Meta Pixel. Company Ops: Apple Business and GlobalSign. Last checked October 3, 2026.
What email provider does Türkiye Emlak Katılım Bankası use?
Türkiye Emlak Katılım Bankası uses Apple Business for email and documents. We found Apple Business through DNS verification records.
What analytics tools does Türkiye Emlak Katılım Bankası use?
Türkiye Emlak Katılım Bankası uses Google Analytics for analytics. We found Google Analytics through website code.
Does Türkiye Emlak Katılım Bankası use Google Analytics?
Yes. We found Google Analytics at Türkiye Emlak Katılım Bankası through website code. Google Analytics is used by 89,943 companies we track.
How does runsonwhat know what Türkiye Emlak Katılım Bankası uses?
We read public traces only: Türkiye Emlak Katılım Bankası'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.