外掛標籤
開發者團隊
原文外掛簡介
Add a professional online booking experience to your WordPress site in minutes. The Bookinda Booking Widget embeds your Bookinda booking flow natively, so visitors can book appointments without ever leaving your website.
Four ways to embed, no code required: a Gutenberg block, an Elementor widget, a Classic editor toolbar button, or the [bookinda] shortcode. Pick an inline iframe that sits right in your content, or a fullscreen lightbox that opens from a button.
The plugin is a lightweight client for the Bookinda SaaS booking platform (https://bookinda.hu). It loads your booking flow from your Bookinda subdomain ({slug}.bookinda.hu) and bridges its lifecycle events to your page as native DOM CustomEvents, so you can wire up your own analytics, CRM, or post-booking redirects.
You need an active Bookinda account to use this plugin. The plugin itself is free.
Perfect for
Salons, spas, barbershops, and beauty studios
Clinics, dentists, and medical practices
Personal trainers, coaches, and consultants
Any service business that takes appointments on a WordPress website
Features
Gutenberg block in the Widgets category with sidebar InspectorControls for every parameter.
Elementor widget with three tabs (Content, Preselection, Style) in the sidebar.
Classic editor (TinyMCE) toolbar button with a dialog that inserts the appropriate shortcode.
Shortcode [bookinda] / [bookinda mode="lightbox"] for any template, widget area, or content block.
Inline mode: the booking iframe is embedded directly in the content (auto-resize).
Lightbox mode: a button opens a fullscreen modal with the booking flow (mobile-optimized with sticky continue button, ESC and backdrop click to close).
Preselection: pass services, staff, category, promo, location parameters to pre-select fields in the booking flow.
Host DOM events: bookinda:complete, bookinda:error, bookinda:step, bookinda:resize CustomEvents dispatched on document for custom integrations.
Optional GA4 and Meta Pixel tracking: if the host page already loads gtag or fbq, the plugin can fire a purchase event on booking completion. Configured via plugin settings (off by default).
Where to find your tenant slug
Your tenant slug is the prefix of your Bookinda URL: https://YOUR-SLUG.bookinda.hu/manager/calendar. The slug is the part before .bookinda.hu.
External Services
This plugin connects to Bookinda (https://bookinda.hu), a third-party SaaS booking platform operated by Bookinda Kft. The connection is required for the plugin to function: the booking widget is hosted by Bookinda and embedded in your WordPress site via an iframe.
What is sent to Bookinda:
When a visitor opens a page containing the booking widget, their browser loads https://{your-tenant-slug}.bookinda.hu/embed/{your-tenant-slug} in an iframe. The URL includes the embed configuration parameters you set (mode, color, preselected service IDs, etc.) and an analytics-only source=wp-plugin parameter so Bookinda can distinguish WordPress plugin traffic from other embed sources.
When the visitor proceeds with a booking, they interact directly with the Bookinda iframe. Any data they enter (name, email, phone, payment details) is sent to Bookinda’s servers, not to your WordPress site. The plugin does not collect or store visitor data on the WordPress site.
What is received from Bookinda:
The booking widget HTML, CSS, and JavaScript, served from the Bookinda CDN.
postMessage events containing booking lifecycle data (completion confirmation, step changes, iframe height). The plugin re-broadcasts these as DOM CustomEvents on the host page.
Service documentation:
Bookinda website: https://bookinda.hu
Privacy Policy: https://bookinda.hu/adatkezeles
Cookie Policy: https://bookinda.hu/cookie-szabalyzat
Terms of Service: https://bookinda.hu/aszf
Data deletion request: https://bookinda.hu/adatok-torlese
By installing and activating this plugin you acknowledge that visitor interactions with the embedded widget are subject to Bookinda’s Privacy Policy and Terms of Service. Please review them and ensure your site’s privacy notice reflects the data flow described above.
