Track the source of leads and bookings in Acuity Scheduling
A booking form can record who booked and when, but without extra fields it usually loses how that person first found you. This guide explains how to preserve marketing origin data inside Acuity Scheduling so paid, organic, and social activity can be compared against actual bookings.
Why booking records need their own source fields
Website analytics and booking tools answer different questions. Analytics can describe how visitors reached a site, while a scheduling record needs to carry that origin forward to the moment someone books. If the origin is not stored with the booking, later reporting has to rely on guesswork or separate manual matching.
The practical fix is to add attribution fields directly to the booking widget. When a visitor submits the form, the fields travel with the booking into the scheduling account. From there they can be inspected per client, included in notification emails, sent onward through integrations, or exported for spreadsheet analysis.
Setup checklist
Work through the setup in order, checking each stage before moving on:
- Install the attribution code on the website using the provider's installation instructions.
- Add hidden fields to every Acuity Scheduling widget: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, and Channel Drilldown 4.
- Confirm the attribution tool is tracking website visitors after the code and fields are in place.
- Submit a test widget and check that the hidden fields contain channel and drilldown values.
- Open the submitted record in the scheduling account to confirm both the client's details and the attribution data were stored together.
A common failure is adding the website code but forgetting the widget fields, or adding fields to only one widget. In both cases bookings may be created without usable source data. Test each widget type you actually use.
What gets stored with each booking
The channel fields break origin into broad and specific layers. Channel gives the broad category, such as Paid Search or Organic Search. The drilldown fields then add the platform, campaign or referring domain, and keyword or other detail available from the UTM parameters.
Consider a paid Google Ads example for a law firm. A booking might store Paid Search as the channel, Google as the first drilldown, the campaign name as the second, and the keyword as the third. The exact labels depend on how the ads were tagged.
An organic example looks different. For an architecture firm found through Google, the record might store Organic Search, Google, the referring domain, and the search keyword. Comparing those two patterns shows why the drilldown fields matter: the broad channel alone cannot distinguish campaigns, domains, or keywords.
Landing page data adds another dimension. The first page a lead visited, together with its page group, shows which part of the site attracted that lead. For example, a blog post URL and its blog category can be counted separately from service pages or other site sections.
Three reports to run first
Once source data is attached to bookings, start with three comparisons:
- Leads by channel: count bookings each month across categories such as Paid Search, Organic Search, and Paid Social to see which broad channels produce volume and which lag.
- Leads by Google Ads campaign: break paid search bookings down by campaign to identify the campaigns generating the most leads.
- Leads by social network: compare bookings from platforms such as Facebook, Twitter, and LinkedIn when ads run across several networks, then direct more effort toward the stronger performers.
These views work best when the same field names are used consistently across widgets. Inconsistent naming between widgets will fragment the reporting even if the underlying tracking works.
Frequently asked questions
Why does website analytics not show the source of a booking?
Website analytics can show how visitors arrived, but it does not attach that origin to a submitted booking. Adding channel fields to the booking form preserves the origin alongside the client's own details, so each record can be reviewed later in the scheduling system, in notification emails, in a CRM, or in a spreadsheet.
Which hidden fields are needed in the scheduling widget?
Add five hidden fields to each scheduling widget: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, and Channel Drilldown 4. The attribution tool then populates those fields when a visitor submits a widget.
What does a captured record look like for paid and organic search?
For a paid Google Ads visit, an example capture is Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = the campaign name, and Channel Drilldown 3 = the keyword. For an organic Google visit, the example capture is Channel = Organic Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = the referring domain, and Channel Drilldown 3 = the keyword. Exact values depend on the UTM parameters used.
Is landing page information also captured?
In addition to channel fields, the initial landing page URL and its page group are captured. That makes it possible to count leads by the site area or page that first attracted them, for example a blog category rather than only a campaign.
How can the captured data be used after submission?
Review an individual record through Clients, then Client List, in the scheduling account. You can also include the fields in lead notification emails, pass them through native integrations to a CRM such as Salesforce, Pipedrive, or HubSpot, or export them to Microsoft Excel or Google Sheets for reporting.
Which reports help compare marketing performance?
Three useful views are leads by channel over time, leads by Google Ads campaign, and leads by social network. Together they show which broad channels, specific campaigns, and social platforms produce bookings, supporting decisions about where to invest more or refine activity.