A clinic that wants online bookings has three realistic routes. List the doctor on a marketplace platform and take bookings there. Embed a third-party booking widget on the clinic's own website. Or build a booking flow that sits on the clinic's own domain and connects to its own systems. Each route works. They differ on four things that matter more than the feature list: what you pay and how, who holds the patient data, how much of the experience you control, and whether you can see what happened between the first click and the booked appointment.
This post is for doctors, clinic owners and practice managers, and for the marketing or IT person advising them. It builds on our earlier note on setting up a Practo profile and does not repeat it. We do not publish any platform's current fee card here, because prices change and vary by plan. Instead, it gives you the matrix and the questions to ask each vendor, so you can fill in the numbers from the quotation in front of you.
Define the three options precisely
Marketplace booking. Patients find the doctor inside a listing platform, which also handles the booking. The platform brings its own audience and its own brand. The patient relationship begins on the platform's pages.
Embeddable widget. A scheduling tool, sold by a software vendor, that you place on your own site as a button, popup or iframe. The page and brand are yours; the booking form and often the patient record sit with the vendor.
Custom build. A booking flow designed and hosted as part of your own website, connected to your scheduling source (a practice management system, a calendar, or the HIS if you are a hospital). More design freedom, more build and maintenance work.
These routes are not exclusive. Many clinics run a marketplace listing for discovery and a widget or custom flow for patients who arrive through their own site, Google Business Profile or referrals.
The build-vs-buy matrix
Score each row from the real quotation, not from a brochure.
| Dimension | Marketplace listing | Embedded widget | Custom build |
|---|---|---|---|
| Fee model | Often subscription and or per-booking; confirm which events are billable | Usually monthly per doctor or location; check booking caps | Build cost plus hosting and maintenance; no per-booking fee unless you add a payment gateway |
| Who the patient is, in your records | Held first by the platform; you may receive a contact and booking detail | Held by the vendor; export may be limited | Held by you |
| Brand control | Low: platform layout and ranking rules | Medium: theme and text, within limits | High |
| Conversion tracking | You see platform reports, not your own funnel | Depends on whether the widget sends events to your analytics | Full, if you instrument it |
| Time to launch | Days | Days to weeks | Weeks to months |
| Integration with your scheduling | Platform's own calendar or a supported integration | Varies widely; check two-way sync | As deep as you build |
| Multi-location or multi-doctor | Per-doctor listings | Plan-dependent | Designed for your structure |
| Exit cost | Lose listing and reviews | Re-create the flow; patient export may be difficult | Low if you own code and data |
| Maintenance burden | Platform | Vendor | You or your agency |
Two rows deserve more detail.
Row one: data ownership is a legal as well as a commercial question
Under India's Digital Personal Data Protection Act, 2023, the entity that determines the purpose and means of processing personal data is a "Data Fiduciary" and a party that processes on its behalf is a "Data Processor" (see the definitions in the Act). Which party holds which role in a marketplace booking can differ from a widget on your own site, and the answer shapes who must give notice, who handles correction and erasure requests, and who is responsible for security.
You do not need to resolve that in an article. You do need to ask each vendor in writing:
- Do you act as a processor for the clinic, or do you treat the patient data as your own?
- Can you export every patient and booking record in a standard format, on request, at any time?
- On what terms do you contact patients we sent you, or patients we received from you?
- What happens to our data if we leave?
The DPDP Rules' consent and notice provisions come into force eighteen months after publication of the Rules in November 2025, per the Rules text. Choose tools now that can support a notice and a consent record, rather than finding out in 2027. Have your legal adviser review the vendor contract.
Row two: conversion tracking decides whether you can improve anything
A booking route that cannot tell you where patients dropped off is a black box. For each route, check what you can measure.
- Marketplace: typically you can see views, bookings and sometimes patient source within the platform's own reports. You will not see how a patient got from your Google Ads click to the platform page, unless the platform allows tagging.
- Widget in an iframe: the widget runs on another domain. Unless the vendor sends events or you configure cross-domain measurement, your GA4 sessions break at the widget and a booking looks like direct traffic. GA4 cross-domain measurement works by listing the domains and passing the client and session IDs in a
_glURL parameter, as described in Google's cross-domain measurement help. It does not work across an iframe unless the widget cooperates, so ask the vendor what it does. - Custom build: you can send named events at each step. A usable set is
booking_started,slot_selected,details_submitted,otp_verifiedandbooking_confirmed, each with doctor, location and source parameters. Our conversion tracking page covers how those events map to ad platforms.
A simple test before you sign: ask the vendor to book a test appointment from your campaign link and show you, in your own analytics, where the booking appears. If they cannot, your cost per booking will be a guess.




