A travel insurance page without a clear next step wastes high-intent traffic. Readers may understand why they need cover, but they still need a fast way to compare or buy a policy.
A Travelpayouts insurance widget puts that action inside your guide, destination page, or booking checklist. You don’t need advanced coding, but you do need the right program access, correct tracking, and a visible disclosure.
Set those controls before you paste anything into your site.
Check the Program and Page Before You Embed
Travelpayouts widgets only appear for programs that support them. First, join the insurance partner program in your Travelpayouts account. Then confirm that its tools are available to your project.
Open Programs and use the Tools filter. Find the relevant insurance brand, then look for the Widgets tab or a similar tool option. Travelpayouts may change dashboard labels and widget settings, so confirm the names in the current interface before you publish.
The platform’s insurance directory currently lists policy-based commission tiers. A sale between $50 and $199.99, for example, is listed at $5. Higher policy values can pay more. Check the live program terms before you build revenue forecasts because rates and eligibility can change.
Match the Widget to Reader Intent
Place insurance tools on pages where insurance is already part of the decision. Good placements include:
- International trip-planning guides with visa, health, or cancellation information.
- Digital nomad articles that discuss medical coverage abroad.
- Family travel checklists and cruise planning pages.
- Booking confirmation pages, if your site has a post-booking content flow.
Don’t put an insurance widget on every page. A reader searching for “best cafes in Lisbon” may not be ready to buy travel cover. A reader researching “travel insurance for a trip to Portugal” probably is.
The destination page, trip duration, traveler location, and policy requirements should match the tool’s available fields. If the widget can’t pre-fill those details, explain what the reader needs to enter.
Create a Clean Project Record
Set up the correct Travelpayouts Project before generating code. Use the site domain where the widget will appear. This keeps reporting organized when you run multiple sites or traffic sources.
Create a simple record with:
| Field | What to record |
|---|---|
| Page URL | The exact page where the widget appears |
| Program | The insurance brand connected to the widget |
| Project | The Travelpayouts project selected during setup |
| SubID | A page or placement identifier |
| Publish date | The date the embed went live |
| Disclosure status | Where the affiliate notice appears |
This record solves basic reporting problems later. You can see which page, placement, and program produced a click or approved reward.
Generate Your Travelpayouts Insurance Widget Code
After you join the program, open its tool area and select the widget you want. Travelpayouts describes the normal flow as choosing a program, selecting a widget, adjusting supported options, and copying the generated code.
Use the Get the Code button after you select your settings. If your account has several Projects, choose the right one from the Project dropdown before copying the snippet.
Travelpayouts also lets many tools use a SubID or additional marker. Use one from day one.
Use a Simple SubID Structure
A SubID identifies where a click came from. It doesn’t replace your analytics platform, but it makes affiliate reports more useful.
Use short, consistent values. Avoid spaces and vague labels.
Examples:
italy-insurance-topjapan-guide-midnomad-checklist-endsidebar-insurance
Don’t reuse the same SubID across unrelated pages. You need separate values to compare placements fairly.
A page with 1,000 clicks and $30 in approved rewards is weaker than a page with 120 clicks and $48 in approved rewards. Track the source of each result before you move widgets, rewrite calls to action, or add more traffic.
Set Only the Options You Can Verify
Some Travelpayouts widgets support language, currency, project selection, SubID, dimensions, and referral-link settings. Other widgets have fewer controls.
Don’t assume every option applies to every insurance tool. Check the preview and test the final result on desktop and mobile.
Travelpayouts notes that some widgets are responsive, not all of them. If the tool has a fixed width, place it inside a content area that doesn’t break on a 360-pixel mobile screen.
A widget that loads but forces readers to pinch, scroll sideways, or guess what to click is not ready to publish.
Keep the default design if it fits your site. A small color adjustment is fine. Rebuilding the surrounding page around a third-party embed usually creates more maintenance work than revenue.
Add the Widget to an HTML Website
For a custom HTML site, the job is simple. Copy the full widget code from Travelpayouts and paste it into the page template or CMS content field that accepts scripts.
Place it after the section that explains the insurance need. Do not place it before the reader understands why they should use it.
A practical page sequence looks like this:
- Explain the trip risk or policy requirement.
- State what the reader should compare, such as medical limits, cancellation cover, or destination eligibility.
- Add the widget.
- Place your disclosure directly above or below it.
- Add a short reminder to check exclusions and policy wording.
Put the Embed in the Right Container
Use a normal content-width container. Avoid placing the widget inside a hidden tab, popup, accordion, or lazy-loaded area until you confirm that the code still loads correctly.
Don’t edit the generated JavaScript, partner ID, or tracking parameter. A minor change can stop clicks from reaching the correct Travelpayouts account.
If your site uses a static-site generator such as Hugo, Jekyll, Astro, or Next.js, confirm that the content pipeline allows third-party scripts. Some systems strip scripts from Markdown files or sanitize HTML during the build.
Add the widget in a component or page section that your team can find later. Document the template name and publish date. If the provider changes the tool, you need to know where the old code lives.
Test the Published Page, Not Only Preview Mode
A staging preview can hide problems. Your live site’s consent banner, cache plugin, content security policy, or script optimizer may block the widget after publication.
Open the public URL in a private browser window. Then test it on a phone. Check that the widget appears, accepts input, and sends the visitor to the expected insurance partner path.
If you use Cloudflare, WP Rocket, LiteSpeed Cache, or another optimization tool, exclude the Travelpayouts script only when testing shows that optimization breaks it. Don’t disable site-wide performance settings without evidence.
Add the Widget in WordPress
WordPress gives you two practical options. You can use the Travelpayouts plugin, or you can paste generated code into the editor.
The official plugin is named “Travelpayouts: All Travel Brands in One Place.” Install it through WordPress, activate it, then connect it with your Travelpayouts partner ID and API token. Travelpayouts warns that widgets and tables won’t track correctly if you skip this account connection. Follow the current WordPress plugin setup instructions before inserting tools.
Use the Plugin Block When Available
In the block editor, add a Travelpayouts block. Select the insurance program and widget. Open Settings, choose the available options, then select Embed widget.
The plugin route is easier for editors who don’t want to touch code. It also reduces the chance that WordPress strips a required script during an edit.
Set the correct Traffic source in plugin settings. This should be the website where the tool appears. Confirm your partner ID and API token are still connected after plugin updates or a site migration.
Use the Code Editor for Manual Embeds
If the insurance widget doesn’t appear as a plugin block, paste its generated code in the WordPress Code Editor. Don’t use a standard Paragraph block.
Travelpayouts provides guidance for placing widgets in WordPress articles. Their instructions include a shortcode-style wrapper for manual placement so WordPress preserves the code when you switch editors.
After you publish, reopen the page in the normal visual editor. Check that WordPress didn’t convert the snippet into visible text or remove part of the script.
Keep one copy of the original generated code in a secure internal document. Label it with the program, project, SubID, and page URL. If a future editor damages the embed, you can restore a known-good version.
Put Affiliate Disclosure Next to the Offer
Affiliate disclosure is part of the page, not a footer task. If you earn a commission when a reader buys through a widget, say so where they can see it before they engage with the tool.
Use plain language. This copy is ready to use:
Disclosure: We may earn a commission if you buy travel insurance through this widget. This doesn’t change the price you pay.
Place the notice directly above the widget, directly below it, or beside a related call to action. Don’t hide it in a site-wide legal page.
The FTC says disclosures must be clear and conspicuous. Review the FTC’s endorsement disclosure guidance if you reach U.S. readers. Your country, audience location, and partner agreement may add other requirements.
Don’t Make Coverage Claims for the Insurer
Don’t write that a policy is “best,” “guaranteed,” or suitable for every traveler. Insurance policies have exclusions, eligibility rules, waiting periods, and destination limits.
Use factual page copy instead:
- “Compare available policy options for your trip.”
- “Check medical cover, exclusions, and destination eligibility before you buy.”
- “Read the policy documents before payment.”
Your content should explain what readers need to check. The insurer’s policy documents control the actual coverage.
Verify Tracking Before You Send Traffic
Do not assume tracking works because the Travelpayouts insurance widget appears on the page. A visible tool can still contain the wrong project, an old partner ID, or a broken script.
Travelpayouts says its tool code includes a partner ID. Their affiliate tool testing guide explains how to inspect the live code and check the shmarker parameter.
Run a Controlled Click Test
Use this process after each new placement:
- Open the published page in a private browser window.
- Inspect the widget code and confirm that
shmarkerincludes your Travelpayouts partner ID. - Complete one normal click through the widget.
- Confirm the destination opens without an error.
- Open Travelpayouts Reports and refresh the relevant date range.
- Check that the click appears, then compare the recorded SubID with your placement record.
Travelpayouts states that tool clicks can appear in reporting in less than a minute. If no click appears after the normal reporting window, collect the page URL, project name, program name, SubID, partner ID, test time, and screenshots before contacting support.
Don’t create fake bookings to test commissions. A click test is enough to confirm basic attribution. Use a legitimate booking only when it follows the partner’s rules.
Measure Approved Earnings, Not Widget Activity
Impressions and clicks are early signals. Pending rewards are not operating income. Cancellations, refunds, approval windows, and program rules can change the final number.
Track these fields each month:
| Metric | What it tells you |
|---|---|
| Outbound clicks | Whether readers use the widget |
| Bookings or leads | Whether traffic progresses |
| Pending rewards | Potential income only |
| Approved rewards | Usable page-level performance |
| Reversals | Cancellations or lost commissions |
| Approved EPC | Approved rewards divided by clicks |
Use this formula:
Approved EPC = approved earnings / outbound clicks
Preserve adjustments instead of overwriting old figures. When a reward reverses, add a new row with the date, amount, and reason. Your record should show what the dashboard reported first and what the final result became.
Final Checks Before You Scale
A Travelpayouts insurance widget works when it matches the page, uses the correct project and SubID, and passes a live tracking test. The code is the easy part. The operating controls protect your reporting and reader trust.
Start with one or two high-intent pages. Review approved EPC, reversals, mobile behavior, and disclosure placement after the first reporting cycle.
Count approved earnings, not clicks. A widget that produces fewer clicks but more approved income is the placement worth expanding.
