runsonwhat

Concord Theatricals's tech stack

What does Concord Theatricals use?

Concord Theatricals (tams-witmark.com) uses at least 11 tools we can see from public records, including Google Analytics for analytics, Cloudflare for content delivery and OneTrust for security. Last checked .

Founded
1925
Re-check liveVisit tams-witmark.com
Tools found
11
Categories
6
Layers
5 of 5
Last checked
Oct 2026

Concord Theatricals'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

3 tools, what the product is built with

Search

Media & UI

Data & Observability

3 tools, what they measure and store

Analytics

Go-to-market

3 tools, how they find and keep customers

Ads & Pixels

Company Ops

1 tool, what the team runs on day to day

Security & Compliance

Companies like Concord Theatricals also use

Tools common among companies with a similar stack that we haven't found at Concord Theatricals.

Companies with a stack like Concord Theatricals's

Ranked by shared tools, with rare tools counting more.

Concord Theatricals tech stack FAQ

What tools does Concord Theatricals use?

We've found 11 tools at Concord Theatricals (tams-witmark.com). Edge & Hosting: Cloudflare. Application: Adobe Fonts, Lottie and Algolia. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Meta Pixel, Google Ads and Pinterest. Company Ops: OneTrust. Last checked October 3, 2026.

What analytics tools does Concord Theatricals use?

Concord Theatricals uses Google Analytics, Google Tag Manager and Hotjar for analytics. We found Google Analytics through website code.

Does Concord Theatricals use Cloudflare?

Yes. We found Cloudflare at Concord Theatricals through website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Concord Theatricals uses?

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