runsonwhat

Converse's tech stack

What does Converse use?

Converse (converse.com) uses at least 42 tools we can see from public records, including Microsoft 365 for email and documents, Salesforce for sales, Google Analytics for analytics and Klarna for payments. Last checked .

Industry
Shoe
Size
1,001–5,000 employees
Based in
Boston, United States
Founded
1910
LinkedIn
Company page
Tools found
42
Categories
16
Layers
5 of 5
Last checked
Oct 2026

Converse'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.

Converse tech stack FAQ

What tools does Converse use?

We've found 42 tools at Converse (converse.com). Edge & Hosting: Cloudflare and Akamai. Application: jQuery, React and Klarna. Data & Observability: Google Analytics, New Relic and Adobe Experience Platform Tags. Go-to-market: Meta Pixel, Microsoft Ads and TikTok Pixel. Company Ops: Microsoft 365, Atlassian and Proofpoint. Last checked October 2, 2026.

What CRM does Converse use?

Converse uses Salesforce for sales and CRM. We found Salesforce through website code.

What email provider does Converse use?

Converse uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records.

What payment provider does Converse use?

Converse uses Klarna for payments. We found Klarna through website code.

What analytics tools does Converse use?

Converse uses Google Analytics, Adobe Analytics and Adobe Experience Platform for analytics, among 4 tools in this category. We found Google Analytics through website code.

What CMS does Converse use?

Converse uses Salesforce Commerce Cloud and Amplience for its website. We found Salesforce Commerce Cloud through website code.

Does Converse use jQuery?

Yes. We found jQuery at Converse through website code. jQuery is used by 761,693 companies we track.

How does runsonwhat know what Converse uses?

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