GA4 Setup for a Dubai Business

GA4 setup for a Dubai business (do it once, properly)

GA4 is free, powerful, and easy to install badly. A double-tagged WordPress theme, an abandoned Universal Analytics habit, and three freelancers each “adding a pixel” will give you numbers you cannot trust. This guide is a clean setup path for UAE SMEs — service, retail, and light ecommerce — without enterprise theatre.

Outcomes you want from GA4

GA4 should answer:

• Where traffic comes from (with honest channel labels)
• Which pages and campaigns produce key events that match money
• How users move on mobile (majority of UAE browsing)
• Whether English vs Arabic paths behave differently
• Ecommerce funnel steps if you sell online

It will not by itself tell you cost per booked job. That needs ad spend data + CRM/offline import. Treat GA4 as the web behaviour layer of a wider stack.

Architecture decision: one property, clear streams

Default for almost every SME: one GA4 property, one web data stream, deployed through Google Tag Manager.

When to split properties:

• Separate legal entities with no shared marketing
• Franchise brands that must never mix data

When not to split:

• “English site vs Arabic site” — usually one property, language as a dimension or path
• “Blog vs main site” on the same domain — one property
• Staging sites — use a separate property or strict hostname filters, never production pollution

Create the property under a Google account the business owns (not a personal freelancers@gmail that vanishes). Add the agency as a user, not as the owner.

Currency and timezone

Set reporting timezone to Gulf Standard Time (Asia/Dubai) and currency to AED. Wrong timezone makes Ramadan evening spikes look like “afternoon performance.” Wrong currency breaks ecommerce revenue and confuses finance.

Install via GTM (preferred)

1. Create a GTM container for the website domain(s).
2. Install the GTM snippet in the site header (or via a reputable plugin — still verify source code once).
3. In GTM, add a Google Tag (GA4 configuration) with your Measurement ID (G-XXXXXXXX).
4. Trigger: All Pages (or Consent-aware equivalent if you use Consent Mode).
5. Publish a workspace version with a clear name: 2026-08 GA4 base.

Verify on a real phone

Open the site on a UAE mobile network. In GA4 Admin → DebugView (with GTM preview or the GA Debugger), confirm:

• page_view fires once per navigation (not double)
• Hostname is production, not staging
• No unexpected second GA4 ID firing

Also check View Source / network tab: you should not see a hard-coded gtag and GTM both sending the same Measurement ID unless you designed dual setup deliberately (you almost never should).

Enhanced measurement: keep the useful bits

GA4’s enhanced measurement can auto-collect scrolls, outbound clicks, site search, video, file downloads. For most Dubai brochure sites:

• Keep page views, outbound clicks (useful for WhatsApp/call deep links if they leave the domain), site search if you have it
• Be cautious treating auto scroll as a KPI — “90% scroll” on a short page is not engagement gold

Turn on what you will actually review monthly. Noise metrics train bad habits.

Domains, subdomains, and bilingual sites

Common UAE pattern: example.ae English + /ar/ Arabic, or ar.example.ae.

• Prefer path-based language with one stream when possible
• Cross-domain only if checkout lives on another domain (payment gateway, booking SaaS). Configure referral exclusions and linker carefully or every paid session becomes “referral from payment provider”

List internal domains in the data stream settings so payment and chat widgets do not steal session credit.

Link Google Ads and other products

If you run Search or Performance Max:

1. Link GA4 ↔ Google Ads from Admin
2. Import only meaningful conversions later (after you define key events)
3. Turn on auto-tagging in Google Ads (gclid)

For Meta, TikTok, Snap: they are not “linked” like Ads; you still need UTMs on destination URLs so GA4 can attribute landing traffic. Platform optimisations stay in-platform (pixels/CAPI).

Filters and data hygiene (SME level)

You do not need a data warehouse on day one. You do need:

• Internal traffic filter for office/home IPs of staff who spam the site while testing
• A note of known bot weirdness (spikes of not-set country) — investigate before celebrating traffic
• Consistent page titles and clean URLs (query parameters for UTMs are fine; random session IDs in URLs destroy reports)

Do not filter aggressively until you understand the data. Bad filters hide real customers.

Ecommerce: start with recommended events

If you take online payments (fashion in Dubai Marina mall catchment, electronics, F&B delivery sites):

Implement the standard funnel where possible:

• view_item
• add_to_cart
• begin_checkout
• purchase (with transaction_id, value, currency AED, items)

Test a real AED 1–5 test order if needed, then refund. Verify purchase value matches the order. Double purchase tags create fantasy ROAS.

Key events: mark few, mark true

In Admin → Events, mark as key events only conversions you would spend money to acquire. Examples:

Deep dive: Events, conversions, and key events.

Consent Mode and cookie banners

If you show a consent banner (increasingly expected, and wise under PDPL thinking), implement Consent Mode so tags respect choices and Google can model where appropriate. Do not paste a free banner that blocks everything forever without a developer pass — you will break ads and analytics silently.

Details: Privacy, cookies, and Consent Mode.

90-minute validation checklist

• ☐ Business-owned Google account + property
• ☐ Timezone Asia/Dubai, currency AED
• ☐ GTM single install, no duplicate hard-coded gtag for same ID
• ☐ DebugView shows clean page_view on mobile Safari/Chrome
• ☐ Key events fire once per real conversion
• ☐ Google Ads linked if applicable; auto-tagging on
• ☐ Internal traffic filtered or documented
• ☐ Homepage, top service page, Arabic page (if live), and thank-you page all tested
• ☐ WhatsApp / tel links checked for accidental double hits
• ☐ Document Measurement ID, GTM ID, and who has Admin access in a shared note

What “done” looks like for a Marina service company

Illustrative: a bathroom renovation firm in Dubai Marina with a 12-page site. After setup they have one property, five key pages instrumented, generate_lead on the quote form, outbound click to wa.me, Google Ads linked, and a weekly export of key events by session source/medium. They still track booked jobs in a sheet — but they finally trust which landing pages and campaigns create the first signal.

Maintenance calendar

• After every site redesign: re-test tags (agencies often drop GTM)
• After new thank-you page or booking tool: re-map events
• Quarterly: access review (remove departed freelancers)
• Before Ramadan / big sale: verify purchase and lead tags under load

Mistakes that create expensive fiction

• Two GA4 IDs on the same page
• Marking all enhanced events as conversions
• Using the agency’s property “for convenience”
• Ignoring Arabic paths
• Celebrating traffic after a bot spike
• Never opening DebugView on a phone

After GA4 is solid

1. Standardise UTMs
2. Instrument calls and WhatsApp offline
3. Add server-side / CAPI if paid spend is material
4. Build the owner dashboard

GA4 is plumbing. Plumbing should be boring, labelled, and leak-tested — then forgotten while you run the business.

Related guides

• Events, Conversions, and Key Events
• UTM Parameters That Stay Clean
• Marketing Analytics in the UAE: Start Here
• Call Tracking for Service Businesses
• Google Ads for UAE Businesses: Start Here
• Meta Ads for UAE Businesses: Start Here

---

Part of the Dubai Marketing Playbook by Shabang — practical marketing for UAE businesses.