| 开发者 | ridedesk |
|---|---|
| 更新时间 | 2026年9月8日 19:45 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
your-name, your-email, your-tel, your-subject, your-message) are mapped automatically; developers can remap custom forms via the ridedesk_widgets_cf7_payload filter.
Knowing which advert produced the booking
A form inside a frame can only see the page it sits on, not the campaign that brought the visitor to your site three pages earlier. RideDesk Widgets closes that gap: an optional script records the arrival page, the referring site and any UTM tags for the length of the visit, and hands them to the form when the visitor actually books. Each booking then tells you which campaign and which landing page produced it.
It sets no cookies, stores nothing a visitor types, and keeps what it does record in the browser's own sessionStorage until the tab closes. Untick one box to turn it off entirely.
Usage
Add the RideDesk Widget block in the editor, or use shortcodes anywhere shortcodes work, including page builders:
[ridedesk_widget type="booking"][ridedesk_widget type="enquiry"][ridedesk_widget type="rental" lang="de" height="520"]Yes. The widgets render your organisation's live booking forms, prices and vehicles from your RideDesk panel, so there is nothing for them to show without one. The plugin is the connector, not the booking system.
No. The plugin needs no API keys of any kind, and there is no key field to fill in. Address suggestions and route distances are served through your RideDesk account, which falls back to open data (Photon, OpenStreetMap and OSRM) when no commercial provider is configured. There is no Google Cloud project to create and no map billing to watch.
Yes. Set four colours, a corner radius and light or dark once in your RideDesk panel and every embed follows, on every site. There is no CSS to write and no theme compatibility layer to break. The frame is transparent by default, so it sits on your own page background.
Yes. There is a block for the editor and a shortcode for everything else, so anywhere that renders shortcodes will render the widget, including Elementor, Beaver Builder, Divi and classic widget areas.
It does not need WooCommerce and does not use it. Bookings, quotes and invoices live in RideDesk, and online payment goes through RideDesk's hosted payment page on your own Stripe, PayPal, SumUp or Mollie account. If you already run WooCommerce for something else, the two simply coexist.
Yes. Each frame measures and resizes itself independently, so a booking form and an enquiry form can sit on the same page without fighting over height.
Twelve: English, German, Spanish, French, Italian, Dutch, Portuguese, Russian, Polish, Turkish, Swedish and Norwegian. Pin one per shortcode with lang="de", or leave it and let the visitor choose.
The embedded forms stop appearing and nothing else changes. Your bookings, customers and settings live in RideDesk and are untouched. If you delete the plugin, it removes the handful of options it stored and leaves no tables or orphaned rows behind.
Check that your RideDesk domain is set under Settings → RideDesk Widgets, and that the Widgets add-on is active in your RideDesk plan. If your site enforces a strict Content Security Policy, allow frames from your RideDesk domain.
Yes, with Visitor attribution left on (Settings → RideDesk Widgets). The booking form runs inside a frame, and a frame can only see the page it sits on — not the Google or Facebook campaign that brought the visitor to your site three pages earlier. The attribution script captures that on arrival and hands it to the form, so each booking in your RideDesk panel shows the campaign, the page the visitor landed on and the pages they read on the way.
No cookies, and nothing a visitor types. It keeps page paths, the referring site and campaign tags in the browser's own sessionStorage, and they are discarded when the visitor closes the tab. If you would rather not run it, untick it in the plugin settings.
Please report it privately by email to hello@ridedesk.app rather than in the public support forum, and give us a way to reach you for follow-up questions. We will confirm receipt and tell you when a fix ships.