, -

Simple Analytics Script for No-Code Apps: A Step-by-Step Setup with Litlyx

What We Are Building and Why It Matters for No-Code Apps

A simple analytics script for a no-code app is a single HTML snippet you paste into your site's head section, and it starts collecting data immediately with zero build steps required. That is exactly what we are setting up here: a Webflow site with live page view tracking and a custom event, running in under ten minutes.

Most analytics tools were designed for developer workflows. They assume you have a terminal open, an npm install ready, and a tag manager configured. For no-code builders, those assumptions break the workflow entirely. You either wrestle with integrations that were never meant for visual editors, or you end up slapping a banner on your site that drives visitors away before they even read a headline.

Litlyx cuts through that problem entirely. It is a Privacy-first analytics platform that is fully EU-hosted and GDPR-compliant by design, collecting no personal identifiers at any point. The entire setup comes down to one script tag with a workspace ID, which any no-code platform that accepts custom head code can handle without a developer in the room.

Finish this guide and you will have a live dashboard showing real-time page views, referrer sources, and a custom event firing on a button click, with no build pipeline touched.

What Do You Need Before You Start?

The prerequisites are minimal. A no-code platform that supports custom head code embeds, and a free Litlyx account. That is genuinely the full list. No npm, no terminal, no build pipeline, no developer waiting on standby.

On the platform side, any tool that lets you paste HTML into the head section will work. Webflow, Framer, Carrd, and even Notion-based sites all qualify. If you can reach a "Custom Code" or "Head Scripts" panel inside your platform's settings, you are ready to go.

For the Litlyx side, sign up for a free account and create a new project. The dashboard assigns a unique project ID instantly, and that ID becomes the only configuration value you will ever need to touch. As the Litlyx setup docs confirm, the entire process takes around 30 seconds and requires nothing more than a single script tag.

Because Litlyx uses Cookieless tracking, your no-code site needs no prompt banner at all. For builders who have watched visitors bounce the moment a privacy pop-up appears, this removes a real and recurring blocker before your first data point even comes in.

How Do You Create a Litlyx Project and Get Your Script Tag?

Getting your script tag takes under a minute. Sign up at Litlyx, create a new project, and the dashboard generates a unique project ID immediately. No configuration wizard required. That ID is the only thing you need to start collecting data-driven decisions from your no-code app.

Where to Find Your Project ID in the Litlyx Dashboard

Once you log in, the dashboard presents your project ID front and center. It looks like a short alphanumeric string, something along the lines of your_project_id. Copy it directly from there; you will paste it into a single data attribute on the script tag. API keys, environment variables, and build pipelines simply do not enter the picture.

What the Default Script Tag Looks Like

The entire installation is one line of HTML:

That snippet is fully self-contained. As documented in the Litlyx setup guide, the whole process takes about 30 seconds from sign-up to live data. Paste it into your platform's head section and you are done.

By default, the script collects page URL, referrer, browser language, and screen size. It gathers nothing that identifies an individual visitor. IP addresses are never stored, browser fingerprinting does not happen, and no data reaches third parties. This is what makes Litlyx a genuinely GDPR-compliant, Privacy-first analytics platform rather than one that simply claims compliance on a marketing page. For no-code builders, that distinction matters because it eliminates the entire permission-banner problem before it even starts.

How Do You Add the Script to a Webflow Site?

Honestly, adding the Litlyx script to a Webflow site takes under two minutes and requires zero changes to your visual design. You work entirely inside Webflow's project settings, paste one line of code, and publish. That is the whole process.

Step-by-Step in Webflow

Webflow supports custom code embeds in the head section via Project Settings, which means no-code builders can inject third-party scripts without touching a single component on the canvas. Here is exactly what to do:

1. Open your Webflow project and click the gear icon to enter Project Settings.
2. Select the Custom Code tab.
3. Locate the Head Code field at the top of the page.
4. Paste your Litlyx script tag into that field. It should look like this:

1. Replace YOUR_PROJECT_ID with the ID copied from your Litlyx dashboard.
2. Click Save Changes, then hit Publish to push the update to your live site.

Once the site is live, open a new browser tab and visit any published page. Switch back to your Litlyx dashboard and watch the real-time counter tick up. That first page view confirms the script is firing correctly. Litlyx automatically tracks page visits, real-time users, and unique visitors without additional configuration, so basic page view data just works from the moment you publish.

Your visual design stays completely untouched. One save and one publish covers every page on the site.

The Same Approach in Framer and Carrd

The pattern is consistent across every no-code platform that accepts a head snippet. Framer users follow an almost identical path: open Project Settings, select Custom Code, and paste the Litlyx tag into the head section before publishing. The script loads on every page automatically.

Carrd works slightly differently. Instead of a project-level settings panel, you add an Embed element to your site, set its type to "Code," and paste the script tag there. Position it so it renders in the head, and your analytics are live on the next save.

Any platform that lets you inject raw HTML into the document head follows this same logic. Bubble, Editor X, and similar tools all have equivalent custom code fields. One script tag covers the entire site, every page, every visit.

How Do You Track a Custom Event Without Writing a Build Script?

Recording custom events in Litlyx requires no external JavaScript file, no build pipeline, and no package manager. Once the script tag loads on your page, Litlyx exposes a global `Lit` object that any inline code block can call directly. That single fact changes everything for no-code builders.

The global Lit object is available the moment the browser finishes parsing the script tag you added in the previous step. You can call it from an onclick attribute, from a Webflow embed block, or from any platform that lets you write a small snippet of inline HTML. Imports, module bundlers, and terminal commands play no role here whatsoever.

Adding the onclick attribute in Webflow

Here is the concrete workflow for tracking a "Sign Up" button click in Webflow:

1. Select your button element in the Webflow Designer.
2. Open the Element Settings panel (the gear icon on the right sidebar).
3. Scroll to the Custom Attributes section.
4. Add a new attribute with the name onclick and this value:

1. Publish the site and click the button on the live URL.

That single attribute is the entire implementation. No external JS file lives on your server; the handler runs inline when the visitor clicks. Within seconds, the event appears in your real-time insights dashboard under the Events panel. You will see the event name, a running count, and a timestamp, all without refreshing the page.

Passing metadata with your event

The Lit.event() method accepts an optional second argument: a plain JavaScript object containing any metadata you want to attach. This is useful when you need to distinguish between similar interactions, such as which pricing plan a visitor clicked or which form field they abandoned.

The syntax looks like this:

You paste that entire string as the onclick value in Webflow's Custom Attributes panel, exactly as shown above. The metadata object travels with the event payload to the Litlyx dashboard, where you can filter and segment by those properties to make genuine data-driven decisions about your funnel.

Because this approach is entirely Cookieless, Privacy-first analytics stays intact. No personal identifier is attached to the event; Litlyx records what happened, not who did it. The result is accurate, actionable event data that satisfies GDPR-compliant requirements without adding a single line to a build script.

What Does the Litlyx Dashboard Show After Setup?

The Litlyx dashboard surfaces real-time, user-friendly insights the moment your first page view fires. You see a live counter update within seconds, a session timeline that builds as visitors move through your site, and a clean breakdown of every key metric without any extra configuration.

The default view presents exactly what most no-code teams need to make data-driven decisions on day one:

• Unique visitors and page views, updated in real time as traffic arrives
• Top pages, ranked by visit count so you know which content or offers are resonating
• Referrer sources, showing where your audience is coming from (organic search, social, direct)
• Device and browser breakdown, useful for optimising layouts across screen sizes

Because Litlyx automatically tracks page visits, real-time users, and unique visitors without additional configuration, you are never hunting through settings menus just to turn on basic reporting. Everything is on by default.

The custom events panel sits alongside these default metrics. After the previous step, your signup_click event appears there with a running count and a timestamp for each trigger. You can filter by date range or event name, which turns raw click data into a clear picture of how visitors are engaging with your calls to action.

Privacy is baked in at the infrastructure level. As a privacy-first, all-in-one analytics platform made and hosted in the EU and fully GDPR-compliant, Litlyx satisfies your data residency requirements without any additional configuration on your part. There is no separate data processing agreement to hunt down, no region selector to toggle.

Compare that to Google Analytics, where simply achieving a GDPR-compliant state requires configuring IP anonymisation, data retention windows, a permission management platform, and potentially a custom subdomain for the collection endpoint. With Litlyx, you paste one script tag and the dashboard is already compliant.

How Do You Verify That Cookieless Tracking Is Actually Working?

Look, confirming that Cookieless tracking is live takes less than two minutes using tools already built into your browser. Open Chrome or Firefox DevTools, go to the Application tab, and click on the storage section in the left panel. After visiting your no-code app's live URL, that list should be completely empty of any Litlyx entries. Zero stored identifiers means zero compliance risk.

Next, switch to the Network tab and reload the page. You will see a single lightweight beacon request fired by the Litlyx script. The payload is minimal by design, carrying only anonymous data like page URL, referrer, browser language, and screen size. No personal identifiers, no fingerprints, nothing that maps back to an individual visitor.

This matters enormously for no-code apps. Because Litlyx uses no stored identifiers and requires no permission banners, you skip the permission management platform entirely. That means no intrusive pop-up greeting visitors the moment they land, which directly reduces bounce risk. Builders on Webflow, Framer, and Carrd can ship a cleaner, faster experience without layering in a third-party tool.

There is one more practical benefit worth calling out. Privacy-first analytics that operate without stored identifiers tend to pass through most browser privacy shields naturally, because the data collection happens in a first-party context rather than through a third-party network. Visitors using strict privacy settings in Firefox or Brave are far less likely to block a lightweight first-party beacon than a traditional third-party script loaded from an external domain. Your data stays accurate, and your visitors stay undisturbed.

What Are the Next Steps After Your First Analytics Script Is Live?

Getting your first page view to appear in the dashboard is satisfying, but the real value of a simple analytics script for no-code apps comes from what you build on top of that foundation. One script tag is the starting point, not the finish line.

Expand Your Custom Event Coverage

The Lit.event() call you used for the sign-up button works equally well for any other interaction on the page. Think about the moments that actually matter to your business: a form submission, a video play, a click on an outbound link to a pricing page. Each of those can be wired up with a one-line inline handler, no external JavaScript file required. Litlyx automatically tracks page visits and unique visitors out of the box, so your custom events layer on top of a solid baseline without any duplication of effort.

Turn Event Data Into Data-Driven Decisions

Raw event counts are useful, but goal funnels are where user-friendly insights become actionable. Inside the Litlyx dashboard, you can group related events into a funnel to see exactly where visitors drop off between landing on a page and completing a sign-up. That view shifts you from passive observation to genuine data-driven decisions about your no-code app's design.

If your project grows and you need to push events from a backend or a third-party integration, the Litlyx API supports server-side event calls, so the same Privacy-first analytics setup scales with you. Finally, consider sharing your public dashboard link with clients or teammates. It acts as a lightweight, always-current reporting layer with zero extra configuration needed., -

This article was produced with AI assistance and reviewed by our editorial team before publication.