FareHarbor · Conversion tracking
FareHarbor conversion tracking that holds up
FareHarbor bookings open in the Lightframe overlay on your site or on a fareharbor.com page, and the purchase itself is recorded on FareHarbor's side. The Dashboard already offers GA4, Meta Pixel with Conversions API, and AdRoll, so the usual failure is not missing tracking. It's a skipped unwanted-referral setting, a second Purchase from your own GTM, or Google Ads reading GA4 imports nobody has checked.
✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.
Written guarantee
95%+ conversion accuracy on FareHarbor
Measured against your own order records at handover. Miss it and we keep working at no cost until it’s met.
Built on — and certified for — the platforms that matter
Stape
Pro Partner
Meta
Tech Provider
Tag Manager
TikTok
Events API
Microsoft
UET Partner
CAPI Partner
CAPI Partner
Built on the same partner stack used by enterprise DTC brands.
By the numbers
No fake testimonials.Just the math.
70+
Platforms supported
Shopify · Woo · Magento · BigCommerce · 65 more
8+ / 10
Meta EMQ guaranteed
in writing — keep working free until hit
2–4d
Build to live
accurate data flowing within 7 days
$0
Monthly fees, ever
one-time fixed price · you own the stack
400d
Cookie lifetime
max RFC 6265bis allows · 57× Safari ITP
9
Ad channels covered
Meta · Google · TikTok · MS · LI · Pin · Snap · Reddit · X
95%+
Tracking accuracy
verified vs Stripe · GA4 · ad-platform reports
30 min
Free founder call
no SDR · no pitch deck · written remediation plan
Every figure above is either a commitment we put in writing or a countable fact. What your own setup is losing is not on this list, because we haven’t measured it yet — that happens on the call, against your own order records.
Real clients · real videos · real outcomes
Don’t take our word for it. Watch the receipts.
Founders, marketers, and agency owners describing the before-and-after of their FareHarbor tracking rebuild — in their own words, on camera.
What goes wrong on FareHarbor
fareharbor.com showing up as the source
FareHarbor states the unwanted-referral setting in GA4 is mandatory. Skip it and the booking is credited to FareHarbor, not your ad.
Two Purchase events for one booking
The native Meta pixel and CAPI fire Purchase on confirmation. A GTM tag on your site doing the same thing doubles it.
One pixel per Dashboard
Operators with several brands or ad accounts can't split them inside FareHarbor, so one pixel ends up carrying everything.
Google Ads trusting an unchecked GA4 import
FareHarbor recommends importing GA4 purchases into Google Ads. If GA4 is wrong, Google Ads inherits it.
Architecture
What FareHarbor actually lets you do
From FareHarbor's analytics help documentation.
Step 1
Native GA4 from the Dashboard
Set under Settings > Analytics & Tracking. Sends ecommerce data including purchase, and FareHarbor is added as an Editor on your property.
Step 2
Unwanted-referral configuration
Required, per FareHarbor. Without it, attribution breaks at the booking step.
Step 3
Native Meta Pixel with Conversions API
Purchase standard event on the confirmation page only, one pixel per Dashboard.
Step 4
Google Ads via GA4 import
FareHarbor's recommended route for purchase conversions.
Step 5
Your site GTM alongside
Allowed, but FareHarbor advises adding pixels in the Dashboard rather than through GTM.
Diagnostic sequence
Where FareHarbor tracking breaks, in diagnostic order
Ordered so the most common FareHarbor cause is ruled in or out first.
- 1
Check the unwanted-referral list in GA4
Then book once and see which source GA4 records. That single booking settles it.
- 2
Count Purchase events per booking in Meta
Native CAPI plus a site tag is the usual double.
- 3
Compare the GA4 import in Google Ads with FareHarbor
If Google Ads is off, trace whether the error is in GA4 or in the import.
- 4
Check value against the booking total
Taxes, fees and gratuity handling can make value disagree with what you were paid.
- 5
Check cancellations come back out
Weather cancellations are common in tours and stay counted unless reversed.
Source-of-truth validation
The QA evidence
Done with a paying booking through the Lightframe; preview mode proves nothing here.
- A live Lightframe booking showing your campaign, not fareharbor.com, as the source in GA4.
- Exactly one Purchase in Meta for that booking, server and browser deduplicated.
- The Google Ads GA4 import showing that same booking, once.
- Value checked against FareHarbor's total for that booking.
- A weather cancellation shown leaving the Meta and Google totals.
- A finished fortnight of bookings matched one at a time against each platform.
- Run again a month later and after any change in the FareHarbor Dashboard.
Straight talk
When you don't need this on FareHarbor
FareHarbor's native setup is better than most, and sometimes it's enough.
- If you run one brand, one pixel, the referral exclusion is in place and Meta shows one Purchase per booking, the native integrations may be all you need.
- If Google Ads is a small share of spend, getting the GA4 import right is a short job.
- If weather cancellations are rare and value already matches, a server rebuild adds little.
- A careful afternoon in the Dashboard fixes plenty of FareHarbor setups. We'll tell you if yours is one.
Who this is for
Honest about who we’re a fit for.
We don’t take every project. Here’s how to tell if we’re right for you.
You’re a great fit if…
- You run FareHarbor (or are migrating to it)
- You spend $5K+/month on paid ads (Meta, Google, TikTok, Microsoft, LinkedIn)
- Your reported ROAS doesn’t match what your bank account is saying
- You want to own your tracking stack — no monthly SaaS fees forever
- You have 2–4 days to do this once and never think about it again
Skip us if…
- You spend less than $500/month on paid ads (browser pixel is fine)
- You want a SaaS dashboard with monthly fees forever (Triple Whale, Hyros)
- You need attribution modeling — we fix the data foundation, not multi-touch reports
- You want a 6-month enterprise consulting engagement (we ship in 4 days)
- You expect us to manage your ad accounts (we don’t — that’s a different service)
If you’re still unsure,book the call anyway— we’ll tell you straight whether we can help.
What changes
One purchase per booking at every destination
Server-sideNative CAPI kept, duplicates removed.
Your campaigns credited, not fareharbor.com
8+ EMQReferral exclusions and cross-domain checked on a live booking.
Booking value that matches FareHarbor's records
DedupedIncluding group size, so a party of eight isn't scored like a solo traveler.
The event map on FareHarbor
Lightframe opened
Intent signal on your own page.
Booking purchased
The conversion, with value from FareHarbor's ecommerce data.
Party size
From the booking record, carried alongside value.
Booking cancelled or refunded
Reversed from FareHarbor's records.
Tour or activity booked
Item-level detail, so a sunset cruise and a walking tour aren't averaged.
Pick the package that fits your ad spend
Fixed-fee, no surprises. If your ad spend is meaningful,server-side tracking is what we recommend— it’s the only setup that survives iOS, Safari ITP and ad blockers.
Browser-side starter
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Save $18K–$120K over 5 years vs Triple Whale / Hyros
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations reversed everywhere
- Monitoring on every destination
Not sure which tier fits?Book a 30-min scoping call— we’ll tell you straight, no upsell pressure.
How it works
Built in 2–4 days. Accurate data within 7.
We deliver the entire 1st-party server-side stack in 2–4 business days. You start collecting accurate, deduped conversion data the moment it goes live — and within 7 days every signal is flowing cleanly to Meta, Google, TikTok and the rest.
Kickoff + audit
30-min call. We map your current pixels, GTM, dataLayer, consent setup, and ad-platform integrations. You get a written report of every leak.
Build the stack
Server-side GTM container deployed on your subdomain. Meta CAPI · Google EC · TikTok Events API · Microsoft UET wired. Identity match + dedup configured.
QA + go-live
Live-fire test purchases across every funnel step. Meta EMQ verified at 8+. Tag Assistant + Pixel Helper passes. Side-by-side report delivered.
Verify accuracy
Your data flows clean. Within 7 days every signal — Meta, Google, TikTok, Microsoft — is fully accurate. Notion runbook + Loom walkthrough handoff.
Got questions?
The honestanswers.
No buzzwords, no upsell. If we don’t know, we say so.
01FareHarbor already has Meta Conversions API. Why would we need more?
You may not. The usual problems are a second Purchase from your site's GTM, one pixel shared across brands, and cancellations never reversed. We check those before recommending anything.
02Why does GA4 credit our bookings to fareharbor.com?
The unwanted-referral setting is missing or incomplete. FareHarbor calls it mandatory, and one test booking confirms whether it's fixed.
03Should we add our Meta pixel through GTM instead?
FareHarbor advises using the Dashboard. Running both fires two Purchases unless they share an event ID, and that dedup has to be verified, not assumed.
04Is importing GA4 purchases into Google Ads good enough?
It's FareHarbor's recommended route and often fine. It inherits every GA4 error, so we check GA4 against bookings first.
05Can we send party size to the ad platforms?
Yes, alongside value. A group booking and a single seat are different outcomes, and bidding should know that.
Still have questions?Book a 30-min call— bring them all.
The call
What happens on your free 30-min call
No pitch deck, no SDR, no upsell pressure. Founder-led. Bring your ad-platform screens and yourFareHarbor setup — we’ll work through it together.
Min 1–5
We get the lay of your store
What you sell, what you spend on ads, who handles dev. Quick context-gathering — no questionnaire upfront.
Min 5–15
We audit your tracking live
Screen-share. We open your Meta Events Manager, GTM, and ad reports. You see exactly which conversions are leaking.
Min 15–25
We map a fix
What needs rebuilding, what stays. The exact FareHarbor setup we'd ship and what it would recover for you.
Min 25–30
Decide. Or don’t.
If we're a fit, we send a 1-page proposal in writing. If not, you walk away with a free remediation plan you can hand to anyone.
Get FareHarbor tracking checked against your bookings
Book a free 30-minute call. We look at your Dashboard integrations and ad accounts live and show you where bookings are being doubled or lost.
Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp
95% tracking accuracy guarantee
Free 30-min consultation · from $400 · 1st-party server-side
95% guarantee · from $400
