WordPress Lead-Capture Plugin
Drop-in WordPress plugin that auto-captures form submissions from TripGo, Tourfic, Elementor, Contact Form 7, and more.
The TravelBoost WordPress plugin is the bridge between your existing WordPress travel website and your TravelBoost account. Install it once and every form submission on your site — no matter which plugin built the form — lands in your TravelBoost leads pipeline within seconds, with the lead context preserved.
Overview
The plugin uses a 7-layer capture system to make sure it catches every form, regardless of which builder created it:
- WordPress core hooks — comments, registrations, contact submissions
- Major form plugins — Contact Form 7, WPForms, Gravity Forms, Forminator, Fluent Forms
- Page builders — Elementor Pro Forms, Divi forms, Bricks forms, Beaver Builder forms
- Travel-specific plugins — TripGo, WP Travel Engine, Tourfic, Travel Master, WP Travel
- Booking plugins — Bookly, Amelia, MotoPress Hotel Booking
- WooCommerce — orders are captured as leads with the cart context
- Custom forms — fall-back generic interceptor for hand-coded
<form>submissions
If your site uses something we don't natively support, the generic interceptor still catches it 95% of the time.
Installation
- Download the plugin ZIP
From your TravelBoost dashboard: Settings → Integrations → WordPress. The download includes your unique API key embedded.
- Install on WordPress
WordPress admin → Plugins → Add New → Upload → choose the ZIP → Install Now → Activate.
- Confirm the connection
A new menu item appears: TravelBoost. Open it — you should see "Connected" and your agency name. If not, paste your API key manually (it's also shown in the dashboard).
- Run a test submission
Submit any form on your website with test data. Within 10 seconds, the lead appears in your TravelBoost leads pipeline.
What gets captured
Every lead arrives with as much context as the form provided:
| Field | Source |
|---|---|
| Name, email, phone | Form fields (auto-mapped) |
| Subject / message | Form fields |
| Source page URL | The page the form was submitted from |
| Source page title | For categorising "Tour enquiry" vs. "Hajj enquiry" vs. "Generic contact" |
| UTM parameters | If present in the URL — feeds your marketing attribution |
| Referrer | Where the visitor came from |
| Visitor IP + country | For geo-segmentation (anonymised after first save) |
| Trip details | When using a travel-specific plugin: destination, dates, pax, package |
Mapping rules
The plugin auto-maps fields by name (email, phone, message, etc.). For travel plugins, it understands additional fields:
- TripGo / WP Travel — destination, departure date, return date, pax, package name
- Tourfic / Travel Master — tour name, traveller count, dates, options selected
- Bookly / Amelia — service, staff member, requested time slot
If your form has custom fields the plugin doesn't recognise, the dashboard's Field Mapping screen lets you manually map them to TravelBoost lead fields.
Real-time vs. queued sending
By default the plugin sends each submission immediately. If your TravelBoost API is briefly unreachable (deployment, maintenance), submissions queue locally in the WordPress database and retry every minute for up to 24 hours.
Security
- API key authentication on every request (rotate from the dashboard)
- HTTPS-only (the plugin refuses to send over HTTP)
- Rate limiting at the TravelBoost API to prevent abuse
- Honeypot fields detected and skipped (spam filtering)
FAQ
Does the plugin slow down my site?
No — it hooks into the submission event, not into page load. The submission to TravelBoost happens server-side, asynchronously, after the form response is already sent to the visitor.
Will it work with my custom theme?
Yes — the plugin doesn't render any frontend. It only listens to backend form events.
Can I capture only certain forms?
Yes — the Form filter page lists every form the plugin can see, with a checkbox to include or exclude each.
What if I run multiple WordPress sites?
Each site needs its own plugin install with its own API key (or you can share one key — but separate keys make per-site reporting easier).