Data Goat (by Flow Ninja)

Webflow publishes the site. The event tracking underneath it is still your job. Traffic counts are one thing, but knowing which outbound link a visitor clicked or which custom event fired means wiring a GA4 data layer by hand, and most marketing teams do not have that skill on staff.

Data Goat existed to close that gap, and it no longer does. Flow Ninja shut it down on November 12, 2024, and every datagoat.co address now redirects to the agency's own site. If you were running it, the tracking it configured stopped with it. The replacement is a mix of native Webflow reporting, the Webflow MCP server for reading that reporting from an AI client, tracking scripts you install yourself, and the Webflow Data API v2.

Marketing teams get reporting they can run without a developer. Developers get the endpoints that recreate Data Goat's form and event data server-side.

How to replace Data Goat on Webflow

No single Webflow feature replaces Data Goat, because Data Goat bundled reporting and data-layer setup into one install. Split the two apart and each half has a clear home in Webflow today.

What was Data Goat? Data Goat was a no-code analytics and tracking tool built specifically for Webflow by Flow Ninja, a Webflow agency. It set up the GA4 data layer automatically and tracked outbound link clicks, site clicks, form submissions, post types, and custom events from inside Webflow, so a marketer could get event-level reporting without GA4 expertise. Flow Ninja retired it to refocus on agency work.

Because the product is gone rather than merely unmaintained, there is no migration path to follow and nothing to keep working. What you are doing is rebuilding, and how far you go depends on how much of Data Goat's output you actually used. Match each function to the corresponding Webflow method:

• The Webflow MCP server: reads traffic, top pages, engagement events, and time on page from your AI client, which is the reporting half of Data Goat without a dashboard to log into.
• Native reporting and marketplace apps: cover traffic and behavior analytics with no code on the page, and this is where most former Data Goat users land.
• Code Embed and custom code: install the GA4 and Google Tag Manager scripts Data Goat used to add for you, which is the only way to get custom events back.
• The Webflow Data API v2: gives full control over form and site event data server-side, at the cost of running an endpoint yourself.

These methods combine. A common setup pairs native reporting for traffic with one custom code block for the two or three events that actually matter to the business.

Read site analytics through the Webflow MCP server

The MCP server connects an AI client directly to your Webflow projects, and its Analyze tools read the same traffic and engagement data the reporting panel shows. Instead of opening a dashboard, you ask which pages lost sessions this month and get the answer where you are already working. This is the closest thing to Data Goat's reporting layer that needs no script on the page at all.

Two gates are worth knowing before you plan around it. The MCP server itself is listed on the free Starter plan, so connecting costs nothing. The Analyze tools are a different matter: they read from Webflow Analyze, which Webflow sells as an optional add-on on paid Site plans, priced by monthly sessions. Check current Webflow pricing before you assume a native swap is free, because Data Goat was not billed this way.

The MCP server also carries documented limits. It does not cover every Webflow capability, and it authorizes against a single workspace at a time, so a multi-workspace agency needs one connection per workspace.

Replace Data Goat with native reporting or an analytics app

For traffic and behavior reporting, an app or the native panel gets you back to useful numbers fastest, and this is the route Flow Ninja itself pointed users toward. What none of these do is rebuild custom GA4 events, so read this method as covering the reporting Data Goat gave you rather than the tracking it configured.

To set up a replacement:

1. For heatmaps, session recordings, and click analytics, install the Microsoft Clarity app on your site.
2. For GA4, create a property and paste its tracking code under Site settings > Custom code.
3. Publish the site.

Tracking starts on the next publish, and nothing already collected transfers across. Both Clarity and Google Analytics are third-party services that set cookies and load a script, so they inherit the consent and page-weight costs described below. Webflow's own reporting does not, which is the strongest argument for staying native where the native numbers are enough.

Behavior analytics is also worth scoping to the pages that matter rather than the whole site. A pricing page or a signup flow will tell you more per recording than a blog archive, and the same logic applies whether you use Clarity or a tool like Hotjar and Webflow together.

Add tracking scripts with Code Embed and custom code

This is the method that actually rebuilds what Data Goat automated: form submission events, custom events, and events triggered by outbound link clicks. You paste the scripts into the site-wide custom code sections or into a Code Embed element, which is the manual work Data Goat existed to remove. Both surfaces accept HTML and JS in <script> tags and CSS in <style> tags, but no server-side languages such as Perl, PHP, Python, or Ruby.

Editing custom code needs Site manager or Designer permissions, and a Core, Growth, Agency, or Freelancer Workspace plan, or any active Site plan. Each custom code section and Code Embed element holds up to 50,000 characters, which is far more than a tag manager snippet needs.

Install site-wide scripts in site settings

GA4 and Google Tag Manager head snippets belong in the site-wide head code, because anything you configure there fires on every page. Per-page widgets stay in a Code Embed instead.

To install the scripts:

1. Go to Site settings > Custom code.
2. Paste the GA4 or GTM snippet in the Head code section and click Save.
3. For GTM's second snippet, open the Add panel and place a Code Embed element under the Body, then paste the snippet there.
4. Publish the site.

After publishing, events flow into your GA4 property or GTM container with no plugin in the middle. Adding external script tags to the head slows page loads, which is Webflow's own warning and the honest cost of this route: Data Goat's convenience is replaced by a tag you own and have to keep an eye on.

Embed per-page components with the Code Embed element

The Code Embed element places third-party HTML inline on a single page, which keeps a one-off widget out of the site-wide custom code where it would load everywhere.

To add an embed:

1. Open the Add panel and drag a Code Embed element onto the page.
2. Paste your code and click Save and close.
3. Publish the site.

Load analytics and ad scripts with the async attribute so they do not block rendering. Any of these scripts also sets cookies on behalf of a third party, so if you serve EU or UK visitors you need a cookie consent banner gating them before they fire. Data Goat inherited whatever consent setup you already had; a script you install yourself does not.

Build with the Webflow Data API v2

The Webflow Data API v2 recovers form submissions and Webflow CMS item data server-side, with no browser tracking involved. That makes it the most reliable half of a Data Goat replacement and the least complete one, because it cannot see a click that never became a submission.

The base URL is https://api.webflow.com/v2 and authentication uses a bearer token. API v1 was deprecated in March 2025, specifically on March 31, so build anything new on v2. Site tokens are the quickest credential to issue, but they cannot reach the authorization, custom code, or workspace activity log endpoints, and each site is capped at five of them. Webhook creation needs a Data Client App token instead.

The form submissions endpoint returns the submission data Data Goat tracked in the browser, while webhooks push events such as form_submission and site_publish to any endpoint you run. Use a webhook to recreate the workflow most Data Goat users cared about.

Capture form submissions with a webhook

Data Goat tracked form submissions in the browser through the data layer. A form_submission webhook captures the submitted fields and form metadata server-side and forwards them anywhere. It does not reproduce client-side GA4 session or attribution context unless you collect and submit those values as fields yourself, which is the one real gap between the two approaches. The payload carries name, siteId, data, submittedAt, formId, formElementId, and a schema array describing each field.

To register the webhook:

1. Get a Data Client App bearer token with the sites:write scope, because the create webhook endpoint does not accept site tokens.
2. Send POST /v2/sites/{site_id}/webhooks with the body { "triggerType": "form_submission", "url": "https://your-endpoint.example.com/hook" }.
3. Parse payload.data on your endpoint and forward the field values to your CRM or a Slack channel.

Your endpoint must answer with a 200. Webflow's webhook retry rules retry a failed delivery up to three more times and then deactivate the webhook entirely, and a redirect or an SSL problem counts as a failure, so point the hook at a final URL with a valid certificate. You can register up to 75 webhooks per trigger type per site. Audit what you have with GET /v2/sites/{site_id}/webhooks and remove one with DELETE /v2/webhooks/{webhook_id}.

What you can build with the Data Goat Webflow integration

Rebuilding Data Goat's tracking on Webflow keeps event and form data flowing without a plugin that can be discontinued out from under you, which is the lesson of the shutdown more than any individual feature.

• GA4 event tracking without a plugin: Install Google Tag Manager through site-wide custom code and use it to track the outbound clicks and custom events Data Goat covered on a marketing site.
• Behavior analytics on the pages that convert: Add Microsoft Clarity for heatmaps and session recordings on a pricing or signup page, then watch where visitors abandon the form.
• Form-to-CRM pipelines: Route form_submission webhook payloads into a CRM record and fire lead notification workflows on every submission.
• Post-type event tracking: Fire custom GA4 events from a Code Embed on blog Collection pages to approximate the post-type reporting Data Goat provided.
• Agent-readable reporting: Connect the MCP server and pull traffic, top pages, and engagement events into the AI client your team already uses, with per-site permissions governing what it can reach.

Reach for the API route when browser snippets do not give you enough control over how events are captured and where they go. If you would rather manage the tracking scripts themselves programmatically instead of pasting them into site settings, see how to apply custom code to pages through the Data API.