Track Facebook Ads Through Chili Piper Bookings
Clicks alone do not show whether paid social is producing meetings. This guide connects a Facebook ad click to the eventual Chili Piper booking, so campaign, network and landing-page context are stored with each lead instead of being lost between the first visit and the scheduling form.
Why connect ads to bookings
A Facebook click creates an opportunity, not a result. The useful result is a booked meeting, a qualified lead or a customer. Without attribution carried through to the booking, teams cannot tell which campaigns produced those outcomes and may keep funding clicks that never convert.
The workflow below solves that gap in four stages: tag the ad, install site-wide capture, configure the booking widget to forward the data, and then report on the bookings that arrive.
Four-step setup
Step 1: Tag every Facebook ad URL Add UTM parameters to the destination URL so the campaign, ad set and individual ad can be identified later. Use one consistent convention across the account:
- UTM Medium: Paid social
- UTM Source: Facebook
- UTM Campaign: campaign name
- UTM Term: ad set name
- UTM Content: specific ad
Example pattern: a destination URL followed by utm_medium=paidsocial, utm_source=facebook and utm_campaign=brand-campaign. Consistency matters more than inventing new labels for each campaign.
Step 2: Install the attribution snippet site-wide Add the snippet provided after signup to the website so visits are recognised from the first landing page, not only from the booking page. Installation varies by platform, with guides covering WordPress, Squarespace, Wix, Webflow and similar builders.
Step 3: Configure the Chili Piper widget Paste the Chili Piper scheduling URL into the embed code generator. Use the generated embed in place of the standard Chili Piper embed where the widget should appear. The generated version adds the lines needed to pass attribution fields through with a submission.
Step 4: Let bookings carry the attribution After setup, each visit is tracked by origin. When a visitor submits the widget, attribution details such as campaign and ad set are passed into Chili Piper and stored alongside that booking.
Pre-launch checklist:
- Every live Facebook ad URL has all five UTM fields populated
- The snippet is present on all pages, not only the booking page
- The generated Chili Piper embed, not the standard embed, is live
- A test booking from a tagged URL shows campaign, ad set and ad fields
- A test booking after browsing to a second page still retains the original source
What makes the attribution reliable
Four capabilities make the data dependable for reporting:
- Full-source capture: Google search, LinkedIn, referral sites and direct visits are recorded alongside Facebook, giving a complete channel picture.
- Cross-page memory: attribution is saved in a browser cookie. A visitor who lands on the homepage and books later from a Book a Call page does not lose the original UTM data, unlike a form that only reads parameters on the landing page.
- Cleaner grouping: inconsistent tags such as utm_source=facebook and utm_source=fb are grouped under the correct channel, such as Paid Social, instead of fragmenting reports.
- Landing-page context: the first page visited and its page group are stored as well as the UTM values. A blog landing page, for example, is recorded by full URL and by its /blog group.
Failure distinction to check: if a booking has no campaign data, first test whether the visitor landed and booked on the same page. If that works but cross-page bookings fail, the cookie-based capture or the generated embed is likely missing.
Putting the data to work
Once bookings carry attribution, the same fields can be routed where the team already works:
- CRM: push the data into Salesforce, Pipedrive, HubSpot or another CRM to report leads, conversions and revenue by campaign.
- Spreadsheet: send records through Zapier to Google Sheets or Excel for sorting, filtering and onward connection to tools such as Google Data Studio or Microsoft Power BI.
- Notifications: include the origin fields in new-booking emails so sales representatives know the source before they respond.
Three reports to run first
Three reports answer the main budget questions:
- Leads by channel: compare Paid Social with Organic Search, Paid Search and other channels to see where bookings originate and where spend should shift.
- Leads by network: split Facebook Ads results across Meta-owned networks such as Instagram, Messenger and WhatsApp. This shows which placements drive bookings and helps improve cost per lead.
- Leads by campaign: show monthly bookings per campaign. This moves evaluation beyond clicks and impressions to the campaigns producing real leads, so successful campaigns can be scaled with evidence.
Wrap up
Start with one tagged campaign and one booking page, verify a cross-page test booking, then expand tagging to the full account. Once channel, network and campaign reports are live, budget decisions can be based on bookings produced rather than clicks alone.
Frequently asked questions
What is the shortest path from a Facebook click to a booking I can attribute?
Add consistent UTM parameters to every Facebook ad URL, install the attribution snippet site-wide, then replace the standard Chili Piper embed with the generated version that forwards attribution fields. When a booking is submitted, campaign, ad set, ad, network and landing-page details travel with the booking record.
What if someone lands on one page and books from another page?
Yes. The attribution data is stored in a browser cookie, so a visitor who lands on the homepage, browses other pages, and books later still carries the original campaign information into the booking.
Does this only work for Facebook traffic?
No. The same capture covers Google search, LinkedIn links, referral sites and direct visits, so channel comparisons are not limited to paid social.
Where can the captured data be used after booking?
Push the fields to a CRM such as Salesforce, Pipedrive or HubSpot, export them through Zapier to a spreadsheet, or add them to new-booking email notifications so sales staff see the origin immediately.