Skip to content

Capture Google Ads Data in Chili Piper Bookings

Clicks and site visits do not prove which campaigns create meetings, customers, or revenue. The fix is to carry campaign identifiers from the ad click through the browsing session and attach them to the booking itself, so each meeting can be reported by channel, campaign, ad group, keyword, and landing page.

1. Tag every ad destination consistently

Start with the destination URL for each ad and append small text tags that identify the visit. A consistent naming convention matters more than clever values: use the same spelling for the same campaign every time, and decide in advance whether a field means a campaign, an ad group, or an individual ad.

A practical Google Ads convention is:

  • Medium set to paid search
  • Source set to Google
  • Campaign set to the campaign name
  • Term set to the ad group name
  • Content set to the specific ad

Check one tagged URL in a browser before launch. Confirm the parameters survive the redirect to the landing page and that capitalization and hyphens are consistent across ads that should roll up together.

2. Install the attribution snippet site-wide

Place the attribution snippet on the site using the platform instructions for your website system. The snippet's job is to read the tags on arrival, store them in the visitor's browser, and keep them available when the booking form is completed.

Before testing bookings, verify the snippet loads on the homepage, on the booking page, and on any page where a visitor might first land from an ad. A missing snippet on one template is enough to lose attribution for that entry point.

3. Let the booking carry the source fields

When a visitor books through the embedded form, the stored source fields travel with the booking. In a worked example, a visitor who clicks a paid-search ad for a construction-software demo and books a meeting would carry fields equivalent to:

  • Channel: Paid Search
  • Channel Drilldown 1: Google
  • Channel Drilldown 2: Scheduling Campaign
  • Channel Drilldown 3: Construction Industry Ad

Those drilldown values come from the tags placed on the ad, so the example only works if the campaign, ad group, and ad naming were set up in step 1. Test with a tagged URL, complete a test booking, and inspect the event before relying on the data.

4. Use the captured data in the CRM or a report

Once the fields sit beside the meeting record, use them in the way that fits your stack:

  • Open the event page in the scheduling account to inspect one booking's attribution
  • Forward the fields to a CRM such as Salesforce, Pipedrive, or HubSpot and build dashboards from the synced records
  • Export to a spreadsheet for a filterable table, or connect the data to a reporting tool for scheduled views

The decision value comes from joining the booking to later outcomes. A campaign that produces many meetings but no customers should not be judged the same as one that produces fewer meetings and more revenue.

Why persistence and landing-page capture matter

Three distinctions make this setup more reliable than reading parameters only at submission.

First, it records every source, not only paid search. A booking that arrived from a social ad, an organic search, or a referral link gets the same treatment, which prevents paid search from looking better simply because it is the only channel measured.

Second, it survives navigation. A visitor can land on the homepage from an ad, browse to a booking page, or leave and return later, and the original tags are still attached at booking time. That closes the common gap where parameters drop from the address bar during internal navigation.

Third, it records the first landing page and the group that page belongs to. For example, a visit to a scheduling feature page can be stored as that exact URL plus a features group, showing which site sections turn visits into meetings.

Three reports to build after capture

Leads by channel: Count bookings per month by originating channel. If most leads arrive through organic search while most budget goes to paid search, the report prompts a rebalancing review.

Customers by Google Ads campaign: Count new customers per month by the campaign that originated the booking. This separates campaigns that generate meetings from campaigns that generate paying customers, so budget can follow the latter.

Revenue by keyword: Total revenue from new customers segmented by the keyword behind the click. Keywords that drive traffic without revenue become candidates for reduced spend, while keywords tied to valuable customers become candidates for more investment.

Pre-launch checklist

Use this checklist before scaling spend on the data:

  • Every Google Ads destination URL carries the five agreed UTM fields
  • The attribution snippet is present on all landing and booking templates
  • A test booking from a tagged URL shows the expected channel and drilldown values
  • A test booking after internal navigation still shows the original tags
  • The landing page and landing page group appear on the booking record
  • CRM fields exist for channel, campaign, ad group, keyword, and landing page before syncing
  • One report each for leads by channel, customers by campaign, and revenue by keyword is built and spot-checked against a known booking

If a test booking fails any check, fix the tag, snippet placement, or field mapping before drawing budget conclusions from the reports.

UTM field map for Google Ads
FieldRecommended valuePurpose
UTM MediumPaid searchIdentifies the channel type
UTM SourceGoogleIdentifies the platform
UTM CampaignCampaign nameRolls bookings up to campaign level
UTM TermAd group nameRolls bookings up to ad group level
UTM ContentSpecific adIdentifies the individual ad

Values are a recommended convention from the captured guidance; the exact values are chosen by the advertiser.

Reports enabled by captured booking data
ReportSegmentDecision it supports
Leads by ChannelMarketing channelRebalance spend toward channels producing leads
Customers by Google Ads campaignGoogle Ads campaignScale campaigns producing paying customers
Revenue by KeywordKeywordInvest in keywords tied to revenue

Reports require booking data synced to a CRM, spreadsheet, or reporting tool.

Frequently asked questions

What is the shortest path from a Google Ads click to a booking record with source data?

Add UTM parameters to the ad destination, install the attribution snippet on the site, and let it attach source fields to the embedded booking form. The captured fields can then be viewed on the booking event or forwarded to a CRM, spreadsheet, or reporting tool.

Why can UTM data disappear before a meeting is booked?

Native tracking that only reads parameters still present at submission can miss the source when a visitor lands on the homepage and later navigates to a booking page. Storing the parameters in the browser preserves them across navigation and a later return visit.

What landing-page information is useful beyond campaign names?

Alongside campaign fields, the original landing page URL and its page group can be stored. That shows whether a feature page, blog post, or dedicated landing page produced the booking.