runsonwhat

Destination Toronto's tech stack

What does Destination Toronto use?

Destination Toronto (destinationtoronto.com) uses at least 48 tools we can see from public records, including Hotjar for analytics, Shopify for its website, ActiveCampaign for marketing and web-vitals for monitoring. Destination Toronto started using Shopify in Oct 2026. Last checked .

Industry
Leisure, Travel & Tourism
Size
51–200 employees
Based in
Toronto, Canada
Founded
1926
LinkedIn
Company page
Tools found
48
Categories
17
Layers
5 of 5
Changes seen
3

Destination Toronto's stack, layer by layer

Of 48 tools, 35 came from website code, 6 from DNS verification records, 3 from email records and 4 from other records. Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.

What changed at Destination Toronto

Recent starts and stops

  1. StartedShopify
  2. StartedFirebase
  3. StartedZapier

Destination Toronto tech stack FAQ

What tools does Destination Toronto use?

As of November 2026, runsonwhat has found 48 tools at Destination Toronto (destinationtoronto.com) in public records. Edge & Hosting: Cloudflare, GoDaddy and Akamai. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Google Ads, Meta Pixel and LinkedIn Insight Tag. Company Ops: Microsoft 365, Google Workspace and SendGrid. Last checked November 5, 2026.

What email provider does Destination Toronto use?

Destination Toronto uses Microsoft 365 for email and office software, alongside Google Workspace, according to runsonwhat (November 2026). runsonwhat found Microsoft 365 through a DNS verification record for Microsoft 365. Microsoft 365 is used by 730,434 companies runsonwhat tracks.

What analytics tools does Destination Toronto use?

Destination Toronto uses Google Analytics for analytics, alongside Google Tag Manager, Microsoft Clarity and Hotjar, according to runsonwhat (November 2026). runsonwhat found Google Analytics through Google Analytics code on destinationtoronto.com. Google Analytics is used by 903,756 companies runsonwhat tracks.

What is Destination Toronto's website built with?

Destination Toronto uses Shopify for its website, according to runsonwhat (November 2026). runsonwhat found Shopify through a subdomain that points at Shopify. Shopify is used by 61,324 companies runsonwhat tracks.

What marketing software does Destination Toronto use?

Destination Toronto uses ActiveCampaign for marketing, alongside Act-On, according to runsonwhat (November 2026). runsonwhat found ActiveCampaign through ActiveCampaign code on destinationtoronto.com. ActiveCampaign is used by 17,812 companies runsonwhat tracks.

What monitoring tools does Destination Toronto use?

Destination Toronto uses web-vitals for monitoring, alongside LogRocket, according to runsonwhat (November 2026). runsonwhat found web-vitals through web-vitals code on destinationtoronto.com. web-vitals is used by 30,164 companies runsonwhat tracks.

Does Destination Toronto use jQuery?

Yes. runsonwhat found jQuery at Destination Toronto through jQuery code on destinationtoronto.com. jQuery is a Frontend tool used by 927,165 companies runsonwhat tracks.

Has Destination Toronto changed tools recently?

Yes. On runsonwhat's rechecks, Destination Toronto started using Shopify, Firebase and Zapier (latest on October 29, 2026). A change counts only between two checks of destinationtoronto.com done the same way.

Which companies have a tech stack similar to Destination Toronto's?

The companies with the stacks most like Destination Toronto's are See Monterey, SouthStar Capital, Horizion and Shores & Islands Ohio, according to runsonwhat (November 2026). Each shares 12 to 24 tools with Destination Toronto, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what Destination Toronto uses?

runsonwhat reads public records only. Of the 48 tools at Destination Toronto, 35 were found through code on destinationtoronto.com, 7 through DNS records, 3 through email records and 3 through subdomains that point at the vendor. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and destinationtoronto.com about 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.