How to capture Facebook Ads data in OnceHub
A Facebook campaign can look healthy in the ads manager while your OnceHub calendar fills with meetings you cannot trace back to a specific ad. The gap is usually not the scheduler — it is the missing link between the ad click and the booking record. This guide walks through tagging your ads, installing a browser-side attribution layer, and reading the resulting booking data so you can tell a free-consultation ad from a customer-story ad.
Why bookings without source data stall optimization
Clicks and impressions tell you what happened on the ad platform. They do not tell you which ad produced a scheduled meeting. If your OnceHub bookings arrive with no campaign context, every scaling decision becomes a guess: you cannot tell whether the consultation offer or the success-story creative is doing the work.
The fix has three parts, and all three are needed: tagged ad URLs, a script that remembers the tag while the visitor moves around your site, and a scheduler that stores the resulting values with the booking.
Step 1 — Tag every Facebook ad URL
UTM parameters are short text fragments appended to a destination URL that identify the traffic source for analytics tools. Without them, nothing downstream has a campaign name to record.
Take a landing page such as https://roipaths.com/integrations/oncehub. A tagged version might read: https://roipaths.com/integrations/oncehub?utm_medium=paidsocial&utm_source=facebook&utm_campaign=brand-campaign.
Use this convention across the account so reports stay comparable:
- UTM Medium: Paid social
- UTM Source: facebook
- UTM Campaign: the campaign name
- UTM Term: the ad set the ad belongs to
- UTM Content: the specific ad
Keep the naming consistent between the ad platform and the URL. A campaign renamed in one place but not the other produces two rows in reporting instead of one.
Step 2 — Install the attribution script on your site
The second step is placing the tracking script on your website. It is a small piece of code whose job is to record where visitors arrive from. The snippet is typically obtained from your attribution tool's account dashboard and added to the site's global header or footer so it loads on every page, not just the landing page. Placement differs by platform, and setup instructions exist for the major builders including WordPress, Wix, Squarespace and Webflow. Once installed, the script works in the background: it captures attribution data and holds it in the visitor's browser until that person completes a booking through your OnceHub widget. Nothing needs to be clicked or confirmed by the visitor.
Step 3 — Confirm the data lands on the booking
With tagging and the script in place, source information is collected for every visitor, including those arriving from Facebook campaigns.
When a visitor submits the OnceHub widget, the attribution values — network, campaign, ad set, ad name and similar fields — are passed into OnceHub and stored alongside the booking. That stored record is what makes per-ad reporting possible later.
Checklist before you trust the numbers
Run this check once, right after setup, rather than discovering a gap a month into spend:
- Open one live ad URL and confirm the UTM string is present in the address bar.
- Click from the ad landing page to a separate booking page, then complete a test booking.
- Open that booking in OnceHub and confirm the campaign and ad fields are populated, not blank.
- Repeat with a second ad that uses a different utm_source spelling (for example fb instead of facebook) and confirm both group under the same channel.
- Only then start comparing cost per booking across campaigns.
If step 3 returns blanks, the problem is almost always one of two things: the ad URL was never tagged, or the visitor's source was recorded only on the landing page and lost when they navigated to the booking page. Fix the tagging or the persistence layer first, then re-run the test booking before drawing conclusions from the numbers.
What you can do with the captured data
Once the values sit on the booking record, several routes are open:
- Push bookings into a CRM such as Salesforce, Pipedrive or HubSpot and use its reporting to count leads, conversions and revenue by campaign.
- Export to Google Sheets or Excel through an automation tool, then connect the sheet to Looker Studio or Power BI for visual reporting.
- Add the ad fields to new-lead notification emails so sales has context before the call.
- Pass the data into a billing platform such as Stripe or Square to connect revenue to specific campaigns or ad sets.
Where same-page-only tracking breaks
Scheduler-native UTM tracking usually only holds when the visitor submits the booking form on the same page where they first arrived. Consider a visitor who clicks an ad, lands on your pricing page, then follows a link to a dedicated scheduling page with an embedded OnceHub widget. By the time the form is submitted, the original campaign tag is gone and the booking looks unattributed.
A browser-stored approach behaves differently: the parameters persist while the visitor browses, and even if they leave and come back later, the original source is still attached when the booking is submitted. That persistence is the difference between a report with gaps and one you can act on.
Messy UTM values and landing page context
Two data-quality problems show up in almost every ad account.
The first is inconsistent naming. If one campaign uses utm_source=facebook and another uses utm_source=facebook-ads, a naive report treats them as separate sources. A cleaning layer that recognizes them as the same source and groups both under Paid Social keeps channel totals honest.
The second is missing page context. Recording the visitor's first landing page and its page group — for example the full URL of a pricing page plus the broader /pricing group — shows which pages and content categories attract leads, not just which ads do.
Three reports worth building first
Once booking data reaches a CRM or analytics tool, three example reports make a practical starting point.
Leads by channel compares Paid Social against Paid Search, Organic Search and other channels, so you can see whether Facebook spend is earning its place in the budget mix.
Leads by network breaks Facebook traffic down across placements such as Feed, Stories and Reels, which helps you shift budget toward the placement producing the most bookings and reduce cost per lead.
Leads by campaign shows monthly lead volume per campaign, counting booked meetings rather than form fills, so budget follows campaigns that consistently convert.
Wrap-up
If the question you keep asking is how many bookings, leads and customers a given Facebook ad produced, the answer depends on three things working together: tagged URLs, a script that remembers the source across pages, and a scheduler that stores the values with the booking. Get those in place and your CRM or analytics tool can answer the question with data instead of intuition. Before committing budget, confirm the current trial length, setup time and pricing terms directly with the tool provider, since these vary by plan and change over time.
| UTM parameter | Recommended value | Captured with booking | Report that uses it |
|---|---|---|---|
| utm_medium | Paid social | Channel grouping | Leads by channel |
| utm_source | Network / source | Leads by network | |
| utm_campaign | Campaign name | Campaign | Leads by campaign |
| utm_term | Ad set name | Ad set | Campaign and ad set breakdowns |
| utm_content | Specific ad | Ad name | Ad-level comparison |
Values reflect the recommended tagging convention and the fields described as passed into OnceHub; exact field labels in your OnceHub account may differ.
| Symptom | Likely cause | Check |
|---|---|---|
| Booking shows no campaign data even though the ad URL is tagged | Source recorded only on the landing page and lost during navigation to the booking page | Complete a test booking after navigating between pages |
| Same source appears as two rows in reporting | Inconsistent utm_source values such as facebook and fb | Compare raw utm_source values across campaigns |
Diagnostic guidance based on the described tracking behavior; confirm against your own test booking.
Frequently asked questions
Does the source survive if a visitor lands on one page and books on another?
With a browser-stored approach, yes. The parameters are held in the visitor's browser, so a visitor who moves between pages — or leaves and returns later — still has the original source attached when the OnceHub booking is submitted. Scheduler-native UTM tracking that only reads the current page will lose it.
What happens if some campaigns use utm_source=facebook and others use utm_source=fb?
A cleaning layer can recognize both as the same source and group them under Paid Social, so channel reporting stays accurate instead of splitting one source into two rows.
Which fields end up on the booking?
Network, campaign, ad set and ad name are among the values passed into OnceHub and stored with the booking, along with the visitor's initial landing page and its page group.
Where can the booking data go next?
Into a CRM such as Salesforce, Pipedrive or HubSpot for reporting; into Google Sheets or Excel via an automation tool and on to Looker Studio or Power BI; into new-lead notification emails; or into a billing platform such as Stripe or Square to tie revenue to campaigns.