DAPSA's tech stack
What does DAPSA use?
DAPSA (dapsa.com) uses at least 15 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and emBlue for marketing. Last checked .
- Industry
- Oil & Gas
- Size
- 201–1,000 employees
- Based in
- Dock Sur, Argentina
- Founded
- 1973
- Company page
- Tools found
- 15
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
DAPSA'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
5 tools, what the product is built with
Data & Observability
3 tools, what they measure and store
Go-to-market
6 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Workspace
DAPSA tech stack FAQ
What tools does DAPSA use?
We've found 15 tools at DAPSA (dapsa.com). Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: WordPress, Google Ads and Meta Pixel. Company Ops: Microsoft 365. Last checked October 8, 2026.
What email provider does DAPSA use?
DAPSA uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records, email records and website code.
What analytics tools does DAPSA use?
DAPSA uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.
What CMS does DAPSA use?
DAPSA uses WordPress, Yoast SEO and Elementor for its website. We found WordPress through website code.
What marketing software does DAPSA use?
DAPSA uses emBlue for marketing. We found emBlue through email records.
Does DAPSA use jQuery?
Yes. We found jQuery at DAPSA through website code. jQuery is used by 761,132 companies we track.
How does runsonwhat know what DAPSA uses?
We read public traces only: DAPSA'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.