Install GetFluxly on Webflow

Drop a single <script> into Webflow's project settings to enable autocapture across every page. Events flow into your GetFluxly project tagged with context.install_source = "webflow".

What you need

• A GetFluxly project (sign up at getfluxly.com).
• A Webflow project with site-level "Custom code" access (Workspace plan or higher).
• The Webflow site must be published for the snippet to run; preview URLs don't execute custom code.

Steps

1. Get the snippet

In the GetFluxly dashboard, open Settings, Install. Switch to the Webflow tab. The snippet is prefilled with your project's first active publishable key, the canonical API host, and data-source="webflow":

<script
  src="https://cdn.jsdelivr.net/npm/@getfluxly/browser@0.5.0/dist/gflux.iife.js"
  data-project="gflux_pub_yourkey"
  data-host="https://api.getfluxly.com"
  data-source="webflow"
  crossorigin="anonymous"
></script>

Click Copy. (Or copy from the dashboard's Install panel, which always shows the latest pinned SDK version.)

2. Paste into Webflow

In Webflow, open the project, then:

1. Project settings, Custom code tab.
2. Scroll to Footer code (the second textarea).
3. Paste the snippet.
4. Save changes.

3. Publish

Webflow's footer code only runs on the published site. Click Publish and choose the domain you want to track. The snippet starts executing on the next page load.

Verify

Step-by-step

1. Open the published site (e.g. https://your-site.webflow.io).
2. Open browser DevTools, Network tab.
3. Filter by events/batch.
4. Navigate to any page. You should see a POST to api.getfluxly.com/v1/events/batch returning 202.
5. In the GetFluxly dashboard, open the live feed for the project. The page_viewed event should appear within a few seconds, with context.install_source = "webflow" visible in the event detail.

Troubleshooting

| Symptom | Likely cause | | --- | --- | | Snippet not visible on the live site | Webflow didn't re-publish. Open Publish and confirm the latest publish includes the footer-code change. | | Network request returns 403 wrong_key_type | Pasted a server key (prefix gflux_secret_) instead of a publishable key. Copy from the dashboard's Install panel, which always uses a publishable key. | | Events appear but without install_source | The snippet is missing data-source="webflow". Re-paste from the Install panel; manually-edited snippets sometimes drop this attribute. | | No request at all | A Content Security Policy is blocking jsDelivr. Check the DevTools console for Refused to load the script. Add https://cdn.jsdelivr.net to your CSP script-src. |

What gets captured

Out of the box, autocapture sends page_viewed, click, form_submit, page_leave, rage_click, and uncaught JS errors. Each event includes:

• anonymous_id (rotates per visitor, persisted via cookie + localStorage)
• context.library (e.g. gflux-browser/0.5.0)
• context.install_source = "webflow" (this guide's main payoff)
• context.locale, context.timezone, context.viewport_*

To send custom events, call window.gflux?.track("event_name", { ... }) from any inline <script> block in a Webflow page or component.