A technical guide to useful GA4 and Google Tag Manager events for virtual tours, including engagement, hotspots, leads and reporting.
- A tour view is not enough to understand whether the experience helped the customer.
- Track meaningful events such as scene changes, hotspot use, CTA clicks and lead actions.
- Use Google Tag Manager to standardize events and GA4 to analyze behavior.
- Measurement should respect consent and avoid personal or sensitive data.
Start with a measurement plan
Before adding tags, define the decisions the data should support. A hotel may need to know whether visitors explore rooms before opening the booking engine. A broker may care about property detail views and advisor contacts. A venue may want to see which spaces receive the most attention before a site-inspection request.
Without that context, analytics becomes a long list of events that nobody uses.
Events worth considering
- tour_view: the experience becomes visible and usable.
- tour_start: the visitor actively begins exploring.
- scene_view: a meaningful room or zone is opened.
- hotspot_click: an information, media or navigation hotspot is used.
- tour_cta_click: the visitor opens WhatsApp, a form, booking engine or property inquiry.
- tour_complete: a defined exploration threshold is reached.
Names and parameters should remain consistent across projects so reports do not fragment.
What Google Tag Manager contributes
GTM can receive structured events from the tour and translate them into GA4 events without hard-coding every analytics rule into the experience. Useful parameters may include the tour identifier, scene name, hotspot type, content category and CTA destination.
Do not send names, phone numbers, email addresses or free-text form responses as analytics parameters. Analytics platforms are not customer databases.
Build reports around questions
Useful analysis compares exploration with downstream actions. Which scenes appear most often before a booking click? Do mobile users abandon before the tour becomes interactive? Are people opening technical documents but not contacting sales?
Combine event counts with users, sessions and conversion rates. Raw clicks can be misleading when one visitor interacts repeatedly.
QA before trusting the data
- Use GA4 DebugView or an equivalent test environment.
- Confirm each user action sends one event, not several duplicates.
- Test desktop, mobile and embedded versions.
- Verify cross-domain behavior when the tour and website use different domains.
- Check consent behavior before analytics or advertising tags load.
- Document event names and parameters for future maintenance.
LUM360 measurement approach
We design tracking around the commercial role of the experience. The goal is not to prove that people clicked everywhere; it is to understand whether the tour helped visitors evaluate the space and move toward a useful next step.
Frequently asked questions
Do I need GTM to measure a virtual tour?
Not always, but GTM makes event governance and future changes easier when several platforms or conversion actions are involved.
Can GA4 measure which scenes people viewed?
Yes, when the tour sends structured scene events and those events are configured correctly in GA4.
Should every interaction be a conversion?
No. Reserve key events for actions that represent meaningful business progress, such as a booking, inquiry or qualified CTA.
Turn the idea into a useful digital experience.
Tell us about the space, audience and business goal. LUM360 can help define the right combination of web, visual production, analytics and immersive media.