A lead form for every ad campaign: UTM kept, one lead per phone, routed to the nearest branch.
Installs with LeadDesk, whose screen it works onGives each ad campaign its own hosted lead form, shared as a link, a QR code or an embed on the clinic’s website. Every fill keeps the UTM source, medium, campaign, term and content, the Google and Meta click ids, the page it came from, and the exact consent words the person ticked. One phone number is one lead: a second fill from the same number is added to the open lead as a repeat. Each lead goes to the branch the person chose or, failing that, the one for their pincode: a pincode rule first, then a branch at that pincode, then the nearest pincode, then the campaign’s default branch. The rule that matched is kept, and a rule can name a doctor. A report per campaign and per source shows leads, repeats, bookings and visits. Meta lead ads and Google Ads lead forms land here the moment a form is filled, with no automation service in between: Meta’s webhook is believed only when signed with the clinic’s own app secret and the lead is read with its Page token, Google’s only when it carries the key set on the lead form; each lead lands once, by the platform’s own id, through the campaign its form is mapped to (a lead from an unmapped form is held until it is mapped, and a Google test lead is kept apart). This needs the clinic’s own Meta app and Google Ads account — until their keys are in the clinic’s key settings the screen says “not connected” and what to add — and their CSV exports still import here, routed and de-duplicated the same way. Build the form itself too: up to twelve questions of the clinic’s own (short answer, pick one, yes or no, a date), required or not, over up to three steps before the contact details, and a landing page around it (an introduction, a few points, a picture, the button’s words); embedded in a website the page is left out. Every answer is checked against the form before anything is kept, and goes to the enquiry in LeadDesk.
/ad-leadsadlead.readWhat it does not do, by design. A listing with only benefits is an advertisement.
Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.