Duda Integration

If you build websites for a living, you know the moment a client says: "and we need to take bookings." For agencies and web professionals working in Duda, that sentence used to mean evaluating booking systems, wrestling with third-party checkouts, and owning the support burden afterwards. With TicketingHub, it means pasting one embed snippet. The result is a client site that sells tours, tickets, and activities directly — while the client manages inventory, pricing, and bookings themselves in a dashboard built for operators.

What is Duda?

Duda is a professional web design platform aimed at agencies, freelancers, and SaaS companies that build websites at scale. Where DIY builders focus on the individual site owner, Duda focuses on the people who build many sites: it offers team collaboration, client management, and white-label tooling so an agency can design, deploy, and maintain dozens or hundreds of client websites efficiently.

• Keep all customer projects organised and easy to find.
• Assign tags for simple status management across a portfolio of sites.
• Control access with roles and permissions, so teams and clients each see what they should.
• Collaborate with teams or individual clients on the same project.

What TicketingHub adds

TicketingHub is a cloud booking platform designed for museums, zoos, aquariums, tours, and activity operators. It gives your client one place to manage every sales channel — their website, their front desk, and OTA or reseller channels — with real-time availability shared across all of them. For the agency, that means the booking problem is solved once, properly, and does not come back as a support ticket.

• All sales channels managed and compared in one dashboard.
• Bookings, manifests, and availability updated in real time.
• Fewer customer-service enquiries and cancellations, because customers self-serve.

How the integration works

TicketingHub's checkout widget embeds into any Duda site through Duda's HTML embed capability. The widget is created and published in the TicketingHub dashboard, where its colours, fonts, and text can be customised to match the site design you have built — with custom CSS available when the brand demands pixel-perfection. Visitors book and pay without ever leaving the client's website, and every sale appears instantly in the client's TicketingHub dashboard. No IT or coding knowledge is needed on the client's side, and nothing about the embed interferes with Duda's editor or your design system.

For agencies serving tourism clients

If tour operators, attractions, or experience businesses are part of your client base, TicketingHub gives you a repeatable answer to the booking question. Build the site in Duda as usual, embed a widget styled to the client's brand, and hand over. The client runs their business in TicketingHub; you are not on the hook for ticketing support. Because Duda is built for managing many client sites, and TicketingHub supports separate widgets per business, the pattern scales cleanly across your whole portfolio.

For a single operator on a Duda site

Plenty of operators end up on Duda because their agency or hosting partner works there. If that is you, the integration is just as simple from your side: your web professional pastes the snippet once, and from then on you control products, prices, schedules, and availability yourself — no need to call the agency to change a departure time.

For sites that sell across channels

A Duda website is often just one of several places an operator sells. TicketingHub's channel manager shares the same live inventory with OTAs and resellers, so the widget on the Duda site, the front desk, and every third-party channel draw from one pool of availability. No double bookings, and no reconciling spreadsheets at the end of the week.

Setting it up

In the TicketingHub dashboard, create a checkout widget: choose the products, extras, or packages it should sell, style it to the site design, and publish. Copy the embed or pop-up code from the installation instructions and paste it into the Duda page using an HTML embed element. Preview, publish the site, and take a test booking. Most integrations are done in well under an hour — and if you are an agency planning to roll this out across several clients, talk to us about the fastest way to set that up.

Frequently asked questions

Does the client need coding knowledge to use this?

No. The only technical step is pasting the embed snippet into the Duda page, which the web professional typically does once. Everything the operator touches afterwards — products, pricing, availability, bookings — lives in TicketingHub's point-and-click dashboard.

Can the widget match the site design we built?

Yes. Colours, fonts, and text are all customisable in the widget editor, and custom CSS is supported for complete control. The widget can be embedded in the page or triggered as a pop-up from a button you design.

As an agency, can we manage widgets for multiple clients?

Each operator runs their own TicketingHub account and dashboard, which keeps their data and revenue cleanly separated — but the embed pattern is identical for every client site, so your team only has to learn it once.

Do bookings sync automatically?

Yes. Every purchase made through the widget on the Duda site is recorded in TicketingHub the moment it happens, alongside bookings from any other channel, and availability adjusts everywhere instantly.

How are payments handled?

Customers pay inside the widget. Stripe handles direct card processing, with PayPal and 100+ other gateways also supported. TicketingHub never stores card data, so neither the Duda site nor your agency carries that risk.

Building in Duda for a client who sells experiences? Book a demo and we will show you how quickly the booking side can be done.