# Owner setup after publication

## Google Analytics 4

The site ships without a Measurement ID, so it does not collect analytics yet. Use the agency's own Google account to create a GA4 property and web data stream, copy its `G-...` Measurement ID, set `ga4MeasurementId` in `content/brand.json`, then rebuild and publish. GA4 and its analytics cookies remain off until a visitor opts in using the consent panel. Visitors can reject analytics or reopen privacy settings. Review retention, Google signals and your privacy notice for the applicable laws and your business needs.

Once connected and consented, GA4 can report aggregated sessions, page views, popular pages, broad location, traffic source, device category and recent activity. The site sends `whatsapp_click` and `booking_inquiry` events only after consent; it does not send a visitor's name, travel dates or message text to Analytics. The enquiry form opens a WhatsApp draft; the site does not store or email submitted enquiries.

For a standard GA4 property, the Realtime report covers the last 30 minutes and events can appear seconds after collection; Analytics 360 supports up to 60 minutes. Realtime is a dashboard, not an email alert for every visitor. An owner with Editor or Administrator access can create Custom Insights, set an evaluation frequency and optionally configure email alerts when conditions are met. Hourly evaluation is available for web data. These are threshold-based alerts and do not identify each visitor personally.

The standard Google Analytics service and Search Console are available without a service fee; Analytics 360 is the paid enterprise offering. The site does not require a separate paid analytics plug-in. Account features and Google terms can change.

## Google Search Console

After the site has a public URL, sign into Search Console using the agency's Google account and add the exact HTTPS URL as a URL-prefix property. Verify ownership using a method available to the owner. DNS verification needs access to the domain's DNS provider; some URL-prefix properties can use a verification method such as an HTML file or meta tag when the platform supports it. The owner must complete verification; publication alone does not prove domain ownership.

After verification, select the property, open **Sitemaps**, and submit `sitemap.xml`. Set `siteUrl` in `content/brand.json` to the final public HTTPS origin, rebuild and republish first; do not use the preview URL as the canonical domain. Google describes sitemap submission as a hint; it does not guarantee crawling, indexing time or search ranking.

## Official references

- [GA4 Realtime report (standard properties: 30 minutes)](https://developers.google.com/analytics/devguides/reporting/data/v1/realtime-basics)
- [Analytics Insights and optional email alerts](https://support.google.com/analytics/answer/9443595?hl=en)
- [Search Console ownership verification](https://support.google.com/webmasters/answer/10267942?hl=en)
- [Google sitemap guidance and submission](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap)