How to add analytics to a Carrd site: Site Analytics or an Embed
Carrd's Site Analytics setting offers its own view counter and eight other tools. Any other script goes in a hidden Embed set to Head, on Pro Standard or higher. And since sections switch within one page, a tool that names pages by their path sees only the home page.
In this article
Carrd sites don't include analytics by default. There are two ways to add it: the Site Analytics setting, which offers Carrd's own counter and a list of other tools, or an Embed element with your tool's script tag. Both need a paid plan. And a Carrd site is one page, so before the numbers come in, it's worth knowing what your tool will make of its sections.
This guide covers the plan, the built-in options, where the script goes, how to test it and why the reports look the way they do. The steps work for any analytics tool that installs with a script tag. The Carrd details come from Carrd's documentation, as of November 2026.
Check your plan first
Carrd's docs mark both routes, Site Analytics and the Embed element, as needing Pro Standard or higher. As of November 2026, Carrd's plans page lists Pro Lite at $9 a year, Pro Standard at $19 and Pro Plus at $49, with embeds and analytics in Pro Standard and Pro Plus. On the free plan or Pro Lite, neither setting is open, and nothing on the analytics side gets around that.
What Carrd already offers
Site Analytics lives in the site's settings, not in the editor. In the Dashboard, open the Sites tab, click the site's Manage icon, choose Analytics in the sidebar and, under Site Analytics, click Select Provider. You pick the provider from a dropdown and click Enable. There are two kinds of choice:
Carrd Analytics
Carrd's own counter, which its docs call native and cookie-free, and say is in beta. It counts views, each one a single load of the site, with presumed duplicates within a short period filtered out. Views are all it counts, so it isn't a count of unique visitors or visits, and for traffic sources and conversions, Carrd's page on it recommends one of the other providers. It shows the last 24 hours, 7, 30 or 90 days, uses no cookies, browser storage or external script, and turning it off deletes the counts.
Other tools from the list
As of November 2026, the same dropdown offers Cloudflare Web Analytics, Fathom Analytics, Google Analytics, Matomo, Plausible, PostHog Web Analytics, Simple Analytics and Umami. If your tool is one of them, select it there rather than pasting its script. Carrd notes that some providers collect more data from visitors and asks you to read their policies before you enable one.
Add the script with a hidden Embed
Sign up for the tool you picked, add your site using the address visitors actually see, and copy the snippet it gives you, usually a single <script> tag shaped roughly like this:
<script defer src="https://analytics.example.com/script.js" data-site="YOUR-SITE-ID"></script>That's a placeholder, not a working tag. Copy the exact one from your tool's dashboard rather than from an email or a document, where straight quotes can turn into curly ones and quietly break it. Then, in the Carrd editor, as Carrd's page on embedding custom code describes it:
- Click Add Element, then Embed.
- Set Type to Code and paste the tag into the Code field. It takes HTML,
<style>and<script>tags. - Give it a Label, such as the tool's name, so you can tell it apart from other embeds later.
- Set Style to Hidden and choose Head. Carrd also offers Body Top, just after the opening
<body>tag, and Body End, just before</body>. Use one of those only if your tool asks for it.
A hidden embed sits outside the normal flow of elements, so its place in the element list doesn't matter. Carrd suggests moving it somewhere out of the way, such as the end of the site. A Carrd site is one page, so one embed in the head covers every section. The other style, Inline, puts the code exactly where the element sits, inside one of your sections, like any visible element. An analytics tag belongs in the head.
One hidden embed, set to Head, covers every section of a Carrd site.
Publish, then test the live site
Carrd's docs say an embed outputs nothing in the builder, so the tag only runs once you publish. Publish, then do this on the published site, not in the editor:
- Open the site's real address in a private window, with any ad or tracker blocker turned off for the test.
- Open the developer tools and search the Elements panel for the script's address. If it isn't there, check that you published after adding the embed, and that the embed's Type is Code.
- Go to the Network tab and reload. Filter by your tool's domain. You should see the script load, and usually a second request that sends the pageview. A blocked request is marked as an error.
- Open the tool's live or real-time view, if it has one, and look for your visit.
- Switch to another section and watch the Network tab. No new request usually means your tool counts the whole site as one page. The next section explains why that's expected.
Sections aren't pages
Carrd builds the feel of several pages out of sections on one page. As Carrd's section docs describe it, a Control element set to Section Break starts each one, its name becomes the link (#work, say), and visitors can open it directly at yoursite.carrd.co/#work. Anything before the first break goes in a section Carrd names home.
Switching sections changes only the part of the address after the #. That part, the fragment, isn't part of the page's path, and following a link to it doesn't load a new page. Carrd Analytics counts the same way: a view is one load of the site. What your own tool shows depends on how it counts:
- A tool that counts page loads sees one load, however many sections the visitor opens.
- A tool that names pages by their path records every section as
/. Top pages has one row, and every visit enters and leaves on it. - Pages per visit stays close to one, and in tools that count a bounce as a visit with one pageview, bounce rate sits near the top. That says nothing about the page. A bounce isn't a bad visit explains what to read on a one-page site instead.
Some tools can count a change after the # as a page of its own. Plausible, for example, documents a hash-based routing option for sites whose page paths carry a #. If yours has one, test it on the published site by switching sections before you rely on it.
One more thing follows from the fragment. When you share a link to a section, the campaign tags go before the #, not after it:
https://yoursite.carrd.co/?utm_source=newsletter&utm_medium=email#workAnything after the # is part of the fragment, not the query string, and a tool that reads campaign tags from the query string won't see it. For the tags themselves, a small UTM naming system keeps the reports readable.
Sign-ups and clicks are something else
On a one-page site, the number that matters is often the sign-ups, not the views. A form submission or a click on a button isn't a page load, so a tool that only counts pageviews doesn't see it. Carrd's own forms can fill part of that gap. According to Carrd's page on UTM parameters, a form with the Collect UTM parameters option turned on adds the visit's UTM values to each submission:
- A contact form appends them to the message.
- A signup form connected to a mailing service fills them into matching custom fields. Carrd lists which services it supports, and Mailchimp's merge tags are shortened to fit its length limit, such as
UTM_CAMPAI. - A custom form includes them as fields named after the parameters, such as
utm_source.
The submissions then say which tagged link each sign-up came from, with no analytics tool involved. Clicks on buttons that aren't forms need a tool with event tracking.
If the numbers look wrong
- Not in the Elements panel. The site wasn't published after the embed was added, or the plan doesn't include embeds.
- There, but nothing loads. A blocker stopped it, or the tag broke on the way: curly quotes, a missing
</script>, or the tag pasted inside other code. - The script loads, but no visits appear. The tool expects a different address. A Carrd site can be published to a
.carrd.coaddress, a custom domain or a custom subdomain, so register the one visitors use. Carrd redirectswwwto the bare domain or the other way round, depending on which one you entered. - Only one page in the reports. That's the sections, and it's expected. See above.
- Everything counted twice. The tool is in the Site Analytics dropdown and in an Embed, or the same tag is in two embeds. Remove one.
- Carrd Analytics and your tool disagree. They will. Carrd filters presumed duplicate views, so a reload may count once there and twice in a tool that counts every load. Carrd Analytics uses no external script, so a blocker that stops your tool's script may leave Carrd's count alone. Check that both rise and fall on the same days, and read why no two analytics tools agree on your traffic for where the gaps come from.
Does the page still need a cookie banner?
Carrd Analytics uses no cookies or browser storage. A cookie-free tool sets no cookies of its own, though some keep an identifier in local storage, so check what yours writes. The rest of the page can add more. The same Analytics panel has Marketing Trackers for the LinkedIn Insight Tag, Meta Pixel and TikTok Pixel, which Carrd warns collect additional data from visitors, and embedded videos and other embeds can bring their own. To see what your published site stores, open the developer tools, clear the site data, open a few sections and look under Cookies and Local storage. Whether you can drop the banner depends on that whole list, and what it takes to run a website without a cookie banner goes through it.
The short version
- Check that your plan is Pro Standard or higher.
- Try Carrd Analytics, or a tool from the Site Analytics list, first.
- Otherwise: Add Element → Embed, Type Code, Style Hidden, Head.
- Publish, then test on the live address.
- Expect one page for the whole site. Sections aren't pages.
- Put UTM tags before the #, and turn on Collect UTM parameters on forms.
Lomen is one of the tools you could add this way. It isn't on Carrd's Site Analytics list, so its one script tag goes in a hidden Embed set to Head, with no API key, package or build step. Pageviews only count from the domain you added and its subdomains, so add the address you publish to: a carrd.co address and your own domain are different domains, and visits to one don't count for the other. It names pages by their path, so a Carrd site shows as one page, /, and switching sections never adds a pageview. A second copy of the tag for the same site does nothing, so a tag in two embeds can't double the count. Its standard tag sets no cookies and by default keeps nothing in the visitor's browser, and IP addresses are never stored. It groups visits from nine AI assistants by referrer and utm_source, and if you sell through Stripe, Shopify, Lemon Squeezy, Polar or Paystack, it can read that revenue and show it on the same chart as visitors, not split by source. It has no custom events or funnels, so counting sign-ups and button clicks is a job for the form's own submissions or a tool with event tracking. Lomen is free during the public beta.