Crazy Egg API
Crazy Egg's public API is a single Conversion Tracking endpoint: server-side POSTs of conversion events using a per-site key. There is no API to pull heatmaps, recordings, or session data out; the platform is a closed dashboard with Zapier, Slack, and webhook notifications for goals.
Frequently asked questions
Crazy Egg scores C on the API Report Card. Crazy Egg's public API is a single Conversion Tracking endpoint: server-side POSTs of conversion events using a per-site key. There is no API to pull heatmaps, recordings, or session data out; the platform is a closed dashboard with Zapier, Slack, and webhook notifications for goals.
Crazy Egg has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood.
Crazy Egg is a website behavior analytics and conversion rate optimization (CRO) platform founded in 2006 by Hiten Shah and Neil Patel.
Horizontal CRO/web analytics tooling. Vertical-agnostic but skews toward e-commerce, lead generation, agencies, education, and SMB-to-mid-market website owners. Marketers install a JavaScript snippet on their site, then use the dashboard to view heatmaps of clicks/scrolls, replay session recordings, run A/B tests on page variants, deploy survey widgets, and analyze conversion funnels.
Claims 449,000+ websites use the platform globally. Reported ~$4.5M–$6.3M revenue with roughly 4,000 paying customers (Latka). Well-known brand in the heatmap category but smaller than Hotjar and dwarfed by free Microsoft Clarity in volume.
Heatmap interaction data (click/scroll/move coordinates), session recordings (video/DOM events), A/B test variant performance, conversion funnel step data, survey responses, popup engagement metrics, and per-visitor metadata (referrer, device, geo).
Founded 2006 in La Mirada, California, one of the original heatmap tools. Product has been iteratively modernized (added session recordings, A/B testing, surveys, AI insights) but the brand and core UX feel mature/established rather than cutting-edge.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.