Big O Tires's tech stack
What does Big O Tires use?
Big O Tires (bigotires.com) uses at least 23 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Bazaarvoice for marketing and web-vitals for monitoring. Last checked .
- Founded
- 1962
- Tools found
- 23
- Categories
- 11
- Layers
- 5 of 5
- Last checked
- Oct 2026
Big O Tires'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
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
3 tools, what they measure and store
Monitoring
Go-to-market
9 tools, how they find and keep customers
Company Ops
8 tools, what the team runs on day to day
Email Delivery
Workspace
Collaboration
Security & Compliance
Big O Tires tech stack FAQ
What tools does Big O Tires use?
We've found 23 tools at Big O Tires (bigotires.com). Edge & Hosting: Akamai. Application: Google Maps and React. Data & Observability: Google Analytics, Google Tag Manager and web-vitals. Go-to-market: Meta Pixel, Google Ads and Microsoft Ads. Company Ops: Microsoft 365, SendGrid and Proofpoint. Last checked October 3, 2026.
What email provider does Big O Tires use?
Big O Tires uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does Big O Tires use?
Big O Tires uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What marketing software does Big O Tires use?
Big O Tires uses Bazaarvoice and BrightEdge for marketing. We found Bazaarvoice through website code.
Does Big O Tires use Microsoft 365?
Yes. We found Microsoft 365 at Big O Tires through DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Big O Tires uses?
We read public traces only: Big O Tires'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.