PosLimitless Booking integrates PosLimitless booking modules directly into your WordPress site.<\/p>\n\n
Included modules:<\/strong><\/p>\n\n Features:<\/strong><\/p>\n\n This plugin relies on the following third-party and external services:<\/p>\n\n This plugin connects to the PosLimitless API to manage bookings, payments, gift cards, client accounts and events. All booking data (customer name, email, phone, reservation details, payment information) is sent to this service when a visitor makes a reservation, purchases a gift card or accesses the client portal.<\/p>\n\n When a center has configured Google tracking tags in PosLimitless, this plugin only<\/strong> loads Google scripts after the visitor has explicitly opted in via the cookie consent checkbox displayed on the confirmation page. No Google scripts are loaded and no data is sent to Google until the visitor grants consent. Once consent is granted, the plugin sends page views and purchase conversion events (transaction ID, amount, currency) to Google for analytics and advertising purposes. Google Consent Mode V2 is used with all storage types denied by default.<\/p>\n\n When a center has configured a Meta Pixel ID in PosLimitless, this plugin only<\/strong> loads the Meta Pixel script after the visitor has explicitly opted in via the cookie consent checkbox displayed on the confirmation page. No Meta scripts are loaded and no data is sent to Meta until the visitor grants consent. Once consent is granted, it sends page views and purchase conversion events (amount, currency) to Meta for advertising purposes.<\/p>\n\n When a center has configured a TikTok Pixel ID in PosLimitless, this plugin only<\/strong> loads the TikTok Pixel script after the visitor has explicitly opted in via the cookie consent checkbox displayed on the confirmation page. No TikTok scripts are loaded and no data is sent to TikTok until the visitor grants consent. Once consent is granted, it sends page views and payment completion events (amount, currency) to TikTok for advertising purposes.<\/p>\n\n When a center uses Stripe as a payment gateway, payment is processed via the Stripe hosted checkout. The customer is redirected to Stripe to complete payment. No card data is handled by this plugin.<\/p>\n\n The frontend module ( Log in to POS Limitless (poslimitless.web.app), go to Configuration > API Keys. You will find your Center ID there and can generate your API Key.<\/p><\/dd>\n Each module has its own appearance page in the PosLimitless menu. You can choose from 5 visual styles and customize all colors.<\/p><\/dd>\n Stripe, Monetico, Sogecommerce and CAWL. Configuration is done in POS Limitless.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
\n
Shortcodes<\/h3>\n\n
\n
[poslimitless_booking]<\/code> \u2014 Booking module<\/li>\n[poslimitless_espace_client]<\/code> \u2014 Client portal<\/li>\n[poslimitless_bon_cadeau]<\/code> \u2014 Gift cards<\/li>\n[poslimitless_verif_bon_cadeau]<\/code> \u2014 Gift card balance check<\/li>\n[poslimitless_event]<\/code> \u2014 Events<\/li>\n<\/ul>\n\nExternal services<\/h3>\n\n
PosLimitless API<\/h4>\n\n
\n
Google Tag Manager \/ Google Analytics \/ Google Ads<\/h4>\n\n
\n
Meta Pixel (Facebook)<\/h4>\n\n
\n
TikTok Pixel<\/h4>\n\n
\n
Stripe<\/h4>\n\n
\n
Source code<\/h3>\n\n
assets\/booking.js<\/code>) is built from a React\/TypeScript application using Vite. The source code is included in the src\/<\/code> directory of this plugin. Build tools used: Node.js, Vite, TypeScript, React.<\/p>\n\n\n\n
poslimitless-booking<\/code> folder to \/wp-content\/plugins\/<\/code><\/li>\n\n
Where can I find my Center ID and API Key?<\/h3><\/dt>\n
How do I customize the appearance?<\/h3><\/dt>\n
Which payment methods are supported?<\/h3><\/dt>\n
2.5.0<\/h4>\n\n
\n
purchase<\/code> event was pushed to the dataLayer and no conversion was sent. The widget now detects success URL params (session_id<\/code> for Stripe, ref<\/code> for CAWL\/Monetico\/Sogecommerce) and switches to the success step on mount.<\/li>\nsitewebmercibon<\/code> field on the center, falls back to sitewebmerci<\/code> if empty), aligned with the existing booking flow. The redirect waits for Meta \/ TikTok \/ Google Ads pixel network requests to actually fire (PerformanceObserver, 5s safety timeout) before navigating away, so pixel\/server deduplication is preserved.<\/li>\n<\/ul>\n\n2.4.9<\/h4>\n\n
\n
assets\/tracking-loader.js<\/code>) instead of inline. Pixel IDs are passed via data-*<\/code> attributes on the <script src><\/code> tag. This bypasses Consent Management Platforms (Complianz, CookieYes, Cookiebot, Borlabs Cookie, etc.) that scan inline script content for tracker references and rewrite them to type=\"text\/plain\"<\/code> \u2014 even when the documented bypass attributes are set. External scripts served from the plugin's own domain are not matched against the CMPs' third-party tracker URL lists.<\/li>\nrocket_delay_js_exclusions<\/code>) for the tracking loader, so the pixel fires immediately on page load instead of waiting for first user interaction. Cloudflare Rocket Loader is also disabled for this script via data-cfasync=\"false\"<\/code>.<\/li>\n<\/ul>\n\n2.4.8<\/h4>\n\n
\n
echo<\/code> in wp_head<\/code> instead of through wp_add_inline_script<\/code>, and wrapped in the official Complianz <!--cmplz-native--><\/code> HTML markers. The previous v2.4.7 attempt to inject CMP bypass attributes via the script_loader_tag<\/code> filter did not work because that filter is only applied to scripts with a src<\/code> attribute, never to inline scripts. As a result, Complianz (and other CMPs) kept neutralizing the tracking script with type=\"text\/plain\"<\/code> even after upgrading.<\/li>\n<\/ul>\n\n2.4.7<\/h4>\n\n
\n
type<\/code> to text\/plain<\/code>, neutralizing it before execution \u2014 even after the visitor accepted cookies, since the script was wrongly classified under \"marketing\". Site owners who want consent-gated tracking can still classify the script manually in their CMP settings.<\/li>\n<\/ul>\n\n2.4.6<\/h4>\n\n
\n
has_shortcode($post->post_content)<\/code>, which silently failed when the booking widget was embedded via a page builder (Elementor, Bricks, Divi, Gutenberg blocks, custom theme template\u2026). Result: zero browser-side pixel events on most modern WP setups. Tracking now loads as long as a center ID is configured in the plugin settings.<\/li>\n<\/ul>\n\n2.4.5<\/h4>\n\n
\n
cookie_consent=granted<\/code> localStorage key.<\/li>\n2.4.4<\/h4>\n\n
\n
2.4.3<\/h4>\n\n
\n
2.4.2<\/h4>\n\n
\n
2.4.1<\/h4>\n\n
\n
2.4.0<\/h4>\n\n
\n
2.3.9<\/h4>\n\n
\n
2.3.7<\/h4>\n\n
\n
2.3.6<\/h4>\n\n
\n
2.3.5<\/h4>\n\n
\n
2.3.4<\/h4>\n\n
\n
2.3.3<\/h4>\n\n
\n
2.3.2<\/h4>\n\n
\n
2.3.1<\/h4>\n\n
\n
2.2.0<\/h4>\n\n
\n
2.0.0<\/h4>\n\n
\n