Capture Facebook Ads Data in Calendly Bookings
Impressions and clicks show activity, not whether advertising produced booked calls. The workflow below connects Facebook campaign tags to a Calendly booking so each completed appointment carries the campaign, ad set, ad, network and landing-page context that led to it. That makes it possible to compare bookings, leads and later revenue by the advertising that generated them.
Tag every Facebook ad before sending traffic
Use a consistent tagging pattern on every Facebook destination URL. Medium identifies paid social, source identifies Facebook, campaign names the campaign, term names the ad set, and content names the individual ad. Consistency matters because later reports group bookings by these values; varied spellings for the same campaign will split results. A practical check is to open each tagged link, confirm the parameters survive to the landing page, and confirm the campaign, ad set and ad names match the naming used in the ad account.
Store attribution, then pass it through the Calendly embed
Install the attribution snippet on the website, then generate a modified Calendly embed using the booking-widget URL and place that embed where the scheduler appears. When a visitor arrives from a tagged ad, the attribution tool records the source in the browser. If the visitor browses other pages or returns later before booking, that stored context can still be attached when the Calendly form is submitted, rather than only working when booking happens on the first landing page. Test the full journey with a tagged link, navigation to a different page, and a test booking, then inspect the resulting Calendly event for the expected fields.
What the captured data adds
The same capture covers bookings from organic search, paid search, organic social, referrals and direct visits, not only Facebook. It also records the first landing page and its page group, such as a blog section, alongside the UTM values. Minor tagging inconsistencies, for example facebook versus facebook.com as the source, can be normalised to the correct channel so reporting is less fragmented. Keep a short field map in your CRM or spreadsheet: channel for budget comparisons, network for placement comparisons, campaign for monthly performance, and landing page or group for content decisions.
Use the data where decisions are made
Send the booking data to a CRM to follow leads through to customers and revenue, export it to a spreadsheet for analysis or dashboard tools, include it in lead-notification emails, or pass it to a connected billing platform to see revenue by advertising source. Choose the destination based on the decision you need to make: CRM reporting for pipeline and revenue, spreadsheets for quick analysis, email notifications for immediate lead context, and billing data for revenue attribution.
Three reports to run first
Start with three views. Leads by channel compares Facebook with other channels and helps reallocate budget toward the sources producing bookings. Leads by network separates placements such as Instagram, Messenger and WhatsApp so stronger placements can receive more spend. Leads by campaign shows monthly bookings per campaign, highlighting campaigns that convert rather than only attracting clicks. Review these views together: a campaign may look efficient by channel, weak by network, or strong in one month and weak in the next.
Pre-launch checklist
Before relying on the reports, confirm that every Facebook ad uses the same parameter pattern, that the site snippet is present on pages containing the scheduler, that the generated embed replaced the standard embed, and that test bookings carry campaign, network and landing-page fields. If you are evaluating a trial or paid plan, check the provider's current signup page for the applicable trial length, pricing and cancellation terms before committing.