A tour page can attract readers and still lose the booking moment. They read your itinerary, open five tabs, then book somewhere else.
A Travelpayouts widget gives readers a direct route from your content to a connected travel partner. You don’t need to build a booking engine. You need the right program, the right widget code, and a clean test process.
Start by matching the widget to the page and the visitor intent.
CHECK WHETHER A TOUR WIDGET IS AVAILABLE
Travelpayouts tools are tied to individual affiliate programs. A program must be connected before its available tools appear in your account.
That means a tour or activities partner may offer a widget, a text link, both, or neither. Don’t assume every connected brand has the same options. Travelpayouts explains this in its widget setup guidance.
Confirm the program and destination
Open the affiliate program you plan to promote. Look for its tools area and check whether it offers a widget for tours, activities, attraction tickets, or experiences.
Read the program rules before publishing anything. Check the accepted traffic sources, booking conditions, and attribution terms. A widget can load correctly while the underlying program is not a fit for your traffic.
Your page should also match the offer:
- Put a city activities widget on a city guide, not a broad home page.
- Use a destination-focused search or booking tool after readers have chosen a place.
- Keep a relevant text link available if no suitable widget exists.
A Travelpayouts booking tool usually sends the visitor to a partner booking flow. Don’t describe it as an on-site checkout unless the actual tool and partner terms support that claim.
Set one measurable goal
Decide what the placement needs to do before you add it. Most sites want one of three outcomes: more searches, more outbound clicks, or more approved affiliate earnings.
A page about “best museums in Paris” can place a relevant activity option after the museum recommendations. A generic banner at the top of that page usually gets weaker intent.
A widget placement is only useful when the page topic, destination, and booking option point to the same decision.
CREATE YOUR TOUR BOOKING TOOL
The setup process is short. The decisions inside it matter more than the code itself.
Travelpayouts describes widgets as promotional tools that can include search forms and other interactive booking content. Some are customizable. Others are ready-made and only provide generated code.
Generate the widget and tracking marker
Use this sequence in your Travelpayouts account:
- Connect the affiliate program that offers the tour or activity product you want to promote.
- Open that program’s tools area and select an available widget.
- Choose “Set up” when customization is available, or use “Get the Code” for a ready-made option.
- Set the visible options that match your page, such as language, currency, title, destination, or traveler details.
- Select the correct Project if your account uses more than one website.
- Create a SubID for the placement before copying the code.
A SubID is your placement marker. It lets you separate results from a Rome guide, a newsletter landing page, or a sidebar widget. Use names you can understand months later.
For example, use rome-museums-widget instead of widget1. Keep the name short and record it in a spreadsheet with the page URL and program name.
Dashboard names and widget controls can change. If your screen doesn’t match these steps, follow the current Travelpayouts affiliate tools documentation using the labels shown in your account.
Install a Travelpayouts widget on WordPress
WordPress gives you two practical routes. Use the Travelpayouts plugin when it supports your selected program and widget. Use generated code when you need manual control or the plugin doesn’t show the tool.
Use the WordPress plugin first
Install and activate the official plugin through your WordPress admin area. Sign in to your Travelpayouts account in the same browser session.
Then open the page or post where the widget belongs. Add a Travelpayouts block, choose the connected affiliate program, select the widget, adjust the available settings, and embed it.
Travelpayouts provides an official guide for adding widgets through the WordPress plugin. Widget-level choices can override broader plugin settings, so check the preview after saving.
Place the block after useful travel advice. A reader should understand why the booking option is relevant before they see it.
Paste generated code without breaking it
Use a Custom HTML block if you copied a code snippet from Travelpayouts. Paste the full code exactly once. Don’t remove script lines, IDs, or tracking values.
If you use WordPress Code Editor, keep the code separated from surrounding copy. Travelpayouts recommends a shortcode comment wrapper for code placed in articles:
<!-- wp:shortcode -->
<!-- Paste the complete generated Travelpayouts widget code here -->
<!-- /wp:shortcode -->
Preview the page before publishing. Avoid switching back and forth between Code Editor and Visual Editor after pasting a widget. WordPress can alter or remove code during later edits.
Don’t paste a widget into a paragraph block. Don’t add the same code to a header, footer, and article while testing. One controlled placement makes faults easier to find.
ADD THE WIDGET TO AN HTML WEBSITE
A standard HTML site doesn’t need a plugin. You need access to the page template, page builder code area, or CMS HTML field.
Put the code inside the content area
Paste the complete generated Travelpayouts code where the booking tool should appear. The widget needs enough room on mobile and desktop screens.
A content section might look like this:
<section class="tour-booking">
<!-- Paste the complete Travelpayouts-generated widget code here -->
</section>
Use a section that sits inside the main article content. Don’t place the code inside another script tag. Don’t load it through a tag manager unless you understand how that setup affects page rendering and consent controls.
If your site has a strict Content Security Policy, the browser may block external widget files. Your developer needs to review the browser console and allow only the domains the generated code requires.
Check mobile layout before launch
Open the preview on a phone, tablet, and desktop browser. Confirm the widget doesn’t overflow the page width or sit behind a sticky navigation bar.
A slow page also needs attention. Avoid adding several third-party booking tools to one article. Each extra script can add load time and confuse the reader.
Keep one primary booking action per page section. A tour widget beside competing hotel, flight, insurance, and car-rental tools creates noise.
TEST SEARCHES, LINKS, AND PAGE BEHAVIOR
Publishing a visible widget is not the finish line. Test the full visitor route before sending traffic to the page.
Run a controlled visitor test
Open the published page in an incognito or private browser window. This reduces the chance that your own logged-in account or browser history changes the result.
Then test these points:
- The widget appears without a blank area or browser error.
- A destination or tour search returns a useful partner result.
- The outbound link opens the expected booking site.
- The destination, dates, language, and currency match your setup where those options apply.
- The widget works on mobile without hiding the search button.
Take a screenshot of the working version. Record the page URL, date, program, Project, and SubID. This gives you a baseline if the result changes later.
A search form can appear normal but send users to the wrong destination. Test the results page, not only the widget frame.
Watch for common placement failures
A blank widget often points to code being removed by the CMS, a blocked script, a caching issue, or a program connection problem.
A generic destination may mean the widget settings weren’t saved, the URL parameters are wrong, or the tool does not support the level of prefill you expected. Check the options available for that exact program.
If the widget works in preview but not on the live page, clear site and browser caches. Then test again in a private window.
VERIFY AFFILIATE ATTRIBUTION AND REPORTING
Clicks are not revenue. A booking can remain pending, cancel later, or fail a partner condition. Your internal tracking needs to separate visitor activity from approved earnings.
Confirm the SubID appears in reports
After the widget receives real clicks, open the relevant program reporting area in Travelpayouts. Filter by the Project, SubID, date range, and page placement where the report supports those fields.
Create one operating record for each widget placement:
| Field | What to record |
|---|---|
| Content page | The exact published URL |
| Program | The connected travel advertiser |
| Project and SubID | The tracking values used in generated code |
| Launch date | When the widget went live |
| Traffic source | Organic, email, social, or paid traffic |
| Results | Clicks, searches, bookings, pending rewards, approved earnings, and reversals |
Keep pending rewards separate from approved earnings. A high pending balance is not money you can use for forecasting.
Compare results by approved EPC
Approved earnings per click helps you compare placements with different traffic volumes.
Approved EPC = approved earnings / outbound clicks
A city guide with 100 clicks and $40 in approved earnings can beat a page with 1,000 clicks and $20 in approved earnings. Give the stronger page better internal links and a more visible position.
Don’t overwrite earlier figures when an earning is reversed or adjusted. Add a new row with the change date and reason. You need the history when a booking cancels or a program updates a result.
FIX PROBLEMS WITHOUT GUESSING
Most widget problems fall into four groups: display, destination, tracking, or program eligibility. Treat each one as a separate check.
Use a short troubleshooting order
Start with the live page. Confirm the widget renders and the booking link opens. Next, verify that the code contains the intended Project and SubID.
Then check the program connection and the current tool settings in Travelpayouts. Finally, allow for the reporting window before deciding tracking failed.
Don’t keep changing the page while you investigate. A new code snippet, a new SubID, and a new page layout create three possible causes.
If support needs to investigate, send a complete record:
- The content URL and a screenshot of the widget.
- The Project, program name, tool type, and SubID.
- The test date and your expected result.
- The report date range and screenshots of relevant report rows.
For a custom site, multi-page tracking plan, or a handoff your team can’t complete, Book A Call with the implementation details ready.
FINAL CHECK BEFORE YOU PROMOTE THE PAGE
A working Travelpayouts widget connects useful travel content with a relevant booking path. The code is the easy part. Matching the program, page intent, destination, and tracking marker is what makes the placement usable.
Publish one placement first. Test its search path, outbound link, and reports. Then measure approved earnings, not clicks alone, before you add the same widget across your site.
