Nocodelytics

Nocodelytics tracks the interactions that native analytics miss: CTA clicks, Jetboost searches, form submissions, and engagement by Webflow CMS collection item. Paste one script into your site's head code and tracking starts automatically, with no Tag Manager or event configuration required.

Agencies use it to build client-facing dashboards across a portfolio of sites, and founders use it to measure blogs, job boards, marketplaces, and membership sites where engagement matters more than raw pageviews.

How to integrate Nocodelytics with Webflow

What is Nocodelytics? Nocodelytics is a no-code analytics tool built for Webflow sites. It tracks page views, clicks, searches, and CMS item engagement through a single script install, and supports form submission tracking by form ID, with no Tag Manager required. It also integrates with Jetboost for search tracking and with Memberstack and Outseta to attach member IDs and emails to tracked events.

Teams reach for Nocodelytics when native reporting can't answer questions about specific interactions. A magazine site tracking paid ad placements in a CMS Collection and a job board measuring listing views both need element-level data that pageview counts don't provide. Agencies delivering per-client reports need the same view. Setup runs through custom code and embed features, so most of the work happens without touching a codebase.

The Nocodelytics-Webflow integration supports three approaches:

• The Nocodelytics app is the official Marketplace app, but the documented setup still centers on copying the Nocodelytics tracking script and pasting it into your Head code.
• Code Embed and HTML Embed elements let you place tracking snippets and embed live dashboards at specific spots on a page.
• The Webflow Data API gives you programmatic access to form submissions, CMS items, and webhooks, but requires server-side development.

Most implementations combine the app install with embed elements depending on whether you need dashboards on the page.

Install the Nocodelytics app

The Nocodelytics app is the official Marketplace listing for Nocodelytics. It's approved and includes security and management features. The documented setup still centers on copying the tracking script from Nocodelytics and pasting it into your Head code; once that script is live, core tracking starts automatically, while form metrics are configured by form ID. Use this method when you want analytics running in minutes without writing tracking code by hand.

The app covers the core tracking features, with form metrics configured in Nocodelytics:

• Page views, button clicks, and link clicks
• Search queries, including Jetboost real-time search
• CMS collection item engagement
• Form submission tracking by form ID

To set up the integration:

1. On the Nocodelytics Sites page, click Finish Setup next to your site and copy the tracking script.
2. Go to Site Settings > Custom Code and paste the script into the Head code section. See Custom code in head and body tags for reference.
3. Click Save, then publish the site.

Custom code fields require a paid Site plan or an active Workspace plan. The head section accepts up to 50,000 characters, so the tracking script leaves plenty of room. To disable tracking later, delete the script from the head section and republish.

Add tracking and dashboards with Code Embed and HTML Embed elements

Beyond the site-wide script, you can place tracking configuration and live dashboards at specific points on a page using embed elements. Use Code Embed for on-canvas snippets and the HTML Embed element for iframe-based dashboards. This approach matters when you want analytics visible inside the page itself, such as a client-facing report or a member dashboard.

Track specific buttons, links, and forms by ID or class

Once the tracking script is installed, configure the target in the Nocodelytics dashboard; the site only needs the site-wide script in place.

To track a specific button or link:

1. Select the element and open the Element Settings tab (gear icon), then copy or add a unique ID.
2. In Nocodelytics, create a New Metric, choose Button or Link Clicks, and enter #unique-id.

To track multiple elements that share a class, open the Style tab (paintbrush icon), copy the shared class, and enter it as .class-name in the metric. Class names use lowercase with spaces replaced by hyphens. For form tracking, create a New Metric, choose the form option, and supply the form's ID to see form views alongside interactions and submissions in one chart.

Embed a single metric or a full dashboard

You can surface Nocodelytics data inside a page using the HTML Embed element. Agencies use this to give clients live access to their own analytics, and membership sites use it to show members metrics scoped to their own content.

To embed a single metric:

1. Add an HTML Embed element where the metric should appear.
2. In Nocodelytics, open the dashboard containing the metric, click Share (enable sharing if needed), and copy the embed code.
3. Paste the code and append ?metric=<METRIC_ID> to the src attribute, using the metric ID copied from the Nocodelytics URL bar (the value after metric/).

For member-specific dashboards, append the path ?path=collection_slug/item_slug to the src attribute so each member sees data tied to their own CMS item. Embeddable dashboards and member dashboards are Growth plan features, so confirm your plan before building these into a client site.

Build with the Webflow Data API

Programmatic work happens on the Webflow side because Nocodelytics lacks a public REST API. The Webflow Data API gives you access to form submissions, CMS items, custom code registration, and webhooks. This path is for developers building custom pipelines, and it requires server-side code and a Bearer token from your dashboard.

The available APIs cover Webflow-side records that sit outside Nocodelytics exports:

• The Data API handles CMS collection items and form submissions
• Webhooks trigger real-time events between systems

Because Nocodelytics can't emit webhooks or export analytics through an API, use these endpoints only for Webflow-side records such as CMS items, form submissions, custom code registration, and publish, CMS, or form webhook events. You can't currently export click, search, or Nocodelytics engagement metrics programmatically.

Pull form submissions programmatically

When you need form data in a database or reporting tool, query the Data API directly. Nocodelytics tracks submission counts inside its dashboard, but the raw records live on the Webflow side.

To retrieve form submissions:

1. Get an API Bearer token from your dashboard.
2. Send a GET request to https://api.webflow.com/v2/sites/{site_id}/form_submissions. Use your site ID for {site_id}.
3. Parse the JSON response, which returns all form submission records for the site.

Use this route when you need raw form records outside the Nocodelytics dashboard.

Register webhooks for CMS and form events

For real-time notifications instead of polling, register a webhook. This lets an external service react the moment a CMS item changes or a form is submitted.

To register a webhook:

1. Send a POST request to https://api.webflow.com/v2/sites/{site_id}/webhooks with your Bearer token.
2. Set the trigger type for the event you need. Use collection_item_changed or collection_item_created for CMS changes. Use form_submission for forms.
3. Validate incoming deliveries using the x-webflow-signature header, which carries an SHA-256 HMAC.

Each site supports up to 75 webhook registrations per trigger type. Payloads arrive as JSON POST requests with fields like id, siteId, collectionId, and fieldData.

What can you build with the Nocodelytics Webflow integration?

Pairing Nocodelytics with your site lets you measure real user behavior without configuring event tags or writing tracking code.

• Build client analytics dashboards that track clicks, searches, form submissions, and top pages, then embed them into a page so clients log in and see their own reporting. Erickson Built used this approach and reported zero client churn over 12 months.
• Track CMS content and ad performance by measuring which collection items get the most views and clicks to prove value to advertisers or prioritize content. 253 Media tracks paid ad spots in a magazine client's CMS to generate advertiser reports tied to revenue.
• Measure conversions on CTAs and forms by tagging a specific button by ID or a group of CTAs by class to measure clicks, and track form submissions as conversion events. A landing page can report which hero button drives the most signups.
• Build member-specific dashboards by attaching Memberstack or Outseta member IDs to events and embed a dashboard scoped by CMS path so each logged-in member sees analytics for their own content.

If you need more control over site-side records such as CMS items or form submissions, the API integration path covers those cases with full flexibility.