Skip to content

Capture UTM Parameters in YouCanBookMe Across Pages

If a visitor clicks an ad, browses your site and books on a different page, the campaign details behind that booking should not disappear. This guide explains how to preserve UTM and channel information through the YouCanBookMe booking flow, store it on the booking record, and turn it into reports by channel, network, campaign and keyword.

Why bookings lose campaign data

Paid campaigns are often judged by meetings booked, not clicks alone. A common gap appears when the first page a visitor sees is not the page containing the booking widget. The visitor may arrive from a search or social ad on a homepage, explore other pages, and only later open the scheduler. In that journey, parameters present in the original URL are no longer present when the form is submitted, so the booking can look unattributed even though an ad drove it. The practical fix is to store attribution when the visitor first arrives, keep it in the browser while they browse, and write it into the booking form at submission.

Four-step setup and field map

First, install the attribution snippet on the website, using the website builder's settings area or a tag manager where appropriate. Second, open the YouCanBookMe form editor, choose Add Question, and create Hidden Questions for the attribution fields you intend to report on. Third, test a booking after arriving through a tagged URL and confirm the hidden values appear on the completed record. Fourth, connect or export those values to the CRM or spreadsheet used for reporting. A useful field map is: Channel for the broad source category, Channel Drilldown 1 to 3 for progressively more specific source detail, Landing Page for the entry page, and Landing Page Group for grouping related entry pages.

Worked example: from ad click to booking record

Consider a visitor who clicks a Google ad, lands on the homepage, then selects a consultation button that opens an embedded scheduler. The stored attribution can populate UTM_Medium as Paid Search, UTM_Source as Google, UTM_Campaign as Enterprise Growth Campaign and UTM_Term as IT support services. Those values are saved with the person's name, email, phone number and other booking answers. The same record can then be reviewed in Scheduled Events, sent to a CRM, or exported for spreadsheet analysis. Use this example as a test case: if any of the four values is missing or mismatched, check the tagged URL, the snippet installation and the hidden-field mapping before relying on campaign reports.

Built-in capture versus stored attribution

Three distinctions matter. Coverage: built-in capture focuses on tagged paid traffic, while stored attribution can also classify organic search, organic social, referral and direct visits. Persistence: built-in capture depends on the booking happening on the landing page, while browser storage carries the original details across pages. Cleanliness: raw UTM values are copied as written, so variants such as adwords, google and google.com can split one source into several CRM values; normalisation assigns them to a single channel such as Paid Search. Together, these differences determine whether reports show every booking's origin or only a subset.

Four reports to build after capture

Start with leads by channel each month to see whether budget matches where bookings actually originate. Then break paid social results down by network, such as Facebook, Instagram or Messenger, to shift spend toward the networks producing bookings. Next, compare customers by Google Ads campaign to identify which campaigns produce customers rather than only enquiries. Finally, where keyword is included in Google Ads tracking templates, report revenue by keyword and raise bids on terms that produce valuable customers. Review these reports in the CRM or spreadsheet where the booking fields land, and act on the pattern rather than on click volume alone.

Hidden booking fields to add
FieldWhat it recordsUse in reporting
ChannelBroad source categoryLeads by channel
Channel Drilldown 1First level of source detailNetwork or source breakdown
Channel Drilldown 2Second level of source detailCampaign or sub-source breakdown
Channel Drilldown 3Third level of source detailKeyword or finer breakdown
Landing PagePage where the visitor first arrivedEntry-page analysis
Landing Page GroupGroup of related entry pagesGrouped landing-page reporting

Field names are taken from the captured setup list; exact form labels should be confirmed in the live YouCanBookMe editor.

Reports worth building
ReportQuestion it answersDecision it supports
Leads by ChannelWhich channels produce bookings?Rebalance budget toward productive channels
Leads by Facebook Ads NetworkWhich social network produces bookings?Focus paid social spend by network
Customers by Google Ads CampaignWhich search campaigns produce customers?Adjust campaign budgets and optimisation
Revenue by KeywordWhich search terms produce revenue?Raise bids on high-value keywords

Report examples are based on captured attribution fields; revenue reporting requires keyword capture and CRM revenue data to be present.

Frequently asked questions

Does YouCanBookMe's built-in UTM capture work across different pages?

No. The built-in option only records parameters when the booking form is completed on the same page where the visitor first arrived. If someone lands on a homepage and then moves to a separate booking page, those parameters can be lost.

Can you capture attribution for organic and direct visitors, not just paid ads?

No. The built-in option is limited to paid campaigns that include UTM parameters. A fuller attribution setup can also classify organic search, organic social, referral and direct visits, so reporting is not limited to paid traffic.

Where can the captured booking data be used after it is recorded?

Yes. Once recorded on a booking, the values can be viewed in the Scheduled Events area, passed to a CRM such as Salesforce, HubSpot, Pipedrive or Zoho CRM, or exported to Google Sheets or Microsoft Excel for reporting.

Why can raw UTM values make CRM reporting messy?

Raw values can create duplicates when naming varies, for example adwords, google and google.com for the same paid search source. Normalising capitalisation and formatting before assigning a channel keeps reports cleaner.