TL;DR
Agree on source evidence and encounter states before accepting an urgent-care ROI report. Keep ad interactions, received inquiries, registration, arrival, completed encounters and collections separate. A known source is an observed connection, not proof that marketing created otherwise absent demand. Report an incomplete connection honestly rather than assigning every encounter to the campaign.
Write the report's acquisition question
Decide whether the campaign aims to produce consumer service inquiries, attended encounters for a defined offer or employer-account opportunities. Keep those objectives separate when they use different buying and receiving processes. The same reporting period does not make their totals interchangeable.
Choose the service, location, campaign period and later observation cutoff. Identify the evidence the practice can appropriately use and who may reconcile it. The article's dictionary is a reporting specification to negotiate, not permission to collect new patient information or upload records to a platform.
The historical JUCM marketing ROI article calls for agreement on marketed services, credited revenue, full costs, linked visits and tracking period. It also describes limitations of source recall. JUCM's ROI discussion. Use that conceptual caution without adopting its old prices, worked examples, suggested tracking duration or assumed incremental returns.
Adopt an encounter source and state dictionary
Have operations map each label to an actual system and event. Keep absent fields marked unavailable.
| Reporting label | Evidence required | Unsupported promotion of the label |
|---|---|---|
| Campaign interaction | Named platform event under the actual configuration | Calling it an inquiry or encounter |
| Inquiry received | Receiving team or approved system establishes receipt | Treating every unanswered call click as a received request |
| Registration submitted | Registration system establishes its actual completion state | Calling it an appointment or arrival without evidence |
| Appointment confirmed, where applicable | Scheduling system verifies the specific reservation | Assuming every urgent-care service uses booked slots |
| Arrival recorded | Clinic establishes arrival under its local definition | Assuming attendance produced a completed encounter |
| Encounter completed | Authorized clinic reporting owner verifies the qualifying event | Treating the event as a new person or collection |
| Collection recorded | Finance supplies actual receipts under a declared basis | Treating charges or estimates as collected money |
| Unresolved | Evidence cannot establish the next state | Filling the gap with a projected conversion |
Preserve legitimate paths that omit an earlier digital event. A walk-in can reach a completed encounter without an online registration. An employer-directed visit can have a commercial origin that a consumer ad tag does not explain. Do not force either through a fabricated website funnel.
Put a source method beside every connection
Use a separate source field: recorded campaign connection, optional self-report, employer direction, other documented origin, mixed evidence or unknown. Record how the information was obtained and what it actually describes. A source reported at arrival can differ from the route used to submit registration.
Keep source uncertainty separate from encounter uncertainty. A completed encounter with unknown source remains completed. A tagged registration with no verified later event remains a registration. The report should not erase either because it cannot complete the full journey.
Google Business Profile counts call-button clicks in its Calls metric. Google's metric definitions. Do not use that total as answered calls or merge it with practice-received calls without a supported reconciliation method.
Have the practice's reporting owner resolve duplicates and related events internally. Repeated attempts to register, a call about a pending request and a changed appointment can be handling activity without representing additional acquired people. Share only the report approved for its actual purpose and recipient.
Preserve timing and corrections
Record the inquiry cohort separately from encounters completed during a calendar period. Someone may register before the reporting boundary and arrive later. Someone may arrive without a match to the campaign record. State how the report handles those situations and which records remain pending at the cutoff.
Keep original event history when correcting a duplicate or misclassification. A later reconciliation can improve the report without pretending the original evidence was complete. If a tracking change alters which events are visible, mark the comparison break.
Use the general measurement dictionary for upstream discovery boundaries and the source-question guide for neutral self-report design. This urgent-care dictionary adds the distinct registration, walk-in arrival and encounter records.
Set a threshold for the claim, not a target result
Ask the analyst what evidence supports the proposed wording. If the practice can verify source-linked completed encounters, use that label. If the evidence supports only registrations, report registrations. Neither label alone establishes incremental business or causal ROI.
Finance should supply the actual cost scope and collection basis for any financial analysis. Keep service delivery costs, collection timing and attribution assumptions visible. When the connection cannot be substantiated, return an evidence gap rather than inventing a return estimate.
GetPatients has a commercial interest in healthcare visibility services. Apply the dictionary to any report used to sell or renew that work. A useful report can be narrower than a sales claim and still tell the owner what to investigate next.
Frequently asked questions
Can all visits during a campaign be credited to it?
A shared period does not establish a connection. Retain unlinked and unknown-source activity separately, and state the actual attribution method and its limits.
What if arrivals are known but registrations cannot be linked?
Report the supported arrival or encounter series and disclose the missing connection. Do not estimate a joined funnel from unrelated totals.
Does a tracked encounter prove the campaign caused it?
No. A documented source connection can support a descriptive report. A causal claim needs additional evidence appropriate to that question.