TL;DR
Evaluate dermatology campaigns with a source-by-service table that preserves the promoted service, requested service and verified appointment event. Keep medical access, cosmetic consultations and later procedures separately labeled. Define exclusive acquisition rows before totaling people, retain mixed or unknown requests, and show missing links. A combined cost-per-lead figure can hide a service mismatch or an unresolved receiving queue.
Give the combined report a decision to support
The owner needs to know whether a campaign reached the service the practice intended to grow and whether the practice could handle the resulting task. A channel total alone cannot answer that. Neither can a service total that removes where the requests arrived and what the public invitation said.
The report should preserve separate facts: what was promoted, what the person requested, where receipt was recorded and which later administrative event the practice can verify. If the requested service is unknown, do not assign it from the landing page. A medical-service page may receive a cosmetic question, and a cosmetic campaign may receive a general practice inquiry.
These are possibilities to test in actual records, not assumptions about dermatology conversion. Keep clinical interpretation out of the marketing report. Authorized practice staff should classify the administrative request within approved systems and prepare only the summary approved for the intended recipient.
Build the source-by-service evidence table
Use the same inclusion rule and observation basis throughout the table. The row structure is an original reporting proposal. Fill amounts and counts only from appropriately available practice evidence.
| Source evidence | Promoted task | Requested service bucket | Receiving outcome | Later verified event | Purchasing implication |
|---|---|---|---|---|---|
| Named campaign and recorded receipt | Medical appointment request | Medical, cosmetic, mixed or unknown ___ | Correct team, transferred, unaccepted or unknown ___ | Defined medical appointment event, if supported ___ | Is the medical invitation and route doing the purchased job? |
| Named campaign and recorded receipt | Cosmetic consultation request | Medical, cosmetic, mixed or unknown ___ | Correct team, transferred, unaccepted or unknown ___ | Defined cosmetic consultation event, if supported ___ | Does the consultation offer preserve service intent? |
| Professional source under the declared method | Verified referral task | Practice-approved service category or unknown ___ | Referral coordination state ___ | Defined appointment event, if supported ___ | Is the professional receiving process usable? |
| General or unassigned entry | No supported campaign assignment | Known request category or unknown ___ | Actual accountable role ___ | Supported event or unavailable ___ | Which source or service evidence remains missing? |
Add included population ___; original receipt period ___; observation cutoff ___; duplicate rule ___; source method ___; service-definition version ___; expense basis ___. Keep consultation and procedure columns separate if the practice later supplies procedure evidence. Do not infer a procedure from attendance.
Resolve the unit before summing rows
A source field can represent measured website routing, a campaign record or someone's optional remembered discovery. Those are different forms of evidence. Google Analytics distinguishes first-user, session and event traffic-source scopes. Google's scope documentation. Name the actual field used; it is not automatically a person's complete discovery history.
For a people-based acquisition table, define how included people receive an exclusive reporting row where the approved records support reconciliation. Preserve overlapping influences separately. Do not add remembered source mentions to exclusive campaign rows and call the sum unique patients.
Mixed service interest also needs a rule. A person asking about medical and cosmetic appointments can appear in a separately labeled mixed group for the people total. Service-request events may be reported separately with an explicit overlapping-event label. Do not duplicate that person in the total merely to improve each service line's acquisition count.
If an appropriate identity match is unavailable, report request events with that limit. Do not call an unlinked form count distinct people. Keep the general event dictionary beside the report when definitions are approved.
Read the combinations before choosing the repair
If a medical campaign receives supported cosmetic requests, inspect its public invitation and destination. The next task may be changing the message rather than expanding distribution. If the requests are medical but arrive at cosmetic coordination, inspect routing and transfer acceptance. Those findings call for different owners.
If a cosmetic campaign produces appropriate consultation requests but later procedure evidence is unavailable, stop the conclusion at the verified consultation event. Do not replace the missing financial outcome with a procedure-rate assumption. An available consultation does not establish later procedural capacity either.
If professional referrals reach the right service but remain unaccepted, retain the unresolved state. More patient-search spending would not demonstrate that the referral receiving problem is fixed. If the source or service cannot be established, improve the specific missing record prospectively rather than rewriting earlier periods.
Make service-level cost labels honest
Let C be recorded cost allocated to a declared source-and-service row and Q its included inquiry units under the stated definition. When Q is positive, C ÷ Q is cost per included unit for that row. State whether the unit is a request event or a distinct inquirer. With an empty denominator, show unavailable rather than a fabricated efficiency result.
Shared agency, production or software charges need a documented allocation and a visible unallocated remainder where appropriate. A media-only amount should not be compared with a fully allocated service cost without explanation. No cost calculation establishes causal appointment growth by itself.
Ask the reporting partner to attach the accepted work, operational change dates and evidence limitations. GetPatients has a commercial interest in healthcare visibility services. Apply the same source and service boundaries to its reports. The reporting guide covers method transparency; this table adds the service-intent and receiving-team combinations that change a dermatology spending decision.
Frequently asked questions
Can the same person request medical and cosmetic appointments?
The reporting design should handle that possibility. Preserve a mixed group for a deduplicated people view and label overlapping service-request events separately.
Should the requested service come from the ad they clicked?
Preserve the promoted service as its own fact. Use actual appropriately available inquiry evidence for requested service, or leave it unknown.
Is a blended practice total still useful?
It can summarize a clearly defined unit after the components reconcile. Keep the source-by-service table available so the summary does not conceal an actionable mismatch.