RideDesk Widgets – Taxi, Transfer & Chauffeur Booking Forms

RideDesk Widgets connects your WordPress site to your RideDesk account. Drop a booking form, enquiry form or vehicle-rental form into any page or post — with live prices from your own rate card, address autocomplete, a route map, and 12 languages.

The forms are rendered by your RideDesk domain inside a responsive, auto-resizing frame. That means:

• No configuration drift — every improvement RideDesk ships appears on your site automatically. This plugin never needs an update for new form features.
• Your branding — colors, corner radius and behaviour are configured once in your RideDesk panel (Settings → Widgets) and apply everywhere.
• Real prices, safe payments — quotes are calculated server-side by RideDesk; optional online payment uses your own payment providers via RideDesk’s hosted payment page.

Requires a RideDesk account. The widgets are part of RideDesk’s Widgets add-on.

Contact Form 7 integration

Already using Contact Form 7? Enable the bridge under Settings → RideDesk Widgets and every successful CF7 submission is ALSO filed as an enquiry in your RideDesk panel — spam-classified, your team notified, matched to the customer’s booking history. Your existing forms and their emails stay exactly as they are. Conventional CF7 field names (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.

Usage

Add the RideDesk Widget block in the editor, or use shortcodes:

• [ridedesk_widget type="booking"]
• [ridedesk_widget type="enquiry"]
• [ridedesk_widget type="rental" lang="de" height="520"]

External services

This plugin embeds forms from your own RideDesk domain (e.g. yourcompany.ridedesk.app or your custom domain connected to RideDesk) inside an iframe.

Visitor attribution (on by default, Settings → RideDesk Widgets). When enabled, every page of your site loads one small script, https://<your-domain>/embed/attribution.js, from your own RideDesk domain. It records — in the browser’s sessionStorage, for the duration of the visit — the page the visitor arrived on, the referring website, any utm_source/utm_medium/utm_campaign parameters in the URL, the paths of the pages they view on your site, and a random id that groups those into one visit. That record is sent to your RideDesk account only when the visitor actually submits a booking or enquiry, so your bookings can tell you which campaign and which page produced them. It sets no cookies and collects nothing a visitor types — no names, emails, phone numbers or form contents. It loads on every page rather than only pages with a form because the arrival page is the thing being recorded. Switch it off in the plugin settings and no such request is made. RideDesk privacy policy

Apart from that script, no data is sent anywhere until a visitor interacts with the embedded form. Depending on your RideDesk configuration, the embedded form itself may load:

• RideDesk (form content, address suggestions, prices) — privacy policy
• OpenStreetMap map tiles — privacy policy
• OSRM (project-osrm.org) for route distance/duration
• Cloudflare Turnstile or Google reCAPTCHA for spam protection, if enabled in your RideDesk settings — Cloudflare privacy, Google privacy
• Google Places or Photon (komoot.io) address suggestions, depending on configuration

Server-side, the plugin only contacts your own RideDesk domain, and only when the optional Contact Form 7 bridge is enabled: successful CF7 submissions (the submitted name, email, phone, subject, message and the page URL) are forwarded to https://<your-domain>/api/enquiries so they appear in your RideDesk panel. With the bridge disabled, the plugin makes no server-side requests at all. Stored options: your RideDesk domain, a default language, the visitor-attribution toggle, and the Contact Form 7 bridge toggle and its key.