Skip to content

Capture UTM Parameters in Chili Piper Across Pages and Channels

If a visitor clicks an ad, browses your site, and only later books a meeting, you still need to know which campaign brought them in. This guide explains why the built-in capture misses those bookings, how browser-stored attribution fixes the gap, and which reports become possible once the data reaches your CRM or spreadsheet.

Why bookings lose their source

Chili Piper makes booking easy, but knowing which campaign produced a booking is a separate problem. Ads on Google, Facebook, Instagram, LinkedIn, X and Bing are only useful for attribution if their UTM parameters travel with the lead. The same applies to niche placements such as industry publications and outbound email.

The built-in capture has a narrow window: it works only when the meeting is booked on the exact page the visitor landed on. A common journey breaks it — click a Google Ad, land on the homepage, click Talk to Us, then complete a Chili Piper form on a different booking page. By then the parameters are no longer in the URL, so the booking arrives with no source information. That undercounts ad-driven leads and hides which spend is working.

A browser-stored attribution approach solves both the page-change problem and the channel problem. A small snippet installed on the website — directly in site settings or via Google Tag Manager — analyses how each visitor arrived, categorises the channel, and stores that data in the browser. When the visitor later submits a Chili Piper form, the stored data is passed through alongside name, email and phone number.

Setup checklist and worked example

Work through this checklist in order:

  • Add UTM parameters to every ad link, including social, search, publication and email campaigns, so the landing URL carries source, medium, campaign and term.
  • Install the attribution snippet on the website using site settings or Google Tag Manager, following the owner's confirmed setup instructions: {{OWNER_TRIAL_TERMS}}.
  • Confirm that a booking made on a different page than the landing page still receives the original parameters. Test with a tagged ad click, navigate to the booking page, and book a test meeting.
  • Check the meeting details in Chili Piper for the passed fields, then forward them to Salesforce, HubSpot, Pipedrive, Zoho CRM or a spreadsheet such as Google Sheets or Microsoft Excel for reporting.

Worked example: a visitor clicks a Facebook ad, lands on the homepage, then uses a Talk to Sales button to reach a separate booking page. The passed data in the example is UTM_Medium = Paid Social, UTM_Source = Facebook, UTM_Campaign = Brand Campaign and UTM_Term = Olmo Software. That pattern — landing page different from booking page — is exactly the case the built-in capture misses.

Built-in capture vs. stored attribution

Three differences matter when choosing a method:

  • Coverage: built-in capture tracks paid campaigns using UTM parameters only. Browser-stored attribution covers all traffic, including Organic Search, Organic Social, Referral and Direct, giving a complete picture rather than a paid-only slice.
  • Persistence: built-in capture requires booking on the landing page. Stored attribution survives navigation across multiple pages before booking.
  • Cleanliness: built-in capture copies URL values verbatim, so inconsistent tagging fragments reporting. Stored attribution normalises capitalisation, spelling and formatting — for example grouping adwords, google and google.com variants under Paid Search — so CRM reports need less manual cleanup.

Four reports to build first

Once attribution reaches the CRM or a spreadsheet, four reports are straightforward to build:

  • Leads by Channel: count meetings per month by channel to see whether budget matches where leads actually originate — for instance, shifting spend toward SEO if Organic Search drives many leads.
  • Leads by Facebook Ads Network: split results across Facebook, Instagram, Messenger and other networks in the same ad account to see which placements deliver.
  • Customers by Google Ads Campaign: count customers per month per campaign to focus budget and optimisation on campaigns producing customers, not just clicks.
  • Revenue by Keyword: add the keyword to Google Ads UTM parameters via tracking templates, then report revenue per keyword to raise bids on proven terms.

Start with Leads by Channel, because it reveals the biggest allocation mistakes first, then drill into network, campaign and keyword detail.

Frequently asked questions

Does Chili Piper's built-in UTM capture work across pages?

No. The built-in capture only works when the booking is completed on the same page where the visitor first landed, while the parameters are still in the URL. If they browse to another page first, that information is lost.

Does the built-in capture cover organic and referral leads?

No. It is designed for paid campaigns that use UTM parameters. Organic Search, Organic Social, Referral and Direct Traffic are not picked up, so most non-paid leads have no source data.

How can attribution survive navigation to a booking page?

Yes, by storing the attribution data in the visitor's browser on arrival and passing it through when they later submit the booking form, even after navigating to a different page.

Why does raw UTM data become messy in a CRM?

Raw values are copied exactly as they appear in the URL, so variations such as adwords, google and google.com for utm_source become three separate sources. Normalising capitalisation, spelling and formatting into a single channel such as Paid Search avoids that cleanup.