Capture UTM Parameters in Zoho Bookings
A booking tells you who wants a meeting, but not which campaign persuaded them to book. This guide explains how to attach channel, campaign, landing-page, and click-ID data to every Zoho Bookings submission so those records can be reported in a CRM or spreadsheet.
The problem: bookings arrive without campaign context
Without attribution, a booking record shows the person who booked but not the journey that led to the booking. That gap makes it hard to tell whether paid search, paid social, organic search, referrals, or direct visits are producing meetings. The fix is to carry visitor-level channel data forward until the booking form is submitted, then store it beside the contact details the visitor provides.
Four-step setup
First, place the attribution snippet on the website, using the site settings area or a tag manager where appropriate. Second, create hidden single-line fields in the Zoho Bookings form for Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Third, let the attribution tool populate those fields at submission. Finally, review the completed booking in Appointments, send the values to a CRM, or export them for spreadsheet analysis. Use the website installation guides and hidden-field setup instructions for platform-specific steps.
Worked example: from ad click to booking page
Consider a visitor who clicks a Google ad, reaches the homepage, then moves to a consultation page and books there. The captured values might read Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Consultation Campaign, and Channel Drilldown 3 = Business Strategy. Because the attribution is stored in the browser, booking on a later page does not erase the original campaign context. Landing-page fields add a further distinction: they show which page first brought the visitor in, not merely where the form happened to be completed.
Beyond UTMs: organic channels and click IDs
UTM values alone do not cover every lead. Organic search, organic social, referrals, and direct visits also need a channel so reporting is not limited to paid campaigns. Click identifiers add another layer: GCLID for Google, MSCLKID for Microsoft, and FBCLID for Meta. Capturing those identifiers can help connect a booking to the originating ad click and, where the workflow supports it, send a downstream conversion back to the advertising platform when the lead becomes a customer.
Reports to build after capture
Once attribution travels with each booking, reporting can move from visits to outcomes. Leads by channel shows the monthly mix across paid and organic sources. Leads by Meta Ads network separates Facebook, Instagram, Messenger, and other placements. Customers by Google Ads campaign connects campaigns to new customers rather than clicks. Revenue by keyword, when keyword values are included in the ad tracking template, shows which search terms produce income. Compare the channel mix with spend before shifting budget: a strong organic-search contribution alongside heavy paid spending may indicate an opportunity to invest more in search content, while weak placements can be reduced.
Pre-publication checklist
Before publishing, confirm the attribution product name, any trial or pricing terms, and whether the customer example and scale figures may be used. Verify image rights and that each registry link destination is live. Do not present the example figures or testimonial as the new publisher's own customer history.
| Hidden field | What it records | Reporting use |
|---|---|---|
| Channel | Broad source category, such as Paid Search or Organic Search | Leads by channel |
| Channel Drilldown 1 | Platform or source detail, such as Google | Leads by Meta Ads network or platform splits |
| Channel Drilldown 2 | Campaign-level detail | Customers by Google Ads campaign |
| Channel Drilldown 3 | Finer campaign, ad, or keyword detail | Revenue by keyword when keyword data is included |
| Landing Page | Page where the visitor first arrived | Content and landing-page performance |
| Landing Page Group | Category grouping for landing pages | Grouped content reporting |
Field set described in the captured workflow; exact labels should be confirmed in the live Zoho Bookings form before implementation.
Frequently asked questions
Why does a Zoho Bookings record not show where a lead came from?
Zoho Bookings does not provide a built-in way to attach campaign attribution to each booking, so the booking record alone will not show which campaign, ad, or keyword produced it. Adding hidden attribution fields and populating them from the visitor's earlier journey lets that information travel with the name and email submitted.
What fields should be added to the booking form?
Add hidden fields for Channel, Channel Drilldown 1 to 3, Landing Page, and Landing Page Group, then use a website attribution tool that stores the visitor's channel data in the browser and writes it into those fields when the booking is submitted.
Will attribution survive if someone books on a different page from their landing page?
Yes. Storing attribution in the browser means the data can still be passed through if the visitor lands on one page, browses to another page, and books there, rather than booking on the original landing page.
What click IDs can be captured alongside UTM parameters?
Beyond UTM values, click identifiers such as GCLID, MSCLKID, and FBCLID can be captured. That can support sending a conversion back to an advertising platform when a booking becomes a paying customer, instead of relying only on a thank-you page visit.
What can you do with the captured booking data?
You can view the values with each appointment, push them to a CRM such as Zoho CRM for reporting, or export them to a spreadsheet for analysis. The useful reports include leads by channel, leads by Meta Ads network, customers by Google Ads campaign, and revenue by keyword.