Baltic Agro's tech stack
What does Baltic Agro use?
Baltic Agro (balticagro.lv) uses at least 9 tools we can see from public records, including Microsoft 365 for email and documents, Zendesk for customer support and Google Analytics for analytics. Last checked .
- Industry
- Manufacture of Pesticides and Other Agrochemical Products
- Size
- 51–200 employees
- Based in
- Latvia
- Founded
- 1994
- Tools found
- 9
- Categories
- 6
- Layers
- 4 of 5
- Last checked
- Oct 2026
Baltic Agro'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
1 tool, what the product is built with
Frontend
Data & Observability
3 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Marketing
Ads & Pixels
Support & Docs
Company Ops
1 tool, what the team runs on day to day
Workspace
Baltic Agro tech stack FAQ
What tools does Baltic Agro use?
We've found 9 tools at Baltic Agro (balticagro.lv). Application: jQuery. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Meta Pixel, Google Ads and Zendesk. Company Ops: Microsoft 365. Last checked October 3, 2026.
What email provider does Baltic Agro use?
Baltic Agro uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.
What does Baltic Agro use for customer support?
Baltic Agro uses Zendesk for customer support. We found Zendesk through email records.
What analytics tools does Baltic Agro use?
Baltic Agro uses Google Analytics, Google Tag Manager and Hotjar for analytics. We found Google Analytics through website code.
Does Baltic Agro use Microsoft 365?
Yes. We found Microsoft 365 at Baltic Agro through email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Baltic Agro uses?
We read public traces only: Baltic Agro'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.