Capture Google Analytics Attribution Data in Chili Piper Bookings
Website analytics can show how many visitors arrived from Paid Search, Organic Search or Social, but it does not show how many of those visitors booked a meeting or became customers. This guide explains how to attach arrival and landing-page information to every Chili Piper booking, then use that record in your CRM or spreadsheet to report on leads, opportunities, customers and revenue by channel.
How attribution reaches the booking
A small website code snippet analyses signals such as UTM parameters and referral sources when a visitor arrives. It assigns the visitor to a marketing channel using categories comparable to those used for website traffic reporting, including Paid Search, Organic Search and Paid Social. That attribution information is kept in the browser until the visitor books a meeting. At booking, it is passed through with the meeting details, stored in Chili Piper, and can then be forwarded to a CRM or another connected tool.
Four-step workflow
Install the attribution code on the website, using the installation method for your builder or platform. When a prospect books through an embedded Chili Piper form, the code populates hidden attribution fields. Chili Piper then saves those fields with the lead's name, email, phone and other booking information. Finally, send the combined record onward and build channel reports in the destination system.
Worked example: a paid-search demo booking
Consider a SaaS prospect who clicks a Google ad, lands on the homepage and books a demo. The booking could carry Channel: Paid Search, Channel Drilldown 1: Google, Channel Drilldown 2: Brand Campaign and Channel Drilldown 3: CloudSync Pro, depending on the UTM values used. It could also carry the first landing page, for example a file-sharing solutions page, and the page category, for example solutions. Together, those fields distinguish both the advertising source and the content that preceded the booking.
Field map: channel versus landing page
Channel captures the high-level source and, for paid traffic, can include campaign, ad group and keyword detail. Landing page data captures the first page visited and its broader category. Use channel fields to judge media performance and landing-page fields to judge which blog posts, service pages or campaign pages generate bookings. Keeping the two concepts separate prevents a common reporting error: a strong channel does not automatically mean every page in that channel performed well.
Four reports to build after capture
Leads by Channel shows monthly bookings by originating channel. Opportunities by Google Ads campaign shows monthly sales opportunities per campaign, helping you spot campaigns worth more budget or copy optimisation. Customers by Facebook Ads Network separates customers acquired through Facebook, Instagram, Messenger, WhatsApp and other Meta placements. Revenue from Organic Search by search engine breaks SEO-attributed revenue across Google, Bing, Yahoo, DuckDuckGo and other engines. Build each report only after the attribution fields are flowing into the CRM or spreadsheet, and compare the same month and attribution definitions across reports.
Pre-launch checklist
Before scaling spend, check that test bookings contain channel, drilldown and landing-page values; confirm the fields survive the Chili Piper-to-CRM handoff; and verify that paid, organic and social test visits are classified as intended. Then use leads, opportunities, customers and revenue together, rather than judging a channel by booking volume alone.
| Field group | What it records | Use it to answer |
|---|---|---|
| Channel | High-level source such as Paid Search, Paid Social or Organic Search | Which channels generate bookings? |
| Channel drilldowns | Platform, campaign, ad group and keyword detail where available | Which campaigns or keywords generate valuable opportunities? |
| Landing page | First page visited by the visitor | Which page first attracted the booker? |
| Landing page category | Broader category of that first page | Which content themes generate bookings? |
Example values depend on the UTM parameters and page structure in use.
Frequently asked questions
Why is website traffic data not enough to judge Chili Piper bookings?
Google Analytics shows visits by channel, but not which of those visitors booked a meeting or later became customers. Adding attribution fields to the booking record closes that gap by storing the arrival channel and landing page alongside contact details.
What is the difference between channel, drilldown and landing page data?
Channel is the high-level source, such as Paid Search, Paid Social or Organic Search. Drilldowns add the platform, campaign, ad group and keyword where available. Landing page data records the first page visited and its category, so you can see which content prompted the booking.
Where should the captured data go after Chili Piper?
Once captured in Chili Piper, use its native integrations or a connector such as Zapier to send the booking plus attribution fields to a CRM, spreadsheet or other sales and marketing system, then build reports there.