Track the Source of Leads and Bookings in Chili Piper
Click counts alone do not show which marketing activity produced a real booking. By passing channel, source, campaign and keyword details through an embedded Chili Piper scheduler, you can connect each meeting to the activity that brought the visitor to your site.
Why attach source data to the booking
Google Analytics and similar tools are useful for counting visits, but they do not reliably show how many leads or customers each channel produced. The workflow below attaches attribution details to the booking itself, so the record created in Chili Piper carries its origin with it.
Step 1: Install the snippet and configure the widget
Install the attribution snippet on your website using the provider's guide for your site builder, such as WordPress, Wix or Webflow. Then paste your Chili Piper link into the embed code generator. It returns a modified version of the standard Chili Piper embed with additions that let attribution data pass through. Place that updated code where the widget should appear.
Step 2: Attribution is stored and passed through hidden fields
On each visit, the attribution tool examines technical arrival details in a similar way to Google Analytics, classifies the visitor into a channel such as Paid Search, Organic Social or Referral, and stores that classification in the browser. When the visitor later books through the embedded Chili Piper form, the stored details are submitted with the booking through hidden fields.
Step 3: Use the data in Chili Piper, your CRM or a spreadsheet
Once data is flowing, check the event details in Chili Piper, push the fields to Salesforce, Pipedrive or HubSpot to build CRM reports and dashboards, or send the records with Zapier to Google Sheets or Excel. From a spreadsheet you can filter and sort the records and visualise them in Google Looker Studio or Power BI.
What a captured booking can show
Consider a prospect who clicks a Google Ad for social media management services and books through the embedded scheduler. The booking can carry Channel: Paid Search; Channel Drilldown 1: Google; Channel Drilldown 2: the campaign name; and Channel Drilldown 3: the keyword used. If the same person arrived through organic search instead, the record would show Channel: Organic Search; Channel Drilldown 1: Google; Channel Drilldown 2: www.google.com; and Channel Drilldown 3: the keyword searched. That distinction lets you tell paid and organic demand apart on every booking.
Report 1: Leads by channel
A monthly breakdown by Paid Search, Paid Social, Organic Search, Referral and other channels shows what is actually generating bookings. If organic search produces most leads while most budget goes to social ads, the report exposes the mismatch and supports moving spend toward the stronger source.
Report 2: Leads by Google Ads campaign
Segment Google Ads bookings by individual campaign month by month. Campaigns that consistently produce bookings can be scaled with more confidence, while weak campaigns can be refined or reduced.
Report 3: Leads by social network
Break bookings down by platform such as Facebook, LinkedIn and Twitter. A side-by-side view shows which networks drive leads, so organic social effort can concentrate on the strongest platforms and ease back elsewhere.
Quick quality check
Before publishing a report, check that every booking carries a channel, that paid and organic search are not merged, and that campaign and keyword drilldowns are populated where UTM parameters exist. Those checks prevent a channel total from hiding the campaign-level detail needed for budget decisions.
| Field | Paid-search example | Organic-search example |
|---|---|---|
| Channel | Paid Search | Organic Search |
| Channel Drilldown 1 | ||
| Channel Drilldown 2 | Campaign name | www.google.com |
| Channel Drilldown 3 | Keyword used | Keyword searched |
Example values are illustrative and depend on UTM parameters and search terms present on the visit.
Frequently asked questions
How does lead-source data reach a Chili Piper booking?
Install the attribution snippet on your site, generate a modified Chili Piper embed from your Chili Piper link, and place that embed where the scheduler appears. The attribution tool then stores the visitor's channel in the browser and passes it through hidden fields when the booking is submitted.
What does the captured data look like for paid versus organic search?
A paid-search example records Channel: Paid Search, Channel Drilldown 1: Google, Channel Drilldown 2: the campaign name, and Channel Drilldown 3: the keyword. An organic-search example records Channel: Organic Search, Channel Drilldown 1: Google, Channel Drilldown 2: www.google.com, and Channel Drilldown 3: the searched keyword.
Where can the attribution data be used after capture?
You can view the details on the event in Chili Piper, send them to Salesforce, Pipedrive or HubSpot for CRM reporting, or export them via Zapier to Google Sheets or Excel for filtering, sorting and visualisation in tools such as Google Looker Studio or Power BI.