Hey Glancy documentation

Hey Glancy is growth analytics for your website and apps, so you know what grows your business. You send events from your product, and Hey Glancy turns them into dashboards, funnels, retention, user journeys, session replays and heatmaps. These docs cover getting your data in and what Hey Glancy does with it.

#How it works

1. Your product sends events. A small SDK in your website or app (or your server) sends what people do, like Signed Up or Order Completed, along with who did it.
2. Hey Glancy stores them in a bucket. A bucket holds the data of one project in one environment, for example Shop — production. Each bucket has its own write key, and the key decides which bucket an event lands in.
3. You explore them in Hey Glancy. Every report, dashboard, replay and alert reads from the bucket you have open.

The write key can only add events to its bucket, never read anything, so it is safe to put in a web page or a mobile app. You'll find it on the bucket's Setup page in Hey Glancy.

#Pick your SDK

You have	Use
A website, landing page or any HTML	Script tag (glancy.js): one line, no build step
A web app built with React, Vue, Svelte, Angular…	JavaScript (npm)
A Next.js app	Next.js: browser and server
A React Native or Expo app	React Native
An iOS, iPadOS, macOS, tvOS or watchOS app	Swift
An Android app, or a Kotlin / Java backend	Android and JVM
A WordPress or WooCommerce site	WordPress plugin
Data already flowing through Segment	Segment
Anything else	The HTTP API, from any language

All of them send the same kind of messages (they follow the Segment spec), so events from your website, your apps and your servers land on the same people and the same reports.

#Next steps

• New to Hey Glancy? The Quickstart gets your first events in, in about five minutes.
• Planning what to track? Read Events, users and sessions.
• Want to watch sessions or see where people click? See Session replay and heatmaps.
• Questions about personal data? See Privacy and your data.