Guides.
Things I had to work out while adding analytics to my own plugins, written down so you do not have to. Most of it applies whatever tool you end up using.
Measuring a plugin.
- How to get analytics and observe a Figma plugin in productionWho uses a Figma plugin, which features they touch, how long the slow part takes and how often it fails: what the sandbox rules out, what to send, and how to read it on one dashboard.
- A Figma plugin template with analytics built inOne command writes a Figma plugin project for React, Vue, Svelte or vanilla TypeScript, with Vite or esbuild, tode wired in, and the files a coding agent needs to work in it.
- Publishing a Figma plugin without losing its analyticsThe five things that make a published plugin go quiet on the dashboard: a missing allowed domain, a key that was not in the build, the placeholder id, the currentuser permission, and what Figma rejects outright.
- What a Figma plugin sends to tode, and what comes backThe three events the tode SDK sends from a Figma plugin, the dashboard numbers they become, what never leaves the plugin, and how to read the Growing, Steady, Slipping and Changed lines.
- Best analytics for Figma plugins: eight options comparedThe Community page, Google Analytics, Mixpanel, PostHog, Amplitude, Plausible, your own endpoint and tode: what each needs to run inside a plugin and who should pick it.
- Google Analytics in a Figma plugin: why it breaks and what to do insteadThe plugin UI runs in a null-origin iframe with no cookies, so gtag.js fails. What the Measurement Protocol gives you, what it costs you, and the shape of a tool built for the sandbox.
- How to track usage of a Figma pluginWhich events are worth sending, where to call them in a plugin, how to name them so the numbers stay comparable, and what the manifest needs.
- Retention for Figma plugins: DAU, MAU, stickiness and week-one returnWhat each retention number means for a tool people open a few times a week, how tode computes them, and how to read a drop without panicking.
- Installs are not usage: what the Community page does not tell youThe Community page counts installs and likes. It cannot say how many people ran your plugin this week, which feature they used, or whether they came back.
- Why Figma and tode show different user counts for the same pluginFigma's user number is a lifetime list that only grows. tode counts Figma account ids seen in its own history. How each one is counted, and why the weekly numbers differ.
- What a Figma plugin can and cannot know about its usersThe Plugin API exposes a user id, a name, the editor and the mode, and nothing else. What that means for counting users, for privacy, and for the text in your Community listing.
- Analytics for Figma widgets: what you can count and where the code goesA widget runs only when someone clicks it and stops when the handler returns. What that means for users, sessions and events, with a working pattern for FigJam and Figma widgets.
tode compared with other tools.
Each page is about one tool: what it takes to run it inside a plugin, what you get, and when it is the better choice.
- Mixpanel in a Figma plugin, compared with todeMixpanel works inside a plugin once you turn persistence off and identify users yourself. When its reports are worth that setup, and when a smaller tool is the better fit.
- Google Analytics 4 in a Figma plugin, compared with todeGA4 is free and familiar, and most of it is built around pages and cookies that a plugin does not have. A side-by-side on what you get from each.
- PostHog in a Figma plugin, compared with todePostHog runs in the plugin iframe with memory persistence and brings funnels, flags and replay. What that buys a plugin developer, and what it asks in return.
- Amplitude in a Figma plugin, compared with todeAmplitude runs in the plugin iframe with identity storage off and autocapture disabled. What its funnels and cohorts are worth to a plugin, and when a fixed dashboard is enough.
- Plausible in a Figma plugin, compared with todePlausible can count plugin events through its Events API. It has no user id by design, so it cannot show returning users or retention. When that is fine and when it is not.