Imperial Logistics's tech stack
What does Imperial Logistics use?
Imperial Logistics (imperial.co.za) uses at least 12 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Cloudflare for content delivery and Cookiebot for security. Last checked .
- Company page
- Tools found
- 12
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
Imperial Logistics'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
CDN & Edge
Application
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
3 tools, what they measure and store
Go-to-market
3 tools, how they find and keep customers
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
Imperial Logistics tech stack FAQ
What tools does Imperial Logistics use?
We've found 12 tools at Imperial Logistics (imperial.co.za). Edge & Hosting: Cloudflare and Amazon CloudFront. Application: jQuery and Vimeo. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and LinkedIn Insight Tag. Company Ops: Microsoft 365 and Cookiebot. Last checked October 2, 2026.
What email provider does Imperial Logistics use?
Imperial Logistics uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does Imperial Logistics use?
Imperial Logistics uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.
Does Imperial Logistics use Microsoft 365?
Yes. We found Microsoft 365 at Imperial Logistics through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Imperial Logistics uses?
We read public traces only: Imperial Logistics'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.