Public analytics, kept narrow.

Optional public-site analytics

Google Analytics is denied by default and the Google tag does not load until you choose “Allow public-page analytics.” If allowed, Musa sends manual page views only for the public discovery page and public event-detail pages, plus two booking signals: that an online checkout started, and that an online booking was completed. Each count sends the order total, currency, ticket type names and codes, prices and quantities; a completed booking also sends the tax amount and a one-way code in place of the order number. Those signals are sent only after you have allowed analytics under this wording. If you allowed page analytics before these booking signals were added, that earlier choice keeps covering page views only; the booking signals stay off until you allow them again. Like any request to Google Analytics, every page view and booking signal also reaches Google with the technical details a browser shares with a website, such as its IP address and browser type. The privacy page itself is not measured.

Product analytics with PostHog

PostHog is a product analytics service, with data hosted in the United States. Musa uses it only if you allowed analytics in the choice panel that names PostHog. If you allowed analytics earlier, before PostHog was added, that choice keeps covering Google Analytics exactly as it described and PostHog stays off; you will be asked again on the public discovery and event pages, never during checkout, and PostHog starts only after you allow it there.

Once you have allowed it, PostHog helps Musa understand how people move from discovery to booking. It loads only on the public discovery page, public event pages, and the checkout and confirmation steps, and records four events: a discovery page view, an event page view with the public event and organizer identifiers, that an online checkout started, and that an online booking was completed. The last two also carry the amount, currency, ticket count, and each ticket type's identifier, price and quantity, plus a one-way code in place of the order identifier. Page addresses are cut to the site and path, and referrers to the site name. PostHog stores a random browser identifier on your device to tell visits apart; it is not linked to a name, email address, phone number, or account.

Like any request to PostHog, each event also carries the technical details a browser shares with a website: browser and operating system type and version, language, time zone, screen and window size, and random session and window codes. PostHog receives your IP address with each request; the project is set not to keep it.

We do not use session replay, screen recording, surveys, feature flags, experiments, or automatic click capture, and we do not build personal profiles. PostHog is never used to decide prices, payment, or ticket delivery.

If you allowed analytics in the choice panel that names PostHog before you started an online checkout, our server also sends one anonymous booking confirmation to PostHog once that booking is complete: the amount, currency and number of tickets, tied only to a random code from your browser. It never includes your name, email, payment details, order number or address. If you did not allow analytics, or allowed it before PostHog was added, no booking confirmation is sent.

To withdraw, choose Keep analytics off from the Analytics settings control on a public event page. That turns off PostHog together with Google Analytics: PostHog makes no further requests, no booking confirmation is sent afterwards, and the PostHog identifier stored on your device is removed. PostHog stays off for that page until it is reloaded.

What stays out

We strip query strings and do not send checkout form entries, buyer or attendee details, email addresses, order numbers, payment references, authentication pages, embedded storefront or box-office activity, or organizer dashboards to Google Analytics or PostHog. Checkout and confirmation pages are not measured as page views. Google advertising storage, advertising user data, advertising personalization, and Google signals remain disabled.

Error reports

If a page breaks, Musa may receive a technical error report, such as the error message, your browser type and the page path without any query string, with personal details like email addresses, phone numbers and ticket links removed and with no screen or session recordings.

Your choice

You can decline without affecting event discovery or ticketing. Use the persistent Analytics settings control on a public event or privacy page to allow or revoke analytics at any time.