Title: CoverManager T Reservation Widget Author: covermanager Published: September 30, 2026 Last modified: September 30, 2026 --- Search plugins ![](https://ps.w.org/covermanager-widget-integration/assets/banner-772x250.png?rev =3720551) ![](https://ps.w.org/covermanager-widget-integration/assets/icon-256x256.png?rev =3720551) # CoverManager T Reservation Widget By [covermanager](https://profiles.wordpress.org/covermanager/) [Download](https://downloads.wordpress.org/plugin/covermanager-widget-integration.1.0.0.zip) * [Details](https://wordpress.org/plugins/covermanager-widget-integration/#description) * [Reviews](https://wordpress.org/plugins/covermanager-widget-integration/#reviews) * [Installation](https://wordpress.org/plugins/covermanager-widget-integration/#installation) * [Development](https://wordpress.org/plugins/covermanager-widget-integration/#developers) [Support](https://wordpress.org/support/plugin/covermanager-widget-integration/) ## Description **This plugin is for restaurants on CoverManager T.** If your restaurant is on CoverManager K, use the [CoverManager](https://wordpress.org/plugins/covermanager/) plugin instead — this one will not load your reservation widget. Not sure which platform your account is on? Your CoverManager contact can tell you. This plugin is published and maintained by CoverManager. This plugin allows you to integrate your restaurant’s CoverManager reservation widget directly on all pages of your website, allowing your customers to take reservations directly without having to switch page. You can also customize the integration according to your needs. ### Usage #### Default (global) widget Once your restaurant’s ID is set, the widget is added automatically to every page of your website, with a floating booking button positioned according to the settings. #### Shortcode You can also place the widget inline on a specific page or post using the `[covermanager_widget]` shortcode. With no attributes, it uses the same settings as the global widget: ``` [covermanager_widget] ``` You can override any of the settings per-page (useful for sites managing several restaurants): ``` [covermanager_widget restaurant_id="367219" open_delay="0" position="center"] ``` All of the settings from the admin page can be overridden as shortcode attributes: ``` [covermanager_widget restaurant_id="367219" language="fr" primary_color="#cc0000" hide_button="1" auto_open="0" disable_gtm="1" disable_ga4="1"] ``` When the shortcode is used on a page, the floating global widget is not also injected, so there is never a duplicate. **Tip for the Gutenberg editor**: Insert the shortcode using a _Shortcode_ block( Add Block / Shortcode), not a Paragraph block — Paragraph blocks can auto-format quotes and break the attributes. The widget only renders on the front-end of your site; Gutenberg does not preview shortcodes inside the editor. ### Support For plugin support, please visit the [support center](https://www.covermanager.com/en/contact). ### Privacy policy Our reservation widget plugin relies on the CoverManager service to enable restaurants to manage table reservations directly from their website. It requires a subscription to CoverManager. #### Purpose The CoverManager service is integrated into our plugin to provide a reservation widget on the restaurant’s website, allowing customers to reserve tables online seamlessly. #### Data Transmission User data is transmitted to CoverManager when a customer makes a reservation or updates their reservation details through the widget. #### What is stored on the visitor’s device The plugin itself sets no cookies and uses no local storage. However, it loads the CoverManager SDK from https://sdk.covermanager.com/v1/sdk.min.js, which embeds the booking widget in an iframe served from bookings.covermanager.com. That iframe writes to the visitor’s device as soon as the page loads, before the visitor interacts with the widget: * `aws-waf-token` (cookie) – distinguishes visitors from automated traffic * `awswaf_session_storage`, `awswaf_token_refresh_timestamp` (local storage) – distinguishes visitors from automated traffic * `unleash:repository:sessionId`, `unleash:repository:repo` (local storage) – keeps feature rollouts consistent across visits * `bugsnag-anonymous-id` (local storage) – groups error reports from the same device Note that local storage counts as storage on terminal equipment under ePrivacy Article 5(3) (and §25 TDDDG in Germany), just as cookies do. The rest is written only once the visitor does something: * `formDataFromCookies` (cookie) – written when the guest ticks “Save the information for my next reservations” and books. Holds their name, email, phone, country and postcode so the form can be pre-filled next time. Cleared when the browser closes, and deleted if the box is unticked. * `zc_popup_*` (local storage, on your own domain) – written when the visitor dismisses a widget popup, so it is not shown again for 14 days. * `adyen-checkout__checkout-attempt-id` (local storage) – written at a payment step, at restaurants that take payment through Adyen. * `__stripe_mid`, `__stripe_sid` (cookies) – written at a payment step, at restaurants that take payment through Stripe. If your restaurant takes prepayments or card imprints, the payment step also loads your payment provider’s own scripts, and Adyen’s checkout includes a Google Pay button loaded from pay.google.com. That does not happen anywhere else in the flow. Your own analytics are separate. If you enter a Google Analytics, Google Tag Manager or Meta Pixel ID under Guest analytics in CoverManager, those load inside the widget too, using your own tracking properties, and set their usual cookies (`_ga`, `_fbp`, and so on). The plugin cannot tell whether you have configured them, so it does not declare them to your consent plugin – treat them the same way you treat the analytics on the rest of your site. Depending on your jurisdiction and how you use the widget, you may need to obtain the visitor’s consent before this happens. The plugin is built to make that possible: * The SDK is loaded by its real URL, so consent platforms that block third-party scripts by URL can detect and block it without any configuration from us. * The plugin registers with the WP Consent API (https://wordpress.org/plugins/wp- consent-api/) and declares the storage above, so compatible consent plugins can list it accurately. * The filters documented under Hooks let you suppress loading or add whatever attributes your consent banner blocks on. Because the SDK is an external script, WordPress also emits a `dns-prefetch` hint for sdk.covermanager.com. That resolves the domain ahead of time but transfers no data and stores nothing on the visitor’s device. It is removed automatically when` covermanager_widget_should_load` returns false; note that it is _not_ removed when a consent platform blocks the script by URL, since the hint is a separate element the platform does not touch. This is a matter for your own legal assessment; the above is a description of the plugin’s behaviour, not legal advice. #### Hooks * `covermanager_widget_should_load` (bool) – return false to suppress the SDK, the widget configuration element and the DNS prefetch hint entirely, for instance until consent has been given. * `covermanager_widget_script_attributes` (array) – attributes of the SDK script tag. Add whatever your consent banner blocks on. Passed $attributes, $handle, $src. The `id` attribute is re-applied afterwards and cannot be changed – the SDK locates its own script element by that id and will not start without it. * `covermanager_widget_consent_category` (string) – the WP Consent API category the widget’s non-essential storage is declared under. Defaults to `statistics`. Suppress the widget until your own code decides otherwise: ``` add_filter( 'covermanager_widget_should_load', function () { return my_visitor_has_consented(); } ); ``` Mark the script for a banner that blocks by attribute: ``` add_filter( 'covermanager_widget_script_attributes', function ( $attributes ) { $attributes['type'] = 'text/plain'; $attributes['data-cookieconsent'] = 'statistics'; return $attributes; } ); ``` #### Read more * [CoverManager](https://www.covermanager.com/). * [Legal Notice](https://www.covermanager.com/en/legal-notice) * [Privacy policy](https://www.covermanager.com/en/privacy-policy) ## Screenshots [⌊The CoverManager widget displayed on your website.⌉⌊The CoverManager widget displayed on your website.⌉[ The CoverManager widget displayed on your website. [⌊The CoverManager widget settings page.⌉⌊The CoverManager widget settings page.⌉[ The CoverManager widget settings page. ## Installation 1. Upload the plugin to your WordPress plugins directory, or install the plugin through your website dashboard, under _Plugins / Add new_ page. 2. Activate the plugin through your website dashboard, under _Plugins_. 3. Set your restaurant’s ID on the new settings page that have been added to your dashboard, under _Settings / CoverManager widget_. ## FAQ ### Where can I find my restaurant’s ID? Your restaurant’s ID is the number displayed on the top of your [CoverManager dashboard](https://appv2.covermanager.com/). ### Can I have two booking-widget plugins active at once? No. Each booking-widget plugin adds its own widget configuration to the page, so with two of them active a visitor can get a duplicated widget or the wrong restaurant— the plugins cannot see each other’s configuration. If you are switching from another one of our widget plugins, deactivate it before activating this one. ### How can I open the booking widget from a custom button (Elementor, Gutenberg, Divi…)? As long as the plugin is active and a restaurant ID is set, you can trigger the booking widget from any clickable element on your page. The CoverManager SDK natively supports three ways to do this: 1. **Add a data attribute to any button or link:** 2. Book a table 3. This works with HTML widgets in Elementor, custom HTML blocks in Gutenberg, or anywhere you can edit raw HTML. 4. **Use a hash-based link** (useful when the page builder only lets you set an URL): 5. [Book a table](https://wordpress.org/plugins/covermanager-widget-integration/?output_format=md#zc-action-open) 6. **Call the JavaScript API** from your own scripts: 7. ZcWidget.open() — opens the widget ZcWidget.close() — closes it ZcWidget.toggle()— toggles it ## Reviews There are no reviews for this plugin. ## Contributors & Developers “CoverManager T Reservation Widget” is open source software. The following people have contributed to this plugin. Contributors * [ covermanager ](https://profiles.wordpress.org/covermanager/) [Translate “CoverManager T Reservation Widget” into your language.](https://translate.wordpress.org/projects/wp-plugins/covermanager-widget-integration) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/covermanager-widget-integration/), check out the [SVN repository](https://plugins.svn.wordpress.org/covermanager-widget-integration/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/covermanager-widget-integration/) by [RSS](https://plugins.trac.wordpress.org/log/covermanager-widget-integration/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.0 * Initial release. ## Meta * Version **1.0.0** * Last updated **12 hours ago** * Active installations **Fewer than 10** * WordPress version ** 4.6 or higher ** * Tested up to **7.1.2** * PHP version ** 7.4 or higher ** * Tags * [food](https://wordpress.org/plugins/tags/food/)[reservation](https://wordpress.org/plugins/tags/reservation/) [restaurant](https://wordpress.org/plugins/tags/restaurant/) * [Advanced View](https://wordpress.org/plugins/covermanager-widget-integration/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/covermanager-widget-integration/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/covermanager-widget-integration/reviews/) ## Contributors * [ covermanager ](https://profiles.wordpress.org/covermanager/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/covermanager-widget-integration/)