For Webflow designers and teams

Webflow popups your client can change without touching the build

Popups, a countdown timer and an announcement bar, kept out of your interactions panel.

You can build a Webflow popup by hand with a div and an interaction, and for a single static modal that is fine. The trouble starts when marketing wants a different offer next week, a countdown timer for the launch, an announcement bar on pricing pages only, and to know which version did better. Tafsee Popup moves all of that out of the Designer: one snippet in site settings, and campaigns that a non-designer can edit, target and switch off.

Tafsee Popup

What you get

  • One snippet in site settings

    Footer code at site level covers every page, including CMS pages.

  • Open on click

    The "Click on element" rule opens a campaign from a button or link you already designed.

  • A/B tests with significance

    On Growth and above, split traffic between two versions and see when the winner is real.

  • 39 display rules

    Page URL, URL parameter, traffic source, country, device, JavaScript event and custom attribute.

  • Leads to your stack

    Mailchimp, Klaviyo, HubSpot, Zoho CRM, Google Sheets, Slack, Zapier, Make and webhooks.

  • About 34 KB gzipped

    One script for every campaign on the site, however many you publish.

A Webflow popup built by hand, or one managed outside the Designer

A hand-built modal gives you full control of the markup, and nothing here replaces that for a navigation overlay or a video lightbox. Marketing popups are a different problem, because the hard part is not drawing the box.

  • Who sees it. New visitors only, people from a paid campaign, visitors in one country, people who already signed up. Each of those is a rule in Tafsee Popup, and a pile of custom code otherwise.
  • How often. Frequency caps stop the same visitor meeting the popup on every page.
  • Where the form goes. Submissions are stored, delivered to your tools and retried on failure.
  • Who changes it. A client or a marketer edits the offer in the Tafsee editor. Nobody republishes the Webflow site for a headline change.
  • Whether it worked. A/B tests report when a difference is statistically significant. Our post on when an A/B test winner is real explains how to read them.

Installing on Webflow

The snippet goes in the site's settings, not in a page-level embed, so it covers every page.

  1. In Tafsee Popup, add the website and click Show install code.
  2. In Webflow, open Site settings, then Custom code.
  3. Paste the snippet into Footer code.
  4. Save and publish the site.
  5. Back in Tafsee Popup, click Check my site.

Two things trip people up. Custom code runs on the published site, not in the Webflow Designer preview, so open the published address to test. And saving the code is not enough: the site has to be published again before the script is live.

If the project already loads Google Tag Manager, you can add the snippet there as a Custom HTML tag on All Pages. The app keeps the same steps next to your install code, which is handy when you hand the site over.

Webflow countdown timer and announcement bar

Both are things a Webflow site tends to get as a one-off custom build, and both get stale the same way: the launch passes and the timer sits at zero until someone remembers to remove it.

  • Countdown timer. Add the countdown block to a bar or popup, set the end date and time, and add a date range rule so the campaign stops when the deadline passes. The timer alone does not stop it. Good for a launch, a webinar registration or the end of an annual-plan discount.
  • Announcement bar. A floating bar pinned to the top or bottom. Use the page URL rule to keep a pricing change on pricing pages and a product update on the product pages.
  • Inline version. An inline campaign renders inside an element you place. Drop Webflow's Embed element where the timer or form should sit and paste the one-line placeholder with the campaign's ID.

Seasonal versions are covered on the Black Friday page.

Controls a Webflow developer will want

The defaults need no code. When a project needs more, these are there.

  • Click on element. Open a campaign when a visitor clicks an element you choose, such as your own "Book a demo" button.
  • JavaScript event. Trigger a campaign from a custom event your site sends.
  • Custom attribute and cookie. Show or hide a campaign based on a value your site passes, or a cookie by name and value.
  • URL parameter and landing page. Match a campaign to the ad that sent the visitor.
  • Element comes into view. Open when the pricing table or the footer scrolls into view.
  • Tag Manager events. On a page with a data layer, the script reports when a campaign is seen and when someone signs up.

For lead forms on a SaaS or agency site, see lead generation popups. To pause a campaign after someone converts, use the "Already signed up" rule.

Plans for one site or a client roster

Plans are counted in websites, live campaigns and leads, never pageviews, which makes them easy to quote to a client.

  • Free: 1 website, 3 live campaigns, 500 leads a month, every template and display rule, with a small Tafsee badge.
  • Starter, $9 a month: 1 website, 10 live campaigns, no badge, 2 team seats.
  • Growth, $19 a month: 3 websites, A/B testing, 3 team seats.
  • Pro, $49 a month: 10 websites, unlimited live campaigns, HubSpot and Zoho CRM, 10 team seats.
  • Business, $99 a month: unlimited websites, campaigns, leads and seats.

Paid plans have a 14-day trial, and reaching a limit never switches live popups off. The Free plan delivers leads to Mailchimp, Klaviyo, Google Sheets, Slack and Zapier. Full details on pricing and integrations.

Limits worth knowing before you propose it

  • It is not a Webflow app and adds no elements to the Designer. Popups are styled in the Tafsee editor, not with your Webflow classes.
  • Nothing renders in the Designer preview. Test on the published address.
  • It needs Webflow's site-level custom code. If that setting is not available on a project, check the project's Webflow plan.
  • The "Adds to cart" rule recognises Salla, Zid, Shopify and WooCommerce buttons. For Webflow Ecommerce, send a dataLayer add_to_cart event or target the cart by URL.
  • If the site uses a Content-Security-Policy, the script's host has to be allowed.

Frequently asked questions


Copy the install code from Tafsee Popup, open Site settings then Custom code in Webflow, paste it into Footer code, save and publish the site. Then run the install check and publish a campaign.


Custom code runs on the published site, not in the Designer preview. Open the published address. If you saved the code but did not publish again, publish the site.


Add the countdown block to a campaign in Tafsee Popup, set the end date and time, and publish. It can show in a bar, in a popup, or in an inline campaign placed inside a Webflow Embed element. A date range rule stops it when the deadline passes.


Yes. The "Click on element" rule opens a campaign when a visitor clicks an element you choose, so your button keeps its Webflow styling.


Yes, within the plan's limits: Growth includes 3 websites and 3 team seats, Pro 10 websites and 10 seats, and Business is unlimited. Each website has its own install code and campaigns.


Yes. HubSpot and Zoho CRM are included from the Pro plan. On lower plans you can deliver to Mailchimp, Klaviyo, Google Sheets, Slack or Zapier. Every lead is stored in Tafsee first, with a delivery log and automatic retries.


Free plan · 14-day trial on paid plans

Try Tafsee Popup on your site today

Enter your website and the setup wizard drafts three on-brand popups for you. Pricing is never based on pageviews.

Lead Generation

Tafsee Popup

Popups, spin-to-win wheels, countdown bars and exit-intent offers for any website — in English and native Arabic.

⚡ Native Arabic, never priced by pageviewsBilingual supportFree plan · 14-day trial
+966 58 267 6110+966 58 267 6110