Know which pages and channels bring enquiries, not just visits

Analytics starts with a list, not a tool. Before touching GA4 we sit down with you and write the questions the business needs answered: which pages produce enquiries, which sources send serious buyers, which language performs better, where visitors leave before a form. Each question maps to an event or a report, and anything that does not map gets dropped.

Then we define events. A form submission, a click on a phone number, a WhatsApp button, a brochure download and a booking are not the same, and lumping them together hides what works. We name each event consistently, mark the ones that count as conversions, and test them in a debug view before any real traffic is trusted.

Existing accounts usually need cleanup before anything new. We check for duplicate tags, internal traffic counted as visits, cross-domain gaps between your site and a booking or payment page, and unused properties. A setup like this takes 2 to 4 weeks, depending on how many sites, languages and forms are involved.

These three tools answer different questions. Google Search Console shows how you appear in Google results: queries, impressions, clicks, indexing and page experience. Bing Webmaster Tools offers the same for Bing, which also feeds several other search products and assistants. GA4 records what visitors do after they arrive. None of them replaces the others.

We verify each property at the domain level, submit sitemaps, link Search Console to GA4 where the data is useful, and set up the checks that tell you when something breaks, such as a drop in indexed pages or a spike in errors. Because Arabic and English pages often live in separate paths, we configure views so you can compare them directly.

We then build a single organic-search report that joins the three. It shows which queries bring impressions, which pages convert, and where a page ranks well but gets no enquiries. That last group is usually where the fastest gains are, and it feeds directly into the SEO work if you run it with us.

Saudi Arabia's Personal Data Protection Law applies when you collect data that identifies people, and analytics identifiers can fall under it. The practical questions are what you collect, why, where it is processed, how long it is kept, and whether visitors are told. We do not give legal advice, and your counsel should confirm your position, but we build the tracking so that those questions have clear answers.

In practice this means a consent banner connected to your tags so that analytics and marketing scripts respect the visitor's choice, shortened data retention, no personal data in event parameters such as email addresses in URLs, and a short written record of what each tool collects. We review the regulator's published guidance as we go and flag points for your legal team.

Finally, access. We set up named user accounts with the least access each person needs, remove old agency users, and document who owns each property. Ownership matters more than most companies expect: if the account sits in a former contractor's login, you cannot reach your own history.