Web tracking and attribution for aesthetic clinics
Connect captured campaign sources with the patients who enquire and book at your aesthetic clinic. See the context behind a conversion, then compare campaigns with recorded patient value where acquisition reporting is enabled.
Knowing a conversion occurred leaves your clinic with bigger questions: who booked, which campaign brought them in, and what happened next? DappleOS connects captured campaign context with enquiries, bookings and patient records. Where acquisition reporting is enabled, follow that story through to recorded patient value, without matching website exports to a separate patient spreadsheet.
Capture page visits and campaign context, with continuity into your booking portal.
Review the tracked pages a lead visited before your team replies.
Distinguish the patient’s original acquisition source from the touch associated with a booking.
Where acquisition reporting is enabled, compare channels with recorded patient value and attribution coverage.
Add your brand’s tracking snippet to your clinic website, directly or through Google Tag Manager. Web Tracking settings show when traffic was last received for each brand, helping your team spot a connection that needs attention.
Each brand uses its own patient-portal domain and snippet. Review brands separately instead of letting a busy website hide a quiet one.
Active means traffic has arrived within the last 24 hours. Inactive and Not set up distinguish a silent connection from one with no recorded traffic.
Administrators can receive an alert when a recently active brand stops reporting traffic. The status stays Unknown if a health lookup is unavailable.
When a tracked visitor is connected to a lead, the lead record can show the pages they viewed, visit times and captured campaign details. Your team can see the interest behind the enquiry before picking up the conversation.
See recorded page titles and visit times together with the source, medium and campaign when captured.
Supported enquiries, Web Chat, bookings and sign-in can connect visitor history to the patient record. Anonymous visits alone do not identify a person.
Someone might discover your clinic through search and return through a campaign before booking. DappleOS keeps the original acquisition source distinct from the marketing touch associated with an individual booking, where that history is captured.
Uses the earliest connected web touch. When web history is missing, a recorded lead source or the patient’s own referral answer can provide context.
Uses the last captured marketing touch before that booking request, falling back to the visitor’s first touch when needed.
Missing tracking or an unconnected visitor can leave a source unattributed. Attribution shows an association with recorded activity, not proof that a campaign caused a booking.
One patient. Two different questions.
Original acquisition source
Captured booking touch
An example of how the two records differ when both visits are captured and connected.
With acquisition reporting enabled, the Acquisition and LTV by channel report connects recorded sources and campaigns with patients, lifetime value and value in their first 90 days. Review coverage alongside the result so you know how much of the patient base has a known source.
Review customer counts, lifetime value and campaign breakdowns. The report also shows average first-90-day value for patients acquired at least 90 days ago.
Which channels bring in patients who return? Which campaigns have a recorded source? Start with the report, then review the underlying records with your team.
Value is based on invoiced amounts, not profit or advertising return. It includes paid and owing amounts, is tax inclusive and is not reduced by refunds. The report does not add advertising costs or guarantee that every patient can be attributed.
DappleOS · Acquisition and LTV by channel
| Channel / campaign | Customers | Lifetime value | Average 90-day value |
|---|---|---|---|
| Paid searchspring-consultations | 24 | $84,000 | $540 |
| Organic search | 15 | $48,000 | $480 |
| Referral | 9 | $36,000 | $620 |
| Unattributed | 12 | $24,000 | $390 |
Conversion postbacks
Campaign attribution helps your team understand who booked and the source connected to that booking. Conversion postbacks carry selected outcomes from DappleOS back to your advertising platform, so its measurement can include what happened after the website visit.
Choose which events to send and confirm consent and privacy-notice requirements during setup. Postbacks use generic event details, without treatment names or clinical notes. Hashed contact details are included only with the patient’s ad-measurement consent. Platform matching and consent can leave gaps; a postback does not guarantee attribution or better ad performance.
Connect Meta Ads to send selected lead, confirmed online-booking and revenue events from DappleOS through the Conversions API. The recommended setup sends new leads, confirmed online bookings and invoices paid in full, connecting ad measurement with recorded clinic outcomes.
Google Ads conversion postbacks are coming soon. They will provide a separate connection for sending selected clinic outcomes back to Google Ads. Website tracking and attribution in DappleOS remain distinct from this unreleased integration.
Trust and compliance
Set up tracking for your clinic’s websites and review what the captured data can tell you.
Feature availability depends on your plan, enabled features and access permissions.
It connects captured website visits, referrers and campaign details with enquiries and patient records. Staff can review a lead’s tracked page history. Where acquisition reporting is enabled, your clinic can compare acquisition channels and campaigns with recorded patient value.
Yes. Your website team can add the brand-specific tracking snippet to your existing site, directly or through Google Tag Manager. Each brand needs a configured DappleOS patient-portal domain. Book a demo to review your website, booking journey and setup.
Yes, where page visits were captured and the visitor is connected to the lead. The lead record can show page titles, visit times and campaign details. It does not identify every anonymous visitor, and no history is shown when there is no tracked activity.
Not necessarily. Original acquisition records the earliest connected web touch, with a lead source or self-reported referral as fallbacks. A booking uses its own captured marketing touch before the request, or the visitor’s first touch if needed. This keeps discovery distinct from the activity associated with a later booking.
Where enabled for your clinic, Acquisition and LTV by channel reports patient counts, attribution coverage, invoiced lifetime value and average first-90-day value by source or campaign. The first-90-day measure includes only patients acquired at least 90 days ago. Availability and setup can be reviewed in your demo.
No. Browser behaviour, consent configuration, missing tracking and unconnected visitor records can leave gaps. Recorded patient value is not an ad-spend return calculation or proof of causation. Sending conversions to advertising platforms is separate from website tracking and attribution.
Web Tracking settings show each brand’s traffic status and when traffic was last received. Active means an event was received within the last 24 hours. Administrators can receive alerts when a recently active brand stops reporting. If a status lookup fails, the interface shows Unknown instead of assuming the snippet is missing.
Meta Ads conversion postbacks are available. Google Ads conversion integration is coming soon and its release depends on platform approval. Conversion postbacks send conversion events back to an advertising platform; they are separate from tracking website visits and reporting attribution in DappleOS. Speak with our team about supported events, clinic setup and consent controls before use.
Ask how your clinic’s website, booking journey and marketing reporting could connect in DappleOS.