Google Analytics 4 (GA4) helps you understand how visitors find your website and which visits lead to online bookings. When your GA4 property is connected to the relevant FareHarbor booking flows, you can measure activity from your website through to a completed purchase.
This guide covers affiliates who use FareHarbor booking links, buttons, or widgets on their own websites. If you use a custom API booking experience, contact us to discuss your tracking setup.
FareHarbor handles connecting your GA4 Measurement ID to the relevant operator Dashboards. FareHarbor cannot provide testing, make test bookings, or verify that tracking is working on your behalf. You must arrange tracking validation with your own website developer or analytics team.
How tracking works
Your website and the FareHarbor booking flow work together to send information to your GA4 property:
- A customer visits your website, where your Google tag records their visit.
- They open a FareHarbor booking flow from your site.
- FareHarbor sends supported booking events to the connected GA4 property.
- When they complete an online booking, a
purchaseevent can record the transaction.
A correctly configured Lightframe integration and analytics setup help connect website activity with booking activity. Your website developer or analytics team should check whether your website’s GA4 client ID is preserved through the booking flow.
Use the same Measurement ID on your website and in the operator’s FareHarbor configuration. Consent restrictions, blockers, or integration issues can interrupt tracking, so enabling cross-domain tracking alone does not guarantee continuity for every visitor. A matching client ID alone does not guarantee correct session attribution.
Affiliate tagging and GA4 attribution serve different purposes. Your affiliate booking link identifies your business in FareHarbor for booking and commission reporting. GA4 uses the available visit and campaign information to report which marketing channels contributed to a purchase.
What you can measure
Depending on the booking flow and your configuration, FareHarbor can send events such as:
| Event | What it tells you |
|---|---|
view_item_grid |
A customer viewed a selection of activities. |
view_search_by_date |
A customer searched for activities by date. |
view_calendar_single_item |
A customer viewed the calendar for an activity. |
view_item_description |
A customer viewed an activity description. |
view_book_form |
A customer reached the booking form. |
add_to_cart |
A customer added a booking to the cart, where a cart is used. |
purchase |
A customer completed an online booking. |
Not every journey includes every step. For example, a link may take a customer straight to a calendar or booking form.
Purchase information includes a transaction ID, value, and currency. The purchase event’s value relates to the booking, not your affiliate commission. Together with your website data, these events can help you identify popular activities and understand where customers leave the booking process.
Set up GA4 for your affiliate website
-
Set up GA4 on your website. Install your Google tag and find the Measurement ID for your web data stream. It begins with
G-. - Check your FareHarbor website integration. Make sure the FareHarbor Lightframe integration is installed and your booking buttons work.
- Prepare your request. Include your affiliate company name, website URL, Measurement ID, and links to the operators and activities you promote.
-
Follow the setup route for your partnership:
- Direct affiliate partnerships, outside FHDN marketplace links: You must obtain approval from each tour operator before FareHarbor can add your GA4 Measurement ID to their Dashboard. Contact channelsupport@fareharbor.com with the operator’s approval and your setup details.
- FHDN marketplace links: Send your activity list and Measurement ID to strategicpartnerships@fareharbor.com so the team can coordinate setup. You do not need to contact each operator yourself as part of this request. FareHarbor Help Center
-
Configure unwanted referrals. Add your root domain and
fareharbor.comto your GA4 property’s unwanted referral list, following the GA4 setup guide. - Arrange tracking validation. Your website developer or analytics team should review your Google tag, consent settings, Lightframe integration, and the relevant GA4 settings.
Your GA4 Measurement ID must be added to each relevant operator’s FareHarbor Dashboard. When you add another operator, follow the appropriate setup route above.
You or your website provider are responsible for managing your website’s Google tag and consent setup. Having your Measurement ID added does not confirm that tracking works. Your own website developer or analytics team must validate it; FareHarbor cannot perform this testing or verification for you.
Understand differences between GA4 and FareHarbor
The purchase event’s value represents the full amount paid by the customer, including taxes and fees, not your affiliate commission. Your commission is calculated separately according to your agreement with the operator. Cancellations and refunds may affect your earnings.
Use GA4 to assess website and marketing performance. Use FareHarbor’s Reports for affiliates to review bookings and commission amounts.
When comparing booking counts, use the same date range, time zone and booking scope. A report based on the activity date will differ from one based on when customers booked.
GA4 can record fewer purchases because customers decline analytics cookies, use blockers, or encounter a tracking interruption. A booking can still be correctly tagged to your affiliate in FareHarbor when GA4 does not record it.
Bookings entered manually in a Dashboard are outside the website journey described here. Links opened directly from emails, social media or QR codes also follow a different path.
Check that your GA4 is connected to an operator and tracking bookings
Your website developer or analytics team can use the checks below to see whether the operator’s booking flow sends events to your GA4 property.
These checks must be carried out by you or your own technical team. FareHarbor can confirm whether your Measurement ID is saved in the relevant Dashboard, but cannot test or verify that events are reaching your property or being correctly attributed.
Confirm your Measurement ID is on the operator’s Dashboard
Find your Measurement ID in your GA4 property under Admin > Data streams > select your web stream. It begins with G-.
For a direct partnership, ask the operator to go to Settings > Analytics & Tracking in their FareHarbor Dashboard and confirm that your exact GA4 Measurement ID is listed.
If you use FHDN marketplace links and do not have contact with the operator, ask strategicpartnerships@fareharbor.com to confirm that your ID has been added for the operators on your submitted list.
Confirm this for each relevant operator. Your ID being connected to one operator does not confirm that it is connected to another.
Having your ID saved confirms only that it is listed in the Dashboard. Your website developer or analytics team should then check that events are reaching your GA4 property.
Run the check in Chrome
- Open the page on your website that contains the operator’s FareHarbor booking button. Use a browser profile with ad blockers disabled for this test.
- Right-click the page and select Inspect, then open the Network tab. Select All and enable Preserve log to keep requests visible throughout the booking process.
- Reload the page and accept analytics cookies where applicable.
- Keep the Network log open. Open the operator’s Lightframe and go through a few booking steps, such as viewing an activity’s calendar and opening its booking form.
- Enter
collectin the Network filter. Select a GA4 request, commonly sent to agoogle-analytics.com/g/collectaddress. - Under Payload or Query String Parameters, check the parameters listed below.
- To check client ID preservation, compare the
cidvalue on a website event sent before you opened the Lightframe with thecidvalues on booking events. Compare events sent to the same Measurement ID during the same browser journey. If you complete a test purchase, check the purchase event’scidvalue too.
| Parameter | What to check |
|---|---|
tid |
Confirm that it matches your affiliate GA4 Measurement ID. |
en |
Check the event name. Look for a booking event triggered during your test, such as view_book_form. |
dl |
Review the page location, where available, to help identify where the event occurred. |
Matching cid values indicate that the compared events use the same client ID. They do not, by themselves, confirm correct session attribution. A page view from your website alone does not confirm that Lightframe booking events are being sent.
Understand the result
| What you see | What it means |
|---|---|
| A booking event with your Measurement ID and a successful request status | Your browser sent that booking event to your GA4 destination during this test. You should also check that it appears in your property. |
| Requests with only the operator’s Measurement ID | These show activity being sent to the operator’s property. They do not confirm that your affiliate property is receiving events. |
| No booking requests matching your affiliate ID | Ask FareHarbor to confirm that your ID is saved. Your website developer or analytics team should then check the tracking settings and website integration. |
If your Measurement ID is saved but booking events are missing, your website developer or analytics team should confirm that your website uses the same ID, analytics consent has been granted for the test, and ad blockers are disabled.
They should also review your Lightframe integration and check that the Calendar, item grid, or book button is added to multiple websites setting is configured as described in the GA4 setup guide. The operator or the FareHarbor team handling your setup can confirm the saved Dashboard setting.
This browser check covers the tested step. It does not prove that all purchases are recorded or correctly attributed, and it does not show events sent only from a server.
Confirm events arrive in your GA4 property
Open Realtime in your GA4 property while testing. Look for booking events, such as view_book_form, to confirm that booking activity is reaching your property. Website page views alone do not confirm this. If debug mode is enabled for your test, you can also check events in DebugView.
Purchase tracking can only be verified after a completed online booking. If you can arrange a test booking directly with an operator, your website developer or analytics team should confirm that a purchase event reaches your GA4 property. Where booking details are available, they should compare the transaction ID, value, and currency with those details.
If you cannot arrange a test booking, including where you use FHDN marketplace links without direct operator contact, you can still check the earlier booking steps and monitor your property for purchase events from actual bookings.
Reaching the booking form alone does not confirm that purchase tracking works. FareHarbor cannot provide a test booking or validate tracking on your behalf. Arrange validation with your own website developer or analytics team.
FAQ
Why do I see affiliate bookings in FareHarbor, but no purchase events in GA4?
FareHarbor commission reporting and GA4 purchase tracking are separate systems.
A booking can be tagged to your affiliate in FareHarbor, while GA4 still needs your Measurement ID connected on each relevant operator’s Dashboard, a matching Google tag on your website, and a completed online booking journey that analytics is allowed to record.
If your Measurement ID is not connected on the relevant operator’s Dashboard, that booking flow will not send events to your property through the integration described in this guide.
Does each operator need to have my GA4 Measurement ID added?
Yes. GA4 booking events are configured on the operator’s Dashboard where the booking is completed. Your affiliate tag alone does not automatically connect every operator’s booking flow to your GA4 property.
If you promote many operators, include each operator’s shortname and activity links in your setup request.
For direct affiliate partnerships outside FHDN marketplace links, approval from each operator is required before FareHarbor can add your Measurement ID.
For FHDN, send your list and Measurement ID to strategicpartnerships@fareharbor.com.
The Calendar, item grid, or book button is added to multiple websites setting should also be reviewed so that tracking is limited to the intended website. This you can ask channelsupport@fareharbor.com to check.
Can FareHarbor send purchases to my GA4 property automatically from my affiliate ref or ASN?
No. Your affiliate ref or ASN identifies bookings for FareHarbor reporting and commission. It does not replace GA4 configuration on each relevant operator’s Dashboard.
It should not be used as a unique per-visitor identifier for Google Ads conversion matching.
What does the “multiple websites” option do in the FareHarbor Dashboard’s Analytics & Tracking section?
When Calendar, item grid, or book button is added to multiple websites is enabled, analytics for that Measurement ID runs only when the underlying host website uses the matching Measurement ID.
Without that setting, a Measurement ID connected on a Dashboard may also receive activity from booking flows opened on other websites.
If you run more than one website with different GA4 Measurement IDs, each relevant ID needs its own analytics entry. Review the multiple-websites setting for each entry so that tracking is limited to the intended website.
Does purchase value in GA4 show my commission or the booking value?
The purchase event’s value relates to the booking. It does not represent your affiliate commission, which is calculated separately according to your agreement with the operator or the applicable FHDN terms.
Use GA4 for conversion and marketing performance. Use FareHarbor affiliate reports for commission amounts.
I promote operators through FHDN and through direct affiliate agreements. Does setup differ?
Your Measurement ID needs to be connected on each relevant operator’s Dashboard, but the request process differs:
- Direct affiliate partnerships outside FHDN marketplace links: Obtain approval from each operator before FareHarbor can add your ID. Contact channelsupport@fareharbor.com with that approval and your setup details.
- FHDN marketplace links: Send your activity list and Measurement ID to strategicpartnerships@fareharbor.com so the team can coordinate setup.
Include your website URL, Measurement ID, affiliate company name or shortname, and the operators and activities you promote.
I use one affiliate identifier across more than one website. Can each site send purchases to its own GA4 property?
Yes, provided each website uses the Measurement ID for its intended GA4 property, that same ID is connected on the relevant operator Dashboards, and the multiple-websites setting is configured appropriately.
Your shared affiliate identifier still groups bookings under the same affiliate in FareHarbor. Separate GA4 Measurement IDs allow each website’s analytics to be sent to its intended property.
If two websites share both the same affiliate identifier and the same Measurement ID, their purchase events will be sent to the same GA4 destination.
Why do I see booking-flow events in GA4, but not purchase?
Booking-flow events and purchase are separate steps. Flow events can appear when a visitor opens calendars or forms. The purchase event is triggered when an online booking is completed and the confirmation page appears, provided analytics is allowed for that visit.
Possible reasons for missing purchase events include:
- The Measurement ID is not connected on the operator Dashboard used for that booking.
- The host website and FareHarbor configuration do not use the same Measurement ID.
- The multiple-websites option is enabled, but the host page does not load the matching ID.
- Consent, blockers, or browser settings prevented tracking for that visit.
- The booking was completed outside the online website journey.
Your website developer or analytics team should check the booking flow and monitor for purchase events from completed online bookings. Where booking details are available, they should compare the transaction ID, currency, and value.
If you cannot arrange a test booking, monitor for purchase events from actual bookings. Earlier booking events alone do not verify purchase tracking.
Can FareHarbor test or verify my tracking?
No. FareHarbor can add your Measurement ID through the appropriate setup process and confirm that it is saved in the relevant Dashboard.
FareHarbor cannot provide testing, make test bookings, or verify that events are reaching your GA4 property or being correctly attributed. You must arrange these checks with your own website developer or analytics team.
Can I use Online ref or UTM values to match a booking to the original ad click?
UTM parameters help GA4 identify campaign traffic. However, campaign attribution through the booking flow depends on your tracking configuration, consent, and the information available for that visit. Your analytics team should validate this rather than assume it is preserved.
Online ref identifies the booking source in FareHarbor. It is not a substitute for GA4 purchase setup or a unique per-visitor key for Google Ads conversion matching.
Use your GA4 and Google Ads integration for marketing attribution. Use FareHarbor affiliate reports for booking and commission reconciliation.
Will moving to an API booking integration solve Google Ads purchase tracking without configuring each operator?
An API booking experience requires its own analytics implementation and validation. It should not be treated as an automatic solution to purchase tracking.
The Dashboard and Lightframe instructions in this guide apply to the website booking flow described here. If you use a custom API booking experience, contact us to discuss the supported setup and arrange validation with your own developers or analytics team.
What should I prepare before contacting FareHarbor?
Send:
- Affiliate company name and shortname.
- Website URL.
- GA4 Measurement ID.
- Operator shortnames and activity links you promote.
- Whether the request is for a direct affiliate partnership or FHDN.
- For direct affiliate partnerships outside FHDN marketplace links, confirmation that each operator has approved adding your Measurement ID (contact us with the Tour Operator in copy)
After the connection is added, arrange for your website developer or analytics team to review your Google tag, unwanted referrals, and consent setup, and validate the available booking and purchase events before relying on the data for paid media. FareHarbor cannot perform this validation on your behalf.