Wellness page-inquiry to confirmed-introduction comparison
Compare two actual inquiry cohorts with their own recorded confirmations.
Use the interactive tool without signing up. It runs in your browser: enter your numbers, save a comparison, download results or print a working copy. Your numbers are not sent to BlueFinch.
Illustrative example inputs
These starting values show how the math works. They are not industry averages, customer results or a quote.
| Input | Example value |
|---|---|
Unique inquiries from selected page A One source definition and observation window. | 40 |
Page A inquiries with confirmed introductions Actual same-cohort scheduling evidence. | 16 |
Unique inquiries from selected page B Own page cohort using the same counting method. | 30 |
Page B inquiries with confirmed introductions Actual confirmations, not clicks or submitted forms. | 9 |
Example results
| Measure | Result |
|---|---|
Page A recorded confirmation share Confirmed introductions among its inquiries. | 40% |
Page B recorded confirmation share Own source group and denominator. | 30% |
Observed percentage-point difference Signed descriptive difference, not a ranking or causation result. | 10 |
Calculation detail
| Measure | Result |
|---|---|
| Page A inquiries without confirmed introductions | 24 |
| Page B inquiries without confirmed introductions | 21 |
Model assumptions
- Define source attribution and deduplicate inquiries under a stated rule.
- Keep each confirmed introduction linked to its own inquiry cohort.
- Use one observation date and retain pending requests.
- The descriptive shares prove no causal page effect or clinical outcome.
Read alongside these results
- No tracking, message or booking is created.
- Use aggregate totals, not actual URLs with private values.
- Empty inquiry groups have unavailable rates rather than invented zero conversion.
Download this worked example (CSV). Use the interactive version to export your own inputs and results.
Two website pages attract inquiries, but the owner wants to know which requests reached a confirmed introduction. Traffic alone does not answer the question. Follow each inquiry group to its actual scheduling evidence. A button click, form submission or preferred date should not become a booking merely because the analytics event is named consultation complete.
The worksheet above compares confirmed introductions among two defined page inquiry cohorts. Its starting counts are fictional. Enter authorized totals, not real URLs containing private values or customer records. The tool installs no tracking and books no appointments. Its shares describe the entered records without proving the page caused a booking or improved anyone's health.
Use with this guide
Review website evidence and gaps
A technical finding is not a booked customer.
Write a supported next-step answer
Explain actual requests and confirmation separately.
Browse the complete wellness center guides and worksheets.
Define the page source and unique inquiry
Define the page-source rule and intake period for each group. Do not turn several forms from one visitor about the same request into several people. Deduplicate through a documented method in the authorized system. Keep original inquiry references beside their later outcomes, using each page's own cohort rather than linking new requests to unrelated older scheduling confirmations.
Set an observation date and retain pending requests. HubSpot documents task owners, due dates and associated records. Use equivalent fields to assign a missing scheduling-source question. A completed callback task does not establish confirmation. Count an introduction only when the business's real scheduling record supports the event, leaving later attendance and completed service outside that booking measure.
Sources for this section: HubSpot: Task owners, due dates and associated records
Keep booking evidence outside public analytics tags
Google Analytics guidance addresses avoiding personal information in collected fields. Keep campaign labels nonpersonal, excluding symptoms, appointment reasons, names and contact details from tracking events. Inspect the proposed payload with fictional data through the authorized test process. Do not paste prior answers into this worksheet or send health details merely to make attribution more convenient.
HHS scope guidance describes covered entities and information. A wellness-center name alone does not decide applicable status or permission for a tracking design. Have the appropriate reviewer assess actual data flows and other obligations. This public aggregate tool supplies no privacy clearance and does not replace qualified review of website intake, analytics or scheduling destinations.
Sources for this section: Google Analytics: Avoid personal information in collected fields · HHS: Covered entities, information and actual Privacy Rule scope
Read the fictional cohort comparison
The fictional page A group has 40 unique inquiries and 16 confirmed introductions, a 40 percent share. Page B has 30 inquiries and nine confirmations, a 30 percent share. The observed gap is ten percentage points. These figures demonstrate the math and are not a website benchmark or measured BlueFinch customer conversion result.
Twenty-four page A inquiries and 21 page B inquiries lack recorded confirmations at the observation date. Some remain pending. NIST discusses proportions and separate statistical questions. This calculator conducts no statistical test and proves no causal page effect. Empty inquiry groups leave their rates unavailable. Different source traffic or observation opportunities limit what the comparison supports.
Sources for this section: NIST: Comparing observed proportions and statistical questions
Use website findings without inventing attribution
BlueFinch's website audit organizes supported technical and content findings, source dates and collection gaps. It does not calculate every downstream customer outcome, certify privacy compliance or automatically change another website. Share the actual finding with the authorized editor and responsible reviewer. Check collection scope before treating an overview as a complete audit or verified explanation of missed bookings.
Download the cohorts for the website review. Start with missing source evidence and assign a supported next check of the actual request route. Keep inquiry, confirmed introduction and attendance as separate records. Evaluate later documented outcomes without renaming clicks as customers or assuming a technical finding explains every scheduling decision in the selected group.
Sources for this section: BlueFinch: Website findings, source dates and collection gaps
Primary sources
BlueFinch last reviewed these sources on October 4, 2026. Payment rules and state requirements can change.
- HubSpot: Task owners, due dates and associated records
- Google Analytics: Avoid personal information in collected fields
- HHS: Covered entities, information and actual Privacy Rule scope
- NIST: Comparing observed proportions and statistical questions
- BlueFinch: Website findings, source dates and collection gaps
Use this page for general business information. It is not legal, tax, or accounting advice.
Related resources
- 2026 Credit Card Processing Cost Report
- Wellness Center Payment Guide
- Wellness Center Credit Card Processing Calculator
- Review wellness repeat visits without confusing prepaid purchases with attendance
- Massage studio processing: sessions, packages and tips
- Pilates and yoga card fees: price memberships and class packs