Analytics Nieruchomości na Cyprze

Choosing a property requires considering location, property type, budget and expectations around floor area or distance from the sea. The analytics needed to reflect that process: from narrowing the results, through interest in a specific listing, to making contact.

It was also important to distinguish the purpose of an enquiry. A callback request, a message from the general contact page and an enquiry sent from a property page carry different context. We reflected this distinction in the event structure together with the language of the website.

We prepared measurement for listing views, property selection and visits to individual property pages. The data includes the property ID, name, list context and price in euros when available. This makes it possible to analyse interest in individual listings and their position within the catalogue.

We described search using the selected criteria: region, property type, number of rooms, price and floor-area ranges, and distance from the sea. We also included sorting changes and adding or removing properties from favourites. These actions show how users narrow their selection before making an enquiry.

For forms, we separated the start of an interaction, error signals and the appearance of a success message. Enquiries from property pages received a separate form type and property context. Phone-number and email clicks were recorded as separate contact events.

Before passing catalogue data to GA4, we added checks for identifiers, names, numeric values and currency. For enquiries, we included validation of form data and a safeguard against passing the same event identifier again. Events and Clarity labels were prepared for behavioural analysis by browsing stage, contact type and website language.