Skip to content
pixelary Docs

Webflow

Custom code

Add the script once in your site’s custom code and publish. Webflow forms and page views are tracked from the start.

Custom code needs a paid Webflow site plan.

1 Copy your script

In the Pixelary dashboard open Install and copy the script. It looks like this, with your own site key:

Head code
<script async src="https://cdn.pixelary.app/s/px_7hq2lm4x.js"></script>

2 Paste it into Head code

In Webflow open Site settings → Custom code, paste the script into Head code and click Save. Site-wide head code runs on every page, including CMS pages.

3 Publish

Publish to your domain and to *.webflow.io if you test there. Add both domains to the site in the dashboard. Once the site has its own domain, events from *.webflow.io go out in test mode only.

Webflow forms

With form tracking on in the dashboard, every Webflow form submission is sent as Lead. To track one form only, or to give it another event name, add a form trigger with that form’s selector instead.

Pixelary sends nothing a visitor has declined. In the EEA, the UK and Switzerland it waits for the visitor’s yes before any pixel loads or any event leaves the page.

Visitors from Europe need a consent banner

Without a banner, Pixelary never gets a yes from visitors in the EEA, the UK and Switzerland, so they are not tracked.

Webflow’s own consent setting only controls Webflow Analytics, so it is not a consent banner for Pixelary. Use one of the banners below.

Pixelary reads these on its own, with no extra setup:

  • Google Consent Mode v2
  • IAB TCF 2.2
  • Global Privacy Control
  • Cookiebot
  • OneTrust
  • CookieYes
  • Usercentrics
  • Complianz
  • iubenda
  • Termly
  • Osano
  • CookieFirst
  • Didomi (via TCF)
  • Framer cookie banner

Another banner can pass its answer with one line of code. Consent & banners

Something here doesn’t match what you see? Write to hello@pixelary.app.