Conversion Tracking lets you point your property site at your own Google Analytics 4, Google Tag Manager, and Meta (Facebook) Pixel accounts, and quietly fixes the tracking problems that otherwise make your booking numbers untrustworthy. It is for owners and marketers who want clean, accurate funnel data they can act on.
What it does #
Out of the box, a HomeRunner site reports to HomeRunner’s default analytics tags. Conversion Tracking does two things on top of that:
- Routes tracking to your own accounts so the data lands where your marketing team already works.
- Repairs the accuracy of the events themselves so the numbers in GA4 and Meta match what actually happened on your site.
It covers the full booking funnel: someone viewing a property, selecting dates and getting a quote, opening checkout, and completing a reservation, plus form-based leads such as contact and inquiry submissions.
Setting your tracking IDs #
Open the module’s settings panel and fill in the IDs you want the site to use. Each one is optional. When you set it, it replaces the default HomeRunner tag; when you leave it blank, nothing changes.
- GA4 Measurement ID (looks like
G-XXXXXXXXXX) sends all ecommerce and funnel events to your own Google Analytics 4 property. - GTM Container ID (looks like
GTM-XXXXXXX) loads your own Google Tag Manager container, so your tag team can manage everything from there. - Facebook Pixel ID turns on Meta Pixel events: ViewContent, InitiateCheckout, Purchase, and Lead.
Click Save Tracking Settings when you are done.
Privacy and consent #
- Consent Mode v2 sets Google’s
ad_storageandanalytics_storageto denied by default, until your consent banner grants them. Turn this on if you operate a cookie-consent banner and need to honor it before any tracking fires.
Cleaner funnel and conversion events #
These fixes are what make your reports trustworthy. Several are on automatically; a few are opt-in so they do not disrupt dashboards you have already built.
Accurate purchase counting #
The module removes duplicate purchase events so a single completed booking is counted once, not several times, and it normalizes the events fired from the property explorer so search and browse activity reports consistently.
Track Purchase on Inquiry #
By default the purchase conversion fires on a confirmed reservation. Turn Track Purchase on Inquiry on if your booking flow runs on inquiries (request-to-book) and you want the conversion counted at the inquiry stage instead.
GA4 Ecommerce Shape #
By default, GA4 receives taxes and every fee (cleaning, pet, and so on) as line items inside the ecommerce items[] array, which makes GA4 treat them as products and inflates your Item Revenue reports.
- Clean items[] array sends only the property as an item. Taxes stay in the standard tax field and fees roll up into a separate fees total.
- Emit per-fee custom params additionally exposes each fee (for example
cleaning_fee,pet_fee) as its own value, so you can register them as custom dimensions in GA4.
This section is off by default so your existing GA4 dashboards keep matching historical data. Turn it on once your team is ready for the cleaner shape.
Extra funnel events #
- Fire add_to_cart on quote emits GA4
add_to_cart(and Meta AddToCart) the moment the booking widget returns a successful quote, before checkout opens. This is how you measure drop-off between selecting dates and starting checkout. - Fire generate_lead on Gravity Forms submission emits GA4
generate_lead(and Meta Lead) whenever any Gravity Form is submitted successfully, including contact, inquiry, and concierge forms. The form ID is attached so you can break leads down by form in GA4.
See your results #
The module also feeds a funnel tracker that surfaces a summary widget on your WordPress dashboard, so you can spot-check the funnel without opening GA4.
For the full list of Toolkit modules, see the Toolkit Overview. If guest math in the booking widget looks off, that is handled automatically and described in Toolkit: Under the Hood.