Messenger button
One floating button: WhatsApp, Telegram, call, chat — up to 12 channels
See example and features →Free
Set up this widgetWebflow · contact from your portfolio
Add contact options or appointments to your existing Webflow design. Choose a task and configure the widget in Meni.ge, then add code at site or page level. Find custom-code requirements and separate consent instructions below.
No card · a minute to sign up, another for the tag · settings reach your site in 5 minutes
Choose a widget and configure it in your dashboard. Standard widgets share a tag; consent and analytics require a separate installation order.
One floating button: WhatsApp, Telegram, call, chat — up to 12 channels
See example and features →Free
Set up this widgetBooking on your own schedule: the client picks the service, the specialist and a free slot
See example and features →Free
Set up this widgetLive chat with visitors — answered by your staff from the team chat
See example and features →Free
Set up this widgetA callback request form, with automatic calling through your connected phone system
See example and features →Free
Set up this widgetA “Call us” button — a conversation from your site through your own PBX, with no number or app for the visitor
See example and features →Free
Set up this widgetModals, slide-ins, bars, embedded forms, coupons and quizzes with display rules and A/B testing
See example and features →$9/mo
Set up this widgetNotices with order, booking, appointment and rating figures from your account
See example and features →Free
Set up this widgetA bubble with a clip from your menu in the corner of your site: tap for video with sound and an “Order” button
See example and features →Free
Set up this widgetA “Book a table” button → one form → a request in your Tables section
See example and features →$9/mo
Set up this widgetAn order button opens your storefront over your existing site
See example and features →Free
Set up this widgetA “?” button → a side panel with your articles, search and a “was this helpful” vote
See example and features →$19/mo
Set up this widgetPrivacy, terms, returns, cookies, delivery — built from your own data and embedded in your site
See example and features →$9/mo
Set up this widgetCookie consent with tracker auto-blocking and Google Consent Mode v2
See example and features →Free
Set up this widgetYour selected widget and platform are saved at registration. Next, configure the widget in the dashboard. Keep this Webflow guide open and return to the installation steps below after setup.
A paid platform plan is required
An active Site plan or a Core, Growth, Agency or Freelancer Workspace is required.
Webflow’s official guide allows Site managers and Designers to add custom code with an active Site plan or one of the listed Workspaces. A paid Site plan is not the only route.
A webflow.io address alone does not tell you whether custom code is available: check the Workspace, permissions and project settings. Custom domains and CMS features have their own plan requirements.
Menu names and plan requirements on this page come from the official help center:
Checked against the platform’s help center on 2026-09-22
Standard widgets: chat, contact button, appointments
<script src="https://cdn.meni.ge/site/v1.js" data-domain="your-site.com" async></script>Example tag for standard widgets. Use your own dashboard code, not this demonstration domain. To block analytics, follow the separate instructions below. Cookie consent and analytics: a separate installation order →
In your Meni.ge dashboard: Admin panel → Marketing → «My Website». Enter your site address in the first field and copy the tag.
In Webflow: Site settings for the project you need.
The Custom code tab has two fields: Head code (inside the head tag) and Footer code (before the closing body tag).
Paste the line into Head code and save. Do not add html, head or body tags around it — only the script itself.
Press Publish: the Webflow help center notes that custom code takes effect on the live site once published.
Open the published site and go back to «My Website» → «Check installation».
Need the widget on one page only — Webflow pages have their own custom code fields in page settings.
For strict opt-in, copy the dedicated consent tag from cookie banner settings and place it first in head, without async or defer, before analytics and advertising scripts. The shared async tag does not guarantee blocking before consent.
<script src="https://cdn.meni.ge/consent/v1.js" data-domain="your-site.com"></script>Check theme code, plugins, GTM and native platform integrations. If the platform cannot run consent before them, an external tag is not enough: configure consent in the integration itself.
In opt-in, known trackers are blocked; unknown scripts need manual markup following the CMP guide. The tag cannot stop code that has already run, server Set-Cookie headers or service workers.
On the published site, open a clean session and Network: before a choice and after rejection, check that trackers intended to be blocked make no requests. Then accept the relevant category, check loading and change the choice. A visible banner and the HTML installation check do not prove blocking.
In site builders your edit lives in a draft: until the pages are republished, the tag is not on the live site.
Admin panel → Marketing → «My Website». Put your site address in the first field and press «Check installation».
The check reads the page’s source HTML and lists the widgets it found. A tag injected through Google Tag Manager stays invisible to it — that is a limit of the check, not of the install.
Install errors and how to fix them — in the help center Installation guide →
Webflow supports custom code in preview/comment modes, but not expand canvas. Visitors see changes after publishing; make your final check on the published address.
Site Head code adds the tag across the site. For one URL, use page settings and avoid duplicating a tag already installed at site level.
The widget does not automatically connect Webflow forms to Meni.ge. Shadow DOM isolates styles, but test animations, button clicks and overlap on your own site.
Do not place consent after a container that has already started trackers. For a standard tag through GTM, the server-side HTML check cannot confirm installation; test the widget on the published page.
No. Webflow also permits custom code through Core, Growth, Agency or Freelancer Workspaces. Check Site manager/Designer permissions and access in your specific project.
Put the standard tag in Head code without html/head/body wrappers. Consent that blocks before a choice requires a separate first script in head before trackers.
Custom code does not run in expand canvas. Preview/comment supports it, but you still need to publish changes. Check widget enablement and the final site address.
Style isolation does not guarantee compatibility with every script. Test interactions, forms and mobile layout before using the widget across your site.
Site-wide code also covers collection pages. Check a published example and avoid duplicating the tag in its template.
To block trackers before consent, place a separate consent/v1.js first in head without async/defer. Test loading before a choice, after rejection and after acceptance. Native platform analytics may need separate configuration; a visible banner does not establish legal compliance.
More — installation per platform, settings and troubleshooting — in the help center. Installation guide →
Same widgets — different menu names.
Check custom-code access, choose a widget and configure it. After publishing, test a regular page and a collection page.
Choose a widgetNo card · a minute to sign up, another for the tag · settings reach your site in 5 minutes