In this article
Framer comes with its own analytics. So the real question is rarely how to add analytics to a Framer site. It's whether you need a second tool, and if you do, how to install it so it counts every page of a visit and not only the first one.
This guide covers both, plus a test that catches the most common mistake. The steps work for any analytics tool that installs with a script tag.
What Framer already counts
Framer's built-in analytics doesn't use cookies, and Framer says that means it needs no cookie banner. According to Framer's help page on it, it reports:
- Live visitors over the last five minutes, unique visitors, pageviews, bounce rate and an estimated average session duration.
- The top 20 sources, UTM tags, pages, entry pages, exit pages, countries, devices, browsers and operating systems, plus 404 pages if you have a custom 404 page.
How far back you can look depends on your plan. As of November 2026, Framer's pricing page lists 30 days of history on Basic, 90 days on Pro and unlimited history on Enterprise, with no figure given for the free plan. Framer can also count clicks on links and submissions of forms that you give a tracking ID, and it sells funnels and A/B tests in an add-on called Convert, billed by the number of events. Check the pricing page for which of these your plan includes.
When a second tool is worth adding
A separate tool earns its place when it answers a question Framer's doesn't. The usual ones:
A longer history
If your plan keeps 30 or 90 days and you want to compare this spring with last spring, a separate tool keeps its own record, for as long as that tool keeps data.
More than the top 20
A blog with hundreds of posts, or a site with many small referrers, has a long tail that a top-20 list cuts off.
Sites on more than one platform
One dashboard for the Framer site and the rest is easier than several. A separate tool's history also doesn't depend on where the site is hosted, if you ever move it.
A team that lives in Google Analytics
Framer has a field for a GA4 Measurement ID in its site settings, so this one needs no custom code. GA4's tags set first-party cookies such as _ga, though, which brings back the question of a cookie banner.
Visits from AI assistants
Visits from ChatGPT, Claude, Perplexity and similar assistants can carry the assistant's site as the referrer, or a tag such as utm_source=chatgpt.com, so in Framer they can end up split between the sources list and the UTM list. The guide to tracking ChatGPT traffic explains how to find them, whichever tool you use.
Revenue next to visitors
If you sell something, revenue on the same timeline as traffic can show a broken checkout, or a launch that only brought visitors. There's more on what that overlay can and can't tell you.
If none of these applies, the built-in analytics is probably enough, and you can stop here.
Two things to check before you paste
Sign up for the tool you picked, add your site and copy the snippet it gives you, usually a single <script> tag. Copy it exactly as given. Don't retype it or change its attributes unless the tool's docs tell you to. Then check two things:
- The domain. Register the address visitors actually see. On Framer's free plan that's a Framer domain; as of November 2026, connecting your own domain needs a paid plan. If you've connected one, use that, not the Framer address.
- Page changes without a reload. Framer sites can move from page to page without loading a new document, which Framer describes as SPA-style navigation. A script that only counts full page loads records the first page of each visit and nothing after it. Some tools notice these page changes on their own, others need a setting. Fathom's Framer instructions, for example, add
data-spa="auto"to its script for exactly this reason. Look for “single-page app”, “SPA” or “client-side navigation” in your tool's docs.
Add the script in Framer
Framer's help page on custom code describes the current steps:
- Open Project Settings and choose the Custom Code tab in the left sidebar.
- Click Add Script, or the + icon if there's already code there, and give the snippet a name you'll recognise later, such as the name of the tool.
- Paste the snippet and choose where it goes. Framer can place code at the start or end of the
<head>and of the<body>. Use the end of the<head>unless your tool's instructions say otherwise. - Don't pick specific pages. Framer lets you limit a snippet to selected pages, but analytics has to run on all of them.
- Leave it set to run Once, unless your tool's own Framer instructions say otherwise. Once is the default, and Framer says it can be used for third-party scripts. Run on every page visit executes the code again each time someone visits a page, which is meant for things like tracking events. With a whole analytics script it can mean loading the tool more than once per visit.
- Save.
If the tool is Google Analytics, use the Google Analytics Measurement ID field in Framer's site settings instead, and don't add the same tag through custom code as well.
Publish, then test on the live site
Framer doesn't load custom code in the canvas preview, so nothing is counted until you publish. Publish or update the site, then do this on the live site in a normal browser window:
- Turn off any ad or tracker blocker for this test, or use a browser without one. Framer's own help page points out that some blockers stop one analytics tool from loading and let another through.
- Open the developer tools (F12, or Cmd+Option+I on a Mac), go to the Network tab and reload. Look for a request to your analytics tool. If it's there, the script loaded.
- Open the tool's live or real-time view, if it has one, and look for your visit.
- Click through three or four pages using the site's own links, not the address bar, and check that each one shows up as a separate pageview. This is the step that catches a script that only counts full page loads, and the one people skip.
If only the first page shows up, go back to your tool's docs for its single-page app setting before you trust any of its numbers.
If the numbers look wrong
- Nothing at all. The site wasn't published after the change, the snippet is limited to certain pages, or a blocker stopped the request.
- Every visit is one page long. The script isn't seeing page changes, and your bounce rate will look far worse than it is. Run the click-through test above.
- Everything counted twice. The tool is installed twice: two snippets in the Custom Code list, a site-wide snippet plus a page-level one, or Google Analytics in both the Measurement ID field and custom code. Remove one.
- A lot of Direct. Plenty of real visits arrive without a referrer. There's a separate article on what hides in direct traffic.
- Small numbers that jump around. On a new site, your own testing can be a large share of the traffic for the first few days.
Two tools, two sets of numbers
If you keep Framer's analytics and add another tool, the two won't agree. Framer counts unique visitors within a one-day window, so someone who comes back tomorrow counts again. A tool that keeps a visitor ID in a cookie can count that same person once across weeks. Blockers stop some tools and not others, and tools handle bots differently.
A gap doesn't mean one of them is broken. Check that they rise and fall on the same days. There's a longer explanation of why analytics numbers don't match, and which number to use for what. Run both for a few weeks, notice which one you actually open, and remove the other.
The short version
- Look at Framer's built-in analytics first.
- Add a tool only for a question the built-in one can't answer.
- Check whether the tool needs a setting for single-page apps.
- Project Settings, Custom Code: end of the head, all pages, run Once.
- Publish, then test on the live site by clicking through several pages.
- Expect two tools to disagree, and keep the one you use.
Lomen is one of the tools you could add this way, as one script tag in Framer's custom code. It sets no cookies, never stores IP addresses and by default stores nothing in the browser. On top of the usual traffic reports, it groups visits from nine AI assistants by name, matched on both the referrer and utm_source, puts revenue from Stripe, Shopify, Lemon Squeezy, Polar or Paystack on the same chart as visitors, and has Lomen AI, a chat that answers questions about your own figures. It has no custom events or funnels, so for tracking clicks, forms or conversions, Framer's own tracking is the closer fit. It's free during the public beta.