Home / Blog / Webflow and Framer Popups
Targeted popups on Webflow and Framer: no custom JavaScript
Both Webflow and Framer let you paste a third-party snippet in a site-wide code panel, which is all a hosted popup tool needs. You do not write JavaScript: you paste one deferred script, then configure the triggers, pages and audience in the tool itself. The work is in three places: finding the right panel, deciding whether the script goes site-wide or on one page, and testing that it loads after the page rather than before it.
Key takeaway: paste the deferred snippet in the site-wide custom code panel, keep triggers in the tool rather than in the site, and test the published domain on a real phone. Never edit the exported code by hand: the next publish overwrites it.
The short answer
- Where the snippet goes: the custom code panel of the project, in the body or before the closing body tag, so it loads on every page.
- What you configure elsewhere: triggers, page rules, audience and frequency caps live in the popup tool, not in Webflow or Framer. That is the point of the no-code path: changing a rule never requires a site publish.
- What to watch: a snippet pasted twice, a script that blocks rendering, and a published domain that behaves differently from the preview.
Webflow: two places, one choice
Webflow exposes custom code at the project level and at the page level. Pick one:
- Project-level custom code. Add the snippet once in the project settings, in the body section. It applies to every page and survives new pages, which is what you want for a popup that should run site-wide.
- Page-level custom code. Add the snippet to one page only. Useful for a test, or for a landing page built for a single campaign, but it means remembering to add it to the next page you build.
The trap with Webflow is duplication. A snippet in the project settings and another in a page inside the same project produces two initialisations, which usually shows up as a popup that appears twice or a widget that ignores its frequency cap. If the popup misbehaves, search the project for the snippet before you debug the campaign.
Framer: site-wide, and mind the publish step
Framer keeps custom code in the site settings, with an option to limit it to a single page. Two differences matter in practice:
- The preview is not the site. Custom code behaves differently in the editor preview than on the published domain, because the preview runs inside the editor's own frame. Always test on the published URL.
- Publishing replaces the build. Anything you edited by hand in an exported package disappears the next time you publish from Framer. Keep every rule in the popup tool, and treat the site as a consumer of the script, not as a place to store logic.
Which triggers work without code
| Trigger | What it needs from the site | Notes |
|---|---|---|
| Time on page | Nothing beyond the snippet | The simplest trigger to test first, and the one most often set too short |
| Scroll depth | Nothing | Works on long pages; set a high threshold on editorial pages |
| Exit intent | Nothing on desktop | Not a cursor event on phones: see the mobile notes below |
| Click on an element | A stable selector or element id on the page | The only trigger that needs attention in the site itself, because a redesign can change the selector |
| Page URL rules | The final URL pattern | Configured entirely in the tool, with no site change when you add a page |
Click triggers are the fragile one. If the popup is attached to a button that a designer later renames, the trigger silently stops matching. Prefer page rules and time or scroll triggers unless you specifically need a click.
Keep the script out of the critical path
A popup tool is not part of the first screen, so its script must not block rendering. Two habits make that true in both builders:
- Use the deferred version of the snippet. If the tool gives you a script with
deferorasync, keep it. Removing the attribute to "make sure it loads" moves the cost into the largest contentful paint. - Measure on the published page. Run PageSpeed Insights on a real URL before and after installing. Our Core Web Vitals guide explains which metric each mistake damages, and what a normal cost looks like.
Test in the right order
- One page, one trigger. Publish, open the page in a private window, and confirm the popup appears once.
- A second visit. Reload. The frequency cap should hold, and the popup should not appear again in the same session.
- A second page. Confirm the site-wide install works where you expected, and nowhere you did not.
- A real phone. Check the close control is reachable with a thumb and that the popup does not cover the main content on load. Our guide to exit intent on mobile covers the signals that make a delayed popup feel earned.
- A form submission. Send a test lead and confirm it arrives in the tool with the page URL and the consent state you configured.
Where no-code stops
No-code covers installation, targeting and design. It does not cover three cases: a single-page app that never reloads, a site with a strict content security policy that blocks third-party scripts, and a campaign that must read data your site keeps in memory. In those cases you need a developer, and the honest move is to say so before promising a no-code setup. If you run several client sites, our multi-site widgets guide covers the workflow that keeps each install separate.
Honest limits
The builder owns the markup, so you do not own the script order. When Webflow or Framer changes how custom code is injected, an install that worked can fail without any change on your side. Keep a written record of the snippet location and the date, test the published site after each major platform update, and do not stack two popup tools on the same project: they compete for the same triggers and neither frequency cap is reliable.
One snippet, both builders.
GrowthTools publishes a deferred script you paste once in Webflow or Framer, then manage triggers, pages and caps from the dashboard.
Create your free accountQuestions
No for a hosted popup. Both builders expose a site-wide custom code panel, and the snippet is a single deferred script. You do need a developer for a content security policy that blocks third-party scripts, for a single-page app that never reloads, or for a campaign that must read data your site holds in memory.
Almost always a duplicated snippet: one in the project settings and one in a page inside the same project, or an old embed left in a symbol. Search the project for the script URL, remove the duplicate, and republish. A duplicated tool initialisation also breaks frequency caps, so the popup can ignore its once-per-session rule.
Not if it is deferred and only injects a button or a modal after load. Measure with PageSpeed Insights on the published domain before and after installing, and watch interaction to next paint rather than only the headline score. A heavy embed with its own fonts and images is what costs performance, not the trigger logic.
Yes. Install the snippet once, site-wide, and create page rules in the popup tool using URL patterns. That way a new page is covered by a rule rather than by another paste, and the campaign stays editable without republishing the site.
Install a popup on your Webflow or Framer site.
Create a free account, paste the snippet in the site-wide code panel, and test one trigger before adding a second.
Create your free accountPublisher: GrowthTools by Seinsights. Product demonstrations are illustrative; results depend on your site and campaign.
Create your free account