Skip to content
pixelary Docs

Framer

Plugin Custom code

The Pixelary plugin installs the script on your Framer site and keeps it up to date. Pixels, triggers and consent are set in the dashboard, so you change them without republishing.

1 Add the plugin

In Framer open the Pixelary plugin in the Marketplace and add it to your project. Run it from the Plugins menu.

2 Sign in and connect the project

Sign in with Google or an email code. The plugin finds the Pixelary site for this Framer project, or creates one, and shows its site key.

3 Install the script and publish

Click Install script, then publish the site. The plugin watches the publish and shows when the script is live. After that, changes in the dashboard reach the site within about five minutes, without another publish.

What is tracked on a Framer site

  • Page views, including navigation between pages and CMS items.
  • Framer form submissions, as Lead, with form tracking on. Email and phone fields are hashed in the browser.
  • Clicks and pages you choose in the dashboard under Triggers.
  • Calendly, Cal.com, Typeform, Tally and HubSpot embeds, with a booking trigger.

Events from your *.framer.app address go out in test mode only once the site has its own domain, so previews stay out of your ad reports.

Without the plugin

In Framer open Site Settings → General → Custom Code, paste the script into End of <head> tag and publish. Copy your own site key from the dashboard.

End of <head> tag 
<script async src="https://cdn.pixelary.app/s/px_7hq2lm4x.js"></script>

Use one method, not both. If both run, Pixelary starts once and the second copy does nothing.

Already on the old plugin

Your current script keeps working. Your sites, pixels and tokens are already in the dashboard under the same login. Update the script from the plugin when you are ready, then publish: from then on pixel and tracking changes no longer need a publish, and the event log starts.

Custom events from the old plugin

Code overrides created by the old plugin (data-ft-event) keep firing with the new script. New click events are easier to manage as triggers in the dashboard.

Everything that changed for Framer sites

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.

Framer’s own cookie banner (Insert → Cookie Banner) works: Pixelary reads the visitor’s answer from it directly.

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

Previous HTML snippet Next Google Tag Manager

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