How do I set up Google Analytics 4 correctly in Morocco in 2026?

A correct GA4 setup follows eight steps. First, create the property and data stream, then arbitrate enhanced measurement to avoid duplicates. Next, build an event plan suited to your business — for e-commerce: view_item, add_to_cart, begin_checkout, purchase with value in MAD; for lead gen: generate_lead and custom events like whatsapp_click. Mark your conversions as key events, eliminate double-counting with DebugView, deploy GA4 server-side to recover lost signal, and configure Consent Mode v2. Finish with the Google Ads link, BigQuery export, and setting retention to 14 months. Budget 2 to 4 days for a standard site. The default install, by contrast, takes only 10 minutes but stays unusable for steering campaigns.

What is a key event in GA4 and how do I set one up?

A key event is a GA4 event you mark as important — the equivalent of Universal Analytics' old 'goals'. Since 2024, Google replaced the term 'conversion' with 'key event' in the GA4 interface, reserving the word 'conversion' for Google Ads vocabulary. To create one: go to Admin > Events, find the desired event (for example purchase or generate_lead), and toggle 'Mark as key event'. You can also create a key event from an event that doesn't exist yet, as long as its name is correctly sent by your tags. Only key events feed the conversion reports and can be imported into Google Ads. Best practice is to mark only events with real business value — purchase, qualified lead, WhatsApp contact — not every micro-interaction.

Why are my GA4 conversions counted twice?

Double-counting happens when the same event is sent twice to GA4. The two most common causes are: automatic enhanced measurement counting an event (outbound click, site search) that a manual GTM tag also sends; and a GA4 configuration tag combined with an event tag both firing page_view. For e-commerce, a purchase that re-fires on every reload of the confirmation page also inflates the numbers. To diagnose, open GA4's DebugView alongside the GTM preview and spot any event appearing twice for a single action. The fix is to set a single source per event — disable the redundant enhanced-measurement option, or remove the duplicate manual tag. For purchase, the ideal is to fire the event server-side with a unique transaction ID that blocks recounts.

Is GA4 server-side necessary in Morocco?

GA4 server-side isn't mandatory, but it's strongly recommended as soon as you invest in advertising in Morocco. The reason is technical: classic client-side collection loses 20 to 40% of events due to Safari ITP, Firefox ETP, ad blockers, and the in-app browsers that are heavily present in Moroccan traffic. Server-side routes data through a GTM container hosted on your own domain, which bypasses most of this blocking and sets first-party cookies with a full lifespan. The measured gain is +20 to +35% of events recovered. In practice, if your advertising budget exceeds 5,000 MAD per month, the server-side infrastructure (10 to 25 USD/month on Cloud Run) pays for itself quickly, especially since a single server can simultaneously feed GA4, Meta CAPI, and Google Ads.

How do I link GA4 to Google Ads without distorting conversions?

Linking is done from GA4 admin, under Product links > Google Ads: select your Ads account and enable the link. This unlocks three uses: importing GA4 key events as conversions in Google Ads, feeding Smart Bidding with richer signals, and building remarketing audiences based on real user behavior. The double-counting trap is crucial here: if you import the GA4 conversion AND keep a native Google Ads conversion tag on the same action, the algorithm counts twice. Choose a single source of truth per action. Most experts recommend using imported GA4 key events as the single source, because they benefit from server-side enrichment and consent-mode modeling. Always verify in Google Ads that each conversion action's status is set to 'Primary' or 'Secondary' according to the intended use.

How long does GA4 keep data in Morocco?

GA4 distinguishes two data types. Aggregated data in standard reports (number of users, sessions, conversions per day) is kept indefinitely — those figures remain accessible forever. However, user-level and event-level data, which feeds the Explore module and detailed analyses, has a configurable retention of 2 months by default or 14 months maximum. The setting is under Admin > Data retention; always switch it to 14 months — it's the first fix to make on any account. This limit is the same in Morocco and everywhere else because it's set by Google, not by local regulation. To keep raw data beyond 14 months — essential for year-over-year analyses — the solution is to enable the BigQuery export, free in its standard version, which archives every event with no time limit.

Back to blog

/ 45 · ga4-migration-guide-marocAnalyticsPublished on10 min

GA4 · ANALYTICS · SETUP · MOROCCO 2026

Configuring GA4 in Morocco in 2026: events, conversionsand server-side without errors

In 2026, a correct GA4 setup in Morocco rests on three pillars: a structured event plan, conversions (key events) cleaned of double-counting, and a consent mode aligned with first-party collection. The migration from Universal Analytics ended back in July 2023, yet most Moroccan accounts still run on a default install that loses 20 to 40% of signal and distorts attribution. Configuring GA4 properly — key events, exploration, Google Ads linking, GA4 server-side — takes 2 to 4 days and turns a passive reporting tool into a campaign optimization engine.

By Marouane MohachtouFounder & CEO

2–4 daysfull setupevent plan + testing

+20–35%signal recoveredGA4 server-side vs client only

14 monthsmax retentionGA4 user-level data

8 steps2026 checklistfrom property to Google Ads

GA4 in Morocco in 2026: what a correct setup demands

Universal Analytics stopped processing data in July 2023, and the 360 version followed in 2024. In 2026, there is only one Google Analytics: GA4. Yet most Moroccan accounts we audit run on a default install — the tag placed once via Google Tag Manager or gtag.js, with no event plan, no declared key events, no consent mode. The result is a passive reporting tool that shows sessions and users but remains unusable for steering campaigns. A correct GA4 setup in Morocco in 2026 demands four things. First, a data model built for your business: which events matter (purchase, lead, add-to-cart, WhatsApp click), which parameters accompany them, and which become key events. Second, collection that stays robust against restrictive browsers and ad blockers — that's the role of server-side. Third, a consent mode that respects user choice while preserving modeling. Fourth, clean links to Google Ads and BigQuery to activate and export the data. The Moroccan context adds its own specifics: majority-mobile traffic, a large share of users on in-app browsers (Facebook, Instagram, TikTok), and e-commerce often based on cash-on-delivery where the real conversion happens offline. These realities change how you define events and measure attribution.

GA4 has been the only Analytics since 2023 — the default install isn't enough to steer campaigns
Four pillars: event plan, server-side, consent mode, Ads/BigQuery links
Morocco context: dominant mobile traffic, in-app browsers, cash-on-delivery e-commerce
Goal: move from a passive reporting tool to a campaign optimization engine

The GA4 event plan: the foundation of any setup

GA4 is built on an event model: everything is an event, unlike Universal Analytics with its separate page, event, and transaction hits. Before touching anything, you must map the events that matter to your business. This is the step 80% of Moroccan installs skip, and it's why their data is unusable. GA4 automatically collects four families of events: automatically collected events (first_visit, session_start), enhanced measurement (scroll, outbound clicks, site search, video views, file downloads), Google's recommended events (purchase, add_to_cart, generate_lead), and your custom events. The rule: always use Google's recommended event names when they exist (purchase, begin_checkout, add_to_cart), because they unlock pre-built reports and machine-learning enrichment. For a Moroccan e-commerce, the minimal plan includes: view_item, add_to_cart, begin_checkout, add_shipping_info, add_payment_info, and purchase, each with e-commerce parameters (items, value, currency in MAD). For a lead-gen site: generate_lead and custom events like whatsapp_click or call_click, essential given WhatsApp's role in local conversion. Document each event in a table: name, trigger, parameters, and key-event status. This document becomes the contract between marketing and the technical implementation.

GA4 = 100% event model — everything is an event, no more separate hit types
Use Google's recommended names (purchase, add_to_cart) to unlock native reports
Morocco e-commerce: view_item → add_to_cart → begin_checkout → purchase with value in MAD
Lead gen: generate_lead + custom whatsapp_click and call_click events, documented

Key events and conversions: clearing double-counting

In GA4, what Universal Analytics called 'goals' is now called key events, and on the Google Ads side we speak of conversions. A key event is simply an event you mark as important in the GA4 interface. That marking feeds the conversion reports and the import into Google Ads. Double-counting is the number-one source of error in Moroccan GA4 accounts. It happens when the same event is sent twice: once by GA4's automatic enhanced measurement, once by a manual tag in GTM. Classic case: GA4 automatically counts outbound clicks while a GTM tag also fires a custom click event on the same links. Another frequent case: the GA4 configuration tag AND a GA4 event tag both sending page_view. The result: conversions inflated by 30 to 50%, Smart Bidding optimizing on noise, and reports leadership can't trust. The cleaning method: first audit with GA4's DebugView and the GTM preview in parallel. Spot every event appearing twice. Decide on a single source of truth per event — either enhanced measurement or a manual tag, never both. Disable enhanced-measurement options that are redundant with your custom tags. Finally, for e-commerce conversions, ensure purchase fires only once per order, ideally server-side to avoid confirmation-page reloads that recount the purchase.

Key events = GA4 conversions; marking them feeds reports and the Google Ads import
Double-counting: automatic enhanced measurement + manual GTM tag on the same event
Symptom: conversions inflated 30–50%, Smart Bidding optimizing on noise
Fix: one source per event, DebugView + GTM preview to audit duplicates

GA4 server-side: recovering lost signal in Morocco

GA4's client-side collection — the gtag.js running in the browser — suffers the same limits as any client-side tracking. Safari ITP and Firefox ETP cut first-party cookie lifespan to 7 days or even 24 hours. Ad blockers (uBlock Origin, AdGuard, Brave) intercept requests to google-analytics.com and region1.analytics.google.com. In Morocco, where a significant share of traffic runs through in-app browsers and restrictive mobile configurations, signal loss routinely reaches 20 to 40% of events. GA4 server-side solves this by routing hits through a GTM Server-Side container hosted on your own domain (e.g., sgtm.yoursite.ma). The browser sends events to your server, which validates, enriches, and relays them to GA4 via the Measurement Protocol. Because the request originates from your domain and not a Google domain, it bypasses most blocking. Measured gains: +20 to +35% of events recovered, first-party cookies set server-side with a full lifespan, and total control over the data sent. Deployment runs through Cloud Run (10–25 USD/month) or Stape (from 19 USD/month) — the same infrastructure used for Meta CAPI. The ideal is to consolidate: a single GTM server feeds GA4, Meta CAPI, and Google Ads Enhanced Conversions. Deduplication remains essential: GA4 server-side must complement, not duplicate, existing collection.

Client-side GA4 loses 20–40% of signal in Morocco: ITP, ETP, ad blockers, in-app browsers
Server-side via a GTM container on your domain (sgtm.yoursite.ma) bypasses blocking
Gains: +20–35% events recovered, first-party cookies with full lifespan
Consolidate: one GTM server for GA4 + Meta CAPI + Google Ads (Cloud Run 10–25 USD/month)

Consent mode and privacy: collect without breaking attribution

Morocco has Law 09-08 on personal data protection, overseen by the CNDP, which requires consent for tracking. For Moroccan advertisers reaching a European audience, GDPR applies too. In practice, a properly configured consent banner is no longer optional in 2026 — and if it's badly implemented, it simply destroys your GA4 collection. Google Consent Mode v2 is the mechanism that connects your CMP (consent management platform) to GA4 and Google Ads. It defines two signals: analytics_storage and ad_storage. When the user declines, GA4 writes no cookies but sends cookieless pings — which lets Google model the missing conversions via its machine learning. The fatal error is installing a banner that fully blocks GA4 from loading before consent: you then lose the modeling pings and attribution collapses. The correct setup: declare the default consent state (denied) before any tag, then update it based on the user's choice. Consent Mode v2 in 'advanced' mode loads GA4 from the start with consent denied, preserving modeling. Always verify in DebugView that events arrive with the right consent status. A clean banner recovers 10 to 20% of modeled conversions you would otherwise lose.

Law 09-08 / CNDP in Morocco + GDPR for EU audiences: consent mandatory in 2026
Consent Mode v2 links the CMP to GA4/Ads via analytics_storage and ad_storage
Fatal error: blocking GA4 from loading before consent destroys modeling
Advanced mode: default consent denied then update — recovers 10–20% of modeled conversions

Exploration, Google Ads linking, and the final checklist

Once collection is clean, GA4 becomes usable. The Explore module is the successor to Universal Analytics' custom reports: it builds funnel analyses, path exploration, overlapping segments, and cohorts. For a Moroccan e-commerce, the view_item → add_to_cart → begin_checkout → purchase funnel exploration reveals exactly where buyers drop off — often at the payment step, where poorly configured cash-on-delivery distorts measurement. Google Ads linking is the step that turns GA4 into an acquisition tool. From GA4 admin, link your Google Ads account: this lets you import GA4 key events as conversions in Ads, feed Smart Bidding with richer signals, and build remarketing audiences based on real behavior. Beware of double-counting: choose ONE source per action (either the imported GA4 conversion or the native Google Ads tag, not both) or you'll distort Smart Bidding again. The final GA4 setup checklist for Morocco in 2026: property and data stream created, enhanced measurement arbitrated, event plan implemented and documented, key events declared, double-counting eliminated, GA4 server-side deployed, consent mode v2 in advanced mode, data retention set to 14 months, Google Ads link active, BigQuery export enabled, and full validation in DebugView. Budget 2 to 4 days for a standard site.

Funnel exploration view_item → purchase reveals where buyers drop off (often at payment)
Google Ads linking: imports GA4 key events, enriches Smart Bidding, builds audiences
Never double-count Ads conversions: one source per action (imported GA4 OR native tag)
2026 checklist: event plan, key events, server-side, consent v2, 14-month retention, BigQuery

FAQ

How do I set up Google Analytics 4 correctly in Morocco in 2026?: A correct GA4 setup follows eight steps. First, create the property and data stream, then arbitrate enhanced measurement to avoid duplicates. Next, build an event plan suited to your business — for e-commerce: view_item, add_to_cart, begin_checkout, purchase with value in MAD; for lead gen: generate_lead and custom events like whatsapp_click. Mark your conversions as key events, eliminate double-counting with DebugView, deploy GA4 server-side to recover lost signal, and configure Consent Mode v2. Finish with the Google Ads link, BigQuery export, and setting retention to 14 months. Budget 2 to 4 days for a standard site. The default install, by contrast, takes only 10 minutes but stays unusable for steering campaigns.
What is a key event in GA4 and how do I set one up?: A key event is a GA4 event you mark as important — the equivalent of Universal Analytics' old 'goals'. Since 2024, Google replaced the term 'conversion' with 'key event' in the GA4 interface, reserving the word 'conversion' for Google Ads vocabulary. To create one: go to Admin > Events, find the desired event (for example purchase or generate_lead), and toggle 'Mark as key event'. You can also create a key event from an event that doesn't exist yet, as long as its name is correctly sent by your tags. Only key events feed the conversion reports and can be imported into Google Ads. Best practice is to mark only events with real business value — purchase, qualified lead, WhatsApp contact — not every micro-interaction.
Why are my GA4 conversions counted twice?: Double-counting happens when the same event is sent twice to GA4. The two most common causes are: automatic enhanced measurement counting an event (outbound click, site search) that a manual GTM tag also sends; and a GA4 configuration tag combined with an event tag both firing page_view. For e-commerce, a purchase that re-fires on every reload of the confirmation page also inflates the numbers. To diagnose, open GA4's DebugView alongside the GTM preview and spot any event appearing twice for a single action. The fix is to set a single source per event — disable the redundant enhanced-measurement option, or remove the duplicate manual tag. For purchase, the ideal is to fire the event server-side with a unique transaction ID that blocks recounts.
Is GA4 server-side necessary in Morocco?: GA4 server-side isn't mandatory, but it's strongly recommended as soon as you invest in advertising in Morocco. The reason is technical: classic client-side collection loses 20 to 40% of events due to Safari ITP, Firefox ETP, ad blockers, and the in-app browsers that are heavily present in Moroccan traffic. Server-side routes data through a GTM container hosted on your own domain, which bypasses most of this blocking and sets first-party cookies with a full lifespan. The measured gain is +20 to +35% of events recovered. In practice, if your advertising budget exceeds 5,000 MAD per month, the server-side infrastructure (10 to 25 USD/month on Cloud Run) pays for itself quickly, especially since a single server can simultaneously feed GA4, Meta CAPI, and Google Ads.
How do I link GA4 to Google Ads without distorting conversions?: Linking is done from GA4 admin, under Product links > Google Ads: select your Ads account and enable the link. This unlocks three uses: importing GA4 key events as conversions in Google Ads, feeding Smart Bidding with richer signals, and building remarketing audiences based on real user behavior. The double-counting trap is crucial here: if you import the GA4 conversion AND keep a native Google Ads conversion tag on the same action, the algorithm counts twice. Choose a single source of truth per action. Most experts recommend using imported GA4 key events as the single source, because they benefit from server-side enrichment and consent-mode modeling. Always verify in Google Ads that each conversion action's status is set to 'Primary' or 'Secondary' according to the intended use.
How long does GA4 keep data in Morocco?: GA4 distinguishes two data types. Aggregated data in standard reports (number of users, sessions, conversions per day) is kept indefinitely — those figures remain accessible forever. However, user-level and event-level data, which feeds the Explore module and detailed analyses, has a configurable retention of 2 months by default or 14 months maximum. The setting is under Admin > Data retention; always switch it to 14 months — it's the first fix to make on any account. This limit is the same in Morocco and everywhere else because it's set by Google, not by local regulation. To keep raw data beyond 14 months — essential for year-over-year analyses — the solution is to enable the BigQuery export, free in its standard version, which archives every event with no time limit.