Skip to content

Track Facebook Ads in Acuity Scheduling

If you run Facebook Ads and take bookings through Acuity Scheduling, the useful question is not only how many clicks an ad received. It is which bookings came from which campaign, ad set, or network. This guide explains how to tag Facebook Ads with UTM parameters, install an attribution script, add hidden fields to Acuity Scheduling booking widgets, and use the captured data in reports.

What you need before you start

You need three things in place: Facebook Ads that point to pages on your website, a way to add a small attribution script to your site, and Acuity Scheduling booking widgets that can accept hidden fields. The setup below uses UTM parameters as the input, a browser-side attribution script as the capture mechanism, and Acuity Scheduling hidden fields as the destination. The protected form-controls contract module accompanies this page and defines the exact control registry; refer to that module for implementation details rather than recreating field names or control values here.

Step 1: Add UTM parameters to your Facebook Ads

A UTM tag is a label attached to the query string of the landing URL you put in an ad. Each label answers a different reporting question: which medium carried the ad, which platform served it, which campaign and ad set it belonged to, and which creative the visitor saw. Keeping those labels consistent is what lets a report group bookings by campaign instead of scattering them across near-duplicate spellings. The source's recommended convention is: UTM Medium = Paid social; UTM Source = Facebook; UTM Campaign = the campaign name; UTM Term = the ad set name; UTM Content = the specific ad. For example, a destination URL of https://roipaths.com/integrations/acuity-scheduling becomes https://roipaths.com/integrations/acuity-scheduling?utm_medium=paidsocial&utm_source=facebook&utm_campaign=brand-campaign. Use the same spelling and capitalization across ads so that reports do not split one campaign into several variants.

Step 2: Install the attribution script on your website

The attribution script is a lightweight tag placed on your site. On each visit it reads the referrer and UTM signals that describe how the person arrived, then sorts that visit into a channel bucket such as Paid Social, Paid Search, or Organic Social. When the same visitor finishes an Acuity Scheduling widget, the script populates the hidden fields with that classification. Acuity Scheduling stores those values next to the name, email address, and any other answers the visitor supplied. Installation instructions for common website builders are available through the source's help registry.

Step 3: Add hidden fields to your Acuity Scheduling booking widgets

Add the following hidden fields to the booking widgets that should receive attribution data: Channel; Channel Drilldown 1; Channel Drilldown 2; Channel Drilldown 3; Channel Drilldown 4; Landing Page; Landing Page Group. Step-by-step instructions, including videos, for adding hidden fields to Acuity Scheduling are available through the source's help registry. The exact field names and control registry are defined in the protected form-controls contract module that accompanies this page.

Step 4: Confirm that Acuity Scheduling captures the data

On arrival from a tagged ad, the script copies the UTM values into a cookie held by the visitor's browser. That cookie is what keeps the campaign detail attached while the person moves between pages, or when they close the tab and return before booking. At widget submission, the script fills the hidden fields from that stored data, and Acuity Scheduling saves it together with the lead's name, email address, and other details. To confirm the setup, submit a test booking using a UTM-tagged URL and check that the hidden field values appear in the Acuity Scheduling record.

Field and control map

The hidden fields map to attribution concepts as follows. Channel identifies the broad source category, such as Paid Social. Channel Drilldown 1 through Channel Drilldown 4 hold progressively finer detail, such as the network, campaign, ad set, or ad. Landing Page records the URL of the visitor's initial landing page. Landing Page Group records the corresponding category, such as /blog. The protected form-controls contract module defines the exact control registry and must be used as the implementation reference.

Where to send the captured data

Once Acuity Scheduling records the attribution values, you can route them to a destination that matches your reporting needs. A CRM such as Salesforce, Pipedrive, or HubSpot lets you report on leads, customers, and revenue by ad source. A spreadsheet such as Google Sheets or Excel, populated through Zapier or a similar platform, supports basic analysis or connection to a reporting tool such as Google Data Studio or Microsoft Power BI. If you do not use a CRM, you can include the Facebook Ads information in the new booking emails that Acuity Scheduling sends. If you use a billing platform such as Stripe or Square with Acuity Scheduling, you can send the attribution data there to see how much money your ads are making.

Decision checklist: choosing a destination

Use this checklist to choose where the captured data should go. If you need lead-to-customer and revenue reporting, send the data to a CRM. If you need lightweight analysis or a handoff to a BI tool, send it to a spreadsheet. If you have no CRM and want source information at a glance, add it to Acuity Scheduling's new booking emails. If you need to connect ad spend to payments, send it to your billing platform. You can combine destinations, but each additional destination adds a sync to maintain.

Three reports to run once data is flowing

Leads by channel shows lead counts grouped by channel, so you can compare Facebook Ads with other channels and decide where to allocate budget. Leads by network shows which Facebook networks, such as Instagram, Facebook, or Messenger, generate the most leads. Leads by campaign shows monthly lead counts broken down by campaign, so you can distinguish campaigns that produce bookings from campaigns that produce clicks but no conversions. These reports depend on the attribution data being captured and sent to a reporting destination.

Common failure distinctions

If bookings show no attribution data, check three separate failure points. First, confirm that the ad's destination URL actually contains UTM parameters; an untagged ad produces no campaign data to capture. Second, confirm that the hidden fields exist on the Acuity Scheduling widget and that their names match the field registry exactly; a missing or misspelled field means the value has nowhere to land. Third, confirm that the attribution script is installed and loading on the pages where visitors arrive and where they book. A cookie or session gap can also cause data loss if a visitor moves between browsers or clears cookies. Treat these as distinct checks rather than a single tracking problem.

What the attribution script adds beyond Facebook Ads

Facebook Ads is only one of the routes this script accounts for. Visits arriving from Organic Search, Organic Social, Referral, or Direct are classified too, so a booking report can compare every channel rather than a single ad platform. Persistence works through the browser: the UTM values are kept in a cookie, which means a visitor who wanders through several pages or returns on a later visit still carries the original campaign detail into the booking. The script also anticipates messy tagging, so a campaign labelled utm_source=facebook and another labelled utm_source=fb can both land in the same channel instead of splitting the report. Finally, it records the first landing page URL and a grouped version of that path, which is how you can tell whether a blog post or another content page is the entry point that produces bookings.

Frequently asked questions

Do I need UTM parameters if I only run Facebook Ads?

Yes. The attribution setup relies on UTM parameters to identify the source, medium, campaign, ad set, and ad. Without them, the booking record will not carry the campaign-level detail needed for reporting.

Which hidden fields should I add to Acuity Scheduling?

Add Channel, Channel Drilldown 1 through Channel Drilldown 4, Landing Page, and Landing Page Group. The protected form-controls contract module accompanying this page defines the exact field registry.

What happens if a visitor leaves the site and returns later?

The attribution script stores UTM parameters in a cookie in the visitor's browser, so the parameters remain available if the visitor browses around the site or leaves and comes back before submitting an Acuity Scheduling widget.

Can I use the captured data without a CRM?

Yes. You can send the data to a spreadsheet through a platform such as Zapier, or add the Facebook Ads information to the new booking emails that Acuity Scheduling sends.