runsonwhat

Hektaur kauplus's tech stack

What does Hektaur kauplus use?

Hektaur kauplus (hektaur.eu) uses at least 15 tools we can see from public records, including Google Analytics for analytics, WordPress for its website, Trustindex for marketing and CookieYes for security. Last checked .

“Kodumasinate kauplus ja ladu Tallinnas, Nõmmel. Laos olevad tooted saab kohapealt kätte samal päeval, tarne üle Eesti 1–2 päevaga.”

Industry
Retail
Size
1–10 employees
Based in
Tallinn, Estonia
Founded
1997
LinkedIn
Company page
Tools found
15
Categories
8
Layers
4 of 5
Last checked
Oct 2026

Hektaur kauplus'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

Data & Observability

3 tools, what they measure and store

Company Ops

1 tool, what the team runs on day to day

Security & Compliance

Hektaur kauplus tech stack FAQ

What tools does Hektaur kauplus use?

We've found 15 tools at Hektaur kauplus (hektaur.eu). Application: jQuery and Font Awesome. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: CookieYes. Last checked October 4, 2026.

What analytics tools does Hektaur kauplus use?

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

What CMS does Hektaur kauplus use?

Hektaur kauplus uses WordPress, Yoast SEO and WooCommerce for its website. We found WordPress through website code.

What marketing software does Hektaur kauplus use?

Hektaur kauplus uses Trustindex for marketing. We found Trustindex through website code.

Does Hektaur kauplus use Google Analytics?

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

How does runsonwhat know what Hektaur kauplus uses?

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