turnoutCulture

How it runs

Google Analytics & conversion tracking

Understand discovery, checkout and enquiries without exporting guest contact details.

What is tracked

  1. 1Public page visits without search text or private URLs
  2. 2Catalogue searches, without the words someone typed
  3. 3Google and WhatsApp sign-in events
  4. 4Checkout starts and submitted bookings
  5. 5Successful space enquiries, class enquiries and event proposals
  6. 6Successful event import prefills, without the pasted announcement

Payment reporting

A pending UPI booking is booking_submitted, not purchase. Immediate confirmed bookings can send purchase with a random analytics reference unrelated to the entry pass. Later organiser payment confirmations are not reported as GA purchases by the current browser implementation; use the workspace for confirmed ticket totals.

Activate Google Analytics

  1. 1Connect a Google Analytics property or configure its public Measurement ID with the Turnout team.
  2. 2Publish after changing tracking settings.
  3. 3Check Realtime and DebugView using a test visit.
  4. 4In GA, choose which successful lead events are key events. Do not count pending UPI bookings as paid sales.

Tag Manager and privacy

Direct GA4 is supported. A separate Tag Manager container is not installed, preventing accidental duplicate tracking. Review consent and Enhanced Measurement settings in Google Analytics before collecting marketing data. Phone numbers, emails, payment references, receipts and entry QR values must never go to analytics.

Was this guide helpful?