Batons Archives's tech stack
What does Batons Archives use?
Batons Archives (batons.com) uses at least 9 tools we can see from public records, including Google Analytics for analytics, WordPress for its website and Listrak for marketing. Last checked .
- Founded
- 1958
- Tools found
- 9
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Batons Archives'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.
Edge & Hosting
1 tool, where the bytes are served from
DNS
Application
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Companies like Batons Archives also use
Tools common among companies with a similar stack that we haven't found at Batons Archives.
Companies with a stack like Batons Archives's
Ranked by shared tools, with rare tools counting more.
Batons Archives tech stack FAQ
What tools does Batons Archives use?
We've found 9 tools at Batons Archives (batons.com). Edge & Hosting: CSC. Application: jQuery and Adobe Fonts. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Google Ads and Yoast SEO. Last checked October 3, 2026.
What analytics tools does Batons Archives use?
Batons Archives uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Batons Archives use?
Batons Archives uses WordPress and Yoast SEO for its website. We found WordPress through website code.
What marketing software does Batons Archives use?
Batons Archives uses Listrak for marketing. We found Listrak through website code.
Does Batons Archives use jQuery?
Yes. We found jQuery at Batons Archives through website code. jQuery is used by 591,427 companies we track.
How does runsonwhat know what Batons Archives uses?
We read public traces only: Batons Archives'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.