FareHarbor to Google Ads
FareHarbor bookings, reported back to Google Ads.
A tour or activity booking is often decided same day, for a specific date, by a specific group size. We connect the paid booking, not the abandoned cart, to Google Ads.
- 10% of ad budget, $600 a month minimum
- No contracts, month to month
- 30 day guarantee on the first month
The workflow
What connects a FareHarbor booking to a Google Ads bid.
The identity match
FareHarbor's widget can often be embedded directly on your own site rather than sending the visitor away to a separate domain, which usually keeps the click identifier available on the page. Where it does not, we fall back to a hashed email from the booking confirmation, checking each operator's actual setup rather than assuming the widget behaves the same way everywhere.
The field map
A FareHarbor booking carries a tour or activity name, a headcount, and a paid total, all of which are different for a group of two and a group of twelve. We send the real paid amount as the conversion value, not a flat number, since a flat number would treat a private charter the same as a single seat on a shared tour.
Where the data enters
FareHarbor makes an API available to operators and approved partners for pulling booking data, which is the path we use to feed Google Ads' offline conversion import. Exact access and fields can change, so we confirm current API access before building, rather than assuming last season's setup still applies this season.
Paid, not started
Group bookings often get started while people are still deciding on a date, then abandoned. We trigger on payment completed, not on a booking that was only begun, so an unfinished checkout does not count as a sale, even when it sits in the cart for days while a group finalizes plans.
What we check before an operator trusts this.
Season handled honestly
A whale watching or boat tour business can see almost all its revenue in a few months a year. We do not smooth that over. The Google Ads data reflects the real season, so you are not chasing a flat monthly budget that does not match demand, and your off season spend is not judged against your peak season results.
Headcount reflected in value
A booking for one person and a booking for a full group charter are not the same result. We send the actual paid total, so your ad account can eventually favor the keywords bringing in bigger groups, the kind of booking that actually moves the needle for a seasonal operator.
Weather cancellations excluded
Tours cancelled or refunded for weather should not sit in Google Ads as a permanent win. We build the sync to reflect a cancellation instead of reporting a sale that never happened, since a rough season for weather can otherwise quietly distort months of data.
Re-tested after FareHarbor updates
FareHarbor's widget and API shift on a timetable that has nothing to do with tour season or ours. The moment one of them changes, bookings get sent back through the pipeline before your numbers are trusted again.
How we build it.
01
Audit your booking widget
We start by checking how your FareHarbor widget is actually embedded on the page, whether the click identifier survives that setup, and what your current API access allows us to pull from it.
02
Build and test the feed
A solo seat on a shared tour and a private charter for twelve should not report the same way, so the build watches for payment completed, headcount and all. Real bookings from your own calendar get run through until the totals, dates, and group sizes all check out.
03
Hand off a plain record
Your booking staff keeps a copy showing which event counts and what it is worth, enough on its own to answer most questions without calling us.
FareHarbor and Google Ads conversions, answered.
Yes. The conversion fires when the booking is made and paid, regardless of the tour date. A booking made in January for a July trip still counts when it is booked, not when the group actually shows up for the tour.
It does not count. We trigger strictly on payment completed, so a group still comparing dates or prices does not show up in Google Ads as a sale until they actually pay.
Yes, and it should. We do not average your data out. If your season runs three months a year, that is exactly what the Google Ads conversion data will show.
We send the actual amount paid for the booking, which already reflects headcount and any per person pricing, so a larger group naturally reports a larger conversion value.
FareHarbor ships changes to its widget and API on a schedule tied to nothing we control. Bookings get sent through the feed again the moment something shifts, and the numbers get confirmed before your operation leans on them.
See which ads actually fill your FareHarbor booking calendar.
Tell us how your booking widget is set up, how your season runs, and roughly how big a typical group booking is. A free, plain-language proposal comes back within one business day.