Callback
A callback request form, with automatic calling through your connected phone system
See example and features →Free
Set up this widgetTilda · enquiries from your landing page
Add callback, a messenger button or appointments alongside your Tilda blocks. Choose a task, configure the widget and paste the code into the project HEAD field. Republish the pages afterwards. Consent and analytics have a separate installation order 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.
A callback request form, with automatic calling through your connected phone system
See example and features →Free
Set up this widgetOne 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 “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 Tilda guide open and return to the installation steps below after setup.
A paid platform plan is required
For third-party HTML code, plan for Personal or Business; do not rely on Free.
Tilda lists custom code among Personal features; Business includes Personal features. Its nonpayment guide explicitly says code in T123/T868 blocks is disabled when switching to Free.
A HEAD help article that omits plan restrictions does not prove free access. Before paying, check the code field in your project and Tilda’s current plan table. Meni.ge widget pricing is separate.
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 the project list press «Site settings» for the site you need — project-wide settings, not a single page.
The «More» section (in some accounts it is labelled «Insert Code») → the «HTML code for the HEAD section» field. Both names appear in Tilda’s own help pages.
Paste the line into the field and save. The code goes into the head of every page of the project.
The Tilda help center says it plainly: republish all pages after adding code. Until then the tag lives only in the editor.
Open the live site and go back to «My Website» → «Check installation».
Need the tag on a single page only — Page settings → Additional → «HTML code for the HEAD section», then republish that page.
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 →
After editing project-wide HEAD code, republish all relevant pages. Check the published website address, not the editor.
Adding the tag does not change where existing forms send submissions. Connecting a form to Meni.ge needs separate configuration and testing; start with an enquiry through the widget itself.
Check that the widget does not cover a purchase button, a native contact button or a banner. Mobile screens have less room; keep only what you need.
The server-side installation check cannot see a dynamic GTM tag. Test standard widgets on the published page; consent must run before analytics, including Tilda integrations.
Do not rely on it for third-party code: Tilda lists custom code in Personal, and T123/T868 code is disabled when switching to Free. Check the plan capabilities in your project first.
Yes: Page settings → Additional → HTML code for the HEAD section. Publish that page and test the selected widget.
For a standard widget on one page, if your plan supports third-party code. For consent that blocks before a choice, T123 does not replace the first script in head before trackers.
Code access in your plan, publication of the relevant pages, widget enablement and the dashboard domain. Test on a phone and without browser extensions.
Forms keep their existing settings. Shadow DOM isolates widget styles, but you still need to check button placement and block behavior on your site.
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.
Choose a landing-page task and configure the widget. After adding the code, republish the pages and send a test enquiry.
Choose a widgetNo card · a minute to sign up, another for the tag · settings reach your site in 5 minutes