Town Fair Tire's tech stack
What does Town Fair Tire use?
Town Fair Tire (townfairtire.com) uses at least 14 tools we can see from public records, including Microsoft 365 for email and documents, Google Tag Manager for analytics, Cloudflare for content delivery and SendGrid for email delivery. Last checked .
- Industry
- Retail
- Size
- 1,001–5,000 employees
- Based in
- East Haven, United States
- Founded
- 1967
- Company page
- Tools found
- 14
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Town Fair Tire'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
CDN & Edge
Application
4 tools, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
6 tools, what the team runs on day to day
Email Delivery
Dev Tools
Security & Compliance
Town Fair Tire tech stack FAQ
What tools does Town Fair Tire use?
We've found 14 tools at Town Fair Tire (townfairtire.com). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Tag Manager. Go-to-market: Meta Pixel. Company Ops: Microsoft 365, Google Workspace and SendGrid. Last checked October 3, 2026.
What email provider does Town Fair Tire use?
Town Fair Tire uses Microsoft 365, Google Workspace and Apple Business for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does Town Fair Tire use?
Town Fair Tire uses Google Tag Manager for analytics. We found Google Tag Manager through website code.
Does Town Fair Tire use Microsoft 365?
Yes. We found Microsoft 365 at Town Fair Tire through DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Town Fair Tire uses?
We read public traces only: Town Fair Tire'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.