Do you need Mixpanel on a small website?
Decide whether product analytics is worth another script, or whether named clicks and a short funnel already answer this month's questions.
You published a site on Webflow, Lovable, or a static host. The next suggestion is often “add Mixpanel.”
Open the live page and write down the actions you can check this month. That list decides whether you need a product analytics tool.
I am not a lawyer, and this is not advice for your country. Read the rules that apply to your audience.
Start with the clicks you can name
Traffic is a different question. Which pages get visits belongs in the Google Analytics guide.
Mixpanel is the next paste when someone wants named clicks, a funnel, and a profile that lasts across days.
A small site usually needs the named clicks. Did anyone open /pricing, press Start with Pro, and join the waiting list? You can count those without a user profile.
If nobody signs in, you also do not have a durable identity to attach. Mixpanel keeps one person together across sessions. A brochure or a freelance site rarely has that loop.
Product analytics has a cost besides the account
Mixpanel, PostHog, and Amplitude store an identifier in the visitor’s browser. The Mixpanel script uses a first-party cookie for that id by default. The default lifetime is 365 days.
That is a cookie. Optional analytics cookies are a common reason a small site needs a consent prompt.
If you add Mixpanel, plan for the cookie banner. Reject has to stop the tag. Name the tool in the privacy policy. A copied template that lists Mixpanel is wrong if you never installed it. It is also wrong if you did install it and the page never says so.
The usual call looks like this:
mixpanel.init('9f2c1a8e4b7d3c6a1e5f0b8d2c4a7e91')
mixpanel.track('signup_click', { plan: 'pro' })Keep Mixpanel when people log in, come back next week, and you need retention or cohorts. You then call identify with your own user id. If you already bought it for an app, keep it on the app. The marketing site can count clicks another way.
Named events cover the usual questions
You can record a click without writing a cookie.
Sitebase’s events use the same cookieless tracker as pageviews. A visitor is a hash of IP, user agent, and a salt that changes every day. Nothing is stored in the browser. Yesterday’s hash cannot be joined to today’s.
You can still follow a path inside one day. A visitor can view /pricing, click the button, and join the list.
Feature embeds already write names such as waitlist_signup and contact_message. Your own buttons can write the rest.
Sitebase is in private beta. Public signup isn’t open.
The site snippet looks like this. Replace YOUR_SITE_KEY with the website key from your dashboard:
<script
async
crossorigin="anonymous"
src="https://sitebase.dev/embed.js"
data-sitebase-site="YOUR_SITE_KEY"
></script>Put it in the shared layout so every public page loads it. Then mark one button:
<a href="/waitlist" data-sitebase-event="signup_click">Start with Pro</a>Or call sitebase.track('signup_click', { plan: 'pro' }) from your own script. Names can be 60 characters. You can send up to 10 properties. Values are strings, numbers, or booleans.
Funnels turn those names into an ordered path. You pick 2 to 8 steps. Each step is a page path or an event name. A visitor counts for step 2 only after step 1. The steps can land anywhere in the selected range, not only in one visit. Ranges are 7 days, 30 days, and 6 months.
It does not build cohorts or a retention curve. Visitor ids rotate every day, so there is no profile that lasts across days. If you need those reports, keep Mixpanel.
Do not check this on localhost. The tracker ignores localhost and file: pages. Open the published URL.
Click it on the live URL
Open the published site in a fresh window, not the preview.
Press the pricing button yourself. Confirm signup_click appears on Events. If you built a funnel, walk the whole path and confirm the counts move.
Search the HTML and the network panel for mixpanel. If it is not there and nobody logs in, you do not need a Mixpanel project.
If a template added it and you do not use the identity features, remove it. If the banner existed only for that tag, you can remove the banner too.
How to track custom events covers the install. How to build a conversion funnel covers the report. Then walk the other checks in the launch checklist.