runsonwhat

PRACTIMAN's tech stack

What does PRACTIMAN use?

PRACTIMAN (practiman.com) uses at least 10 tools we can see from public records, including Google Analytics for analytics, WordPress for its website and Campaign Monitor for marketing. Last checked .

Industry
Consumer Goods
Size
51–200 employees
Based in
Alicante, Spain
LinkedIn
Company page
Re-check liveVisit practiman.com
Tools found
10
Categories
6
Layers
3 of 5
Last checked
Oct 2026

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

2 tools, what the product is built with

Frontend

Media & UI

Data & Observability

2 tools, what they measure and store

Analytics

Go-to-market

6 tools, how they find and keep customers

Website & CMS

Marketing

Ads & Pixels

Companies like PRACTIMAN also use

Tools common among companies with a similar stack that we haven't found at PRACTIMAN.

Companies with a stack like PRACTIMAN's

Ranked by shared tools, with rare tools counting more.

PRACTIMAN tech stack FAQ

What tools does PRACTIMAN use?

We've found 10 tools at PRACTIMAN (practiman.com). Application: jQuery and Font Awesome. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Google Ads and Yoast SEO. Last checked October 6, 2026.

What analytics tools does PRACTIMAN use?

PRACTIMAN uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What CMS does PRACTIMAN use?

PRACTIMAN uses WordPress and Yoast SEO for its website. We found WordPress through website code.

What marketing software does PRACTIMAN use?

PRACTIMAN uses Campaign Monitor and Metricool for marketing. We found Campaign Monitor through email records.

Does PRACTIMAN use jQuery?

Yes. We found jQuery at PRACTIMAN through website code. jQuery is used by 531,409 companies we track.

How does runsonwhat know what PRACTIMAN uses?

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