Feeding Booking Data Back into Google Ads: Offline Conversions Explained
A clinic ran Google Ads, but the account could not see which enquiries became real bookings. The booking system sat separately, so the platform had no way to link an ad click to an appointment. That made it impossible to measure return on ad spend, and left the ad system optimising for form fills rather than patients. The fix is to feed booking data back to the platform.
This is known as importing offline conversions. Here is what it means, why it matters and how a clinic can do it responsibly.
What offline conversions are
An offline conversion is a result that happens outside the ad platform, such as a booking made by phone or in a separate system, or a patient who attends. By importing that information, you tell the platform which clicks led to real outcomes, so it can learn from them.
Why clicks and forms are not enough
Ad platforms count what they can see: clicks, calls and form submissions. But many forms are never followed by an appointment. Optimising for forms can favour cheap, low-quality enquiries. Optimising for bookings points the system towards the searches and audiences that actually produce patients.
Offline conversions and return on ad spend
Without booking data, you cannot calculate what each pound of advertising returns. With it, you can see cost per booked patient and, if you also record value, revenue per pound spent. That turns advertising from a cost into an investment you can judge.
How the process works
When someone clicks an ad, the platform records a click identifier. If that identifier is stored with the enquiry, you can later send back the outcome, such as booked or attended, along with the time. The platform matches it to the original click and learns from it.
Capture the click identifier
Your website forms need to store the identifier with each enquiry, so it can be linked later. A developer or agency can set this up. Without it, the connection is lost. Test that the identifier reaches your booking or customer system correctly.
Connect your booking system
Decide how booking outcomes will flow back. Some systems offer direct integrations, and others need a regular export. Even a simple weekly upload from a spreadsheet can work at small scale. Choose a method your team can keep up reliably.
Choose which outcomes to send
Common choices are booked appointment, attended appointment and paid treatment. Attended is often more reliable than booked. You can send more than one and assign values. Start simple, and refine once the flow is working.
Respect privacy and consent
Offline conversion data involves personal information. Be clear in your privacy notice about how data is used, get any consent that is needed and follow data protection rules. Share only what the platform needs, and never send detailed health information. Handle it carefully.
Use references, not health details
You do not need to send clinical information to gain the benefit. The platform needs the click identifier, the outcome and a time, not diagnoses. Keep sensitive details out of the process, and store them only where they belong.
Expect a delay
Bookings and attendance happen days or weeks after the click. The platform can only use conversions within its allowed window. Upload regularly and promptly so that the learning stays fresh and complete.
Check that the numbers match
Compare what you send with what the platform shows, and with your own records. Small differences are normal. Large ones suggest a matching problem. Regular checks keep the data trustworthy, and stop the system optimising from faulty signals.
Let the data change your decisions
Once real bookings feed in, review which campaigns, searches and pages produce patients. Shift budget, tighten targeting and adjust bidding accordingly. The value of the data is in the decisions it changes.
Start small and improve
Begin with one campaign or service, prove the flow works and then extend it. A small, reliable setup beats an ambitious one that breaks. Document the process, so it survives staff changes, and review it every quarter.
Plan who maintains the process
Offline conversion imports depend on regular uploads and checks. Name a person responsible, with a backup, and put the routine in the diary. Processes that belong to no one fade within months, and the platform quietly loses its link to real outcomes.
Test with a small batch first
Before uploading everything, send a small sample of bookings and confirm that the platform matches them correctly. Check the numbers in the account against your records. A small test catches mistakes cheaply, and gives you confidence that the larger flow will work.
Understand the limits of matching
Not every click can be matched to a booking, because of privacy settings, changed devices or missing identifiers. Expect a share to be unmatched, and interpret results with that in mind. Treat imported data as a strong signal, not a perfect record.
Review the results each quarter
Every three months, review how many bookings were matched, how bidding changed and how cost per booked patient moved. Use the findings to refine the process and to decide where to invest. Regular review keeps the effort worthwhile, and shows whether it is paying back.
A quick checklist
- Store the click identifier with every enquiry.
- Decide which outcomes to send.
- Choose a method you can keep up reliably.
- Protect privacy and send no health details.
- Upload promptly and compare figures.
- Change budgets based on real bookings.
Our companion article on the optimisation score explains a less useful measure, and our guide to tracking ad ROI without online booking covers a simpler starting point. If you would like help, we are glad at Pulse Digital Health to talk.
Frequently asked questions
What are offline conversions?
Results that happen outside the ad platform, such as a booking made in a separate system. Importing them tells the platform which clicks led to real outcomes so it can learn from them. Ask your developer to store the click identifier with each enquiry. Storing the identifier is the step that makes everything else possible.
Why import booking data into Google Ads?
Because platforms otherwise count only clicks, calls and forms. Importing bookings lets you measure return on ad spend and helps the system optimise for patients, not cheap enquiries. Send bookings and attendance, not health details. Keeping health details out protects patients and keeps you compliant.
What do I need to set it up?
Forms that store the click identifier, a way to send booking outcomes back, such as an integration or regular upload, and clear privacy notices and consent where needed. Choose a method your team can keep up reliably. A reliable method beats an ambitious one that breaks.
Do I need to send health information?
No. The platform needs the click identifier, the outcome and a time. Keep clinical details out of the process and follow data protection rules. Upload promptly and check the numbers against your records. Prompt uploads keep the learning fresh and complete.
Why is there a delay?
Bookings and attendance happen days or weeks after the click, and the platform only uses conversions within a set window. Upload regularly and promptly. Start with one campaign and test a small batch first. A small first step proves the flow before you rely on it.
How do I start?
Begin with one campaign or service, prove the flow works, check the figures against your records and then extend it. Document the process so it survives staff changes. Document the process so it survives staff changes. A written process survives holidays and changes of staff.
