runsonwhat

Coca-Cola's tech stack

What does Coca-Cola use?

Coca-Cola (simplyorangejuice.com) uses at least 18 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Adobe Edge Delivery Services for its website and web-vitals for monitoring. Last checked .

Size
1–10 employees
Based in
Sugar Land, United States
Founded
2001
LinkedIn
Company page
Tools found
18
Categories
10
Layers
5 of 5
Last checked
Oct 2026

Coca-Cola'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

2 tools, where the bytes are served from

Application

1 tool, what the product is built with

Media & UI

Data & Observability

5 tools, what they measure and store

Company Ops

4 tools, what the team runs on day to day

Coca-Cola tech stack FAQ

What tools does Coca-Cola use?

We've found 18 tools at Coca-Cola (simplyorangejuice.com). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: YouTube. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and TikTok Pixel. Company Ops: Microsoft 365, Proofpoint and reCAPTCHA. Last checked October 3, 2026.

What email provider does Coca-Cola use?

Coca-Cola uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.

What analytics tools does Coca-Cola use?

Coca-Cola uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics, among 4 tools in this category. We found Google Analytics through website code.

What CMS does Coca-Cola use?

Coca-Cola uses Adobe Edge Delivery Services for its website. We found Adobe Edge Delivery Services through website code.

Does Coca-Cola use Microsoft 365?

Yes. We found Microsoft 365 at Coca-Cola through email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Coca-Cola uses?

We read public traces only: Coca-Cola'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.