Install Spurn on Webflow
Spurn runs on Webflow through one line of code in your site's head. It does nothing on organic visits and starts work when a visitor arrives from a paid ad.
Before you start#
- A Webflow site with access to Site settings. Webflow runs custom code on the published site only, not in the Designer.
- Your site's public key from Spurn: Sites, then your site, then the Install tab (it is also on the Keys tab). It looks like
sp_pub_XXXXXXXXXXXXXXXXXXXXXXXX.
Add the tag#
In Webflow, open Site settings, then the Custom code tab.
Paste this into Head code, with your public key:
<script async src="https://spurn.io/s.js" data-site="sp_pub_XXXXXXXXXXXXXXXXXXXXXXXX"></script>Click Save changes.
Publish the site. Saved code is not live until you publish.
The tag goes in Site settings rather than a page's settings, so it runs on every page. That matters: a paid visitor often lands on one page and buys on another.
Report conversions (optional)#
Detection and blocking work without conversions. Reporting them adds one more piece of evidence: a click that led to a purchase or a lead counts in its favour, and the dashboard shows which paid clicks converted.
Add this to the page visitors see after they convert, in that page's settings under Custom code, Before </body> tag:
<script>
window.spurn = window.spurn || function () { (window.spurn.q = window.spurn.q || []).push(arguments) }
spurn('conversion', { value: 49.9, currency: 'USD', orderId: 'order-1001' })
</script>
valueis in major units (49.9for $49.90). Leave it out for a lead with no value.orderIdshould be unique per conversion, so a reload doesn't count twice.- Only visitors who arrived on a paid click are reported. Everyone else is ignored.
Webflow Ecommerce shows the order on its /order-confirmation page, but Webflow doesn't document variables that put the order's id and total into custom code. To send real order values, read them in your own script from what the page shows, or send conversions from a server with /docs/install/server-api.
Check it works#
- Add your own IP address to the allowlist in Spurn (Blocking, then Allowlist), so your tests are never blocked.
- Open your published site with a test click id:
https://yoursite.com/?gclid=test-123. - Open Clicks in Spurn. The visit appears within a minute, and the site's Install tab shows Receiving.
A test landing counts as a real paid click and uses one credit. Test on the published domain, not the Designer preview.
Troubleshooting#
Nothing arrives. Check you published after saving, and that the test URL has a click id. Visits without one are ignored by design.
Clicks are rejected for the wrong site. Spurn checks the page reporting a click against your site's domain and extra hosts. If visitors also reach the site on yoursite.webflow.io or a second domain, add it in Sites, then your site.
The tag is blocked. If you set a Content Security Policy, allow script-src https://spurn.io and connect-src https://spurn.io. Ad blockers can stop the tag in your own browser; try a private window without extensions.
A consent banner holds the tag back. If your consent tool blocks scripts until the visitor accepts, Spurn waits too, and visitors who decline aren't checked. The tracking template still records the IP behind Google and Microsoft clicks: /docs/guides/tracking-template.
Wrong key. The tag takes the public key (sp_pub_…). A secret key (sp_sec_…) must never go in a page; if one did, revoke it in Sites, then your site, then Keys.
What data is sent#
On paid landings only: the landing URL and referrer, the IP address and user agent, browser signals used to spot automation, and engagement such as time on page and scrolling. Conversions send the value, currency and id you put in the snippet. See /docs/detection.