GA4: Set Up Measurement and Acquisition Reporting That Helps Decisions

GA4 supports acquisition decisions when a team can trace a visit to its source and to an agreed business action. The aim is not to collect every click. It is to define meaningful actions, keep campaigns comparable, and distinguish traffic or engagement from a confirmed enquiry or sale.

The assigned primary query, “Google Analytics / GA4,” has volume 8,900, keyword difficulty 56, and traffic potential 300 — Ahrefs Morocco estimate, 22 October 2026 — with informational and commercial intent. This is a search-demand estimate, not a forecast of traffic, rankings, enquiries, or revenue.

Begin with the acquisition decision

Decide what a GA4 configuration should help the team do. It may identify the channels associated with confirmed requests, check whether a campaign reaches the intended page, expose untagged email traffic, or investigate a change after a website release. “Get more traffic” is too broad to design measurement around.

Create a concise measurement plan with marketing, sales, and technical stakeholders. For each important action, record the event name, exact trigger, relevant journey, useful parameters, business owner, deduplication rule, test case, and decision supported. A confirmed form submission, completed booking, purchase, or thank-you-page arrival is usually more interpretable than one button click. Clicks can still help diagnose friction, but they are not automatically commercial outcomes.

Google defines a key event as an event that measures an action particularly important to a business. Any collected event can be marked as key and then reviewed by channel or touchpoint. Read Google’s key-events guidance before elevating an event into a KPI.

Set up GA4 in a dependable sequence

Establish the property and collection method

First confirm that the correct Google Analytics property is used, with intentional time-zone, currency, and access settings. These choices affect how later reports are read; a time-zone change applies going forward and can complicate trend comparisons.

For websites, Google supports collection through a Google tag on pages, a CMS integration, or Google Tag Manager. The right approach depends on the technical architecture and release process. Avoid duplicate installations, which can make one action appear twice. Google’s website and app setup guide gives the current workflow and role requirements. A GA4 tracking and analytics scope can connect implementation to an agreed measurement plan and test process.

Validate before adding more events

Test a representative journey in a browser and on mobile: entry from a campaign, a key-page view, form start, abandonment, and successful confirmation. Check that expected pages and events arrive, that no event fires twice, and that parameters contain no personal data.

Use short, consistent event names that describe an action. Keep a definition for each one. Do not mark an event as key merely because it is easy to tag; ask whether the business can explain, test, and act on it.

Test journeys that move between domains

A visitor may move from a main site to a booking engine, payment flow, subdomain, or another owned domain. A configuration gap can split that journey and make the next step appear to start from a new source. List the domains, redirects, external flows, and confirmation pages, then test the complete path. Page-view collection alone does not prove continuity.

Document the date, configuration change, owner, code or container version, test scenario, and result. Repeat critical tests after a CMS migration, form change, consent update, language-path change, or URL redirect.

Read acquisition reports at the right scope

The Traffic acquisition report answers a session question: where did website or app visitors come from for their sessions, including returning visitors? It is different from User acquisition, which focuses on the initial source of new users. Google describes Traffic acquisition as a pre-made detail report and explains its session-scoped dimensions in the Traffic acquisition report guide. If navigation differs, a report collection may have been changed.

Start with Session default channel group, then inspect Session source / medium and Session campaign. Categories such as Organic Search, Paid Social, Email, and Direct are useful prompts for investigation, not final judgments on channel quality.

Sessions show visits that began, not business value.
Engaged sessions and engagement rate describe activity under GA4’s definition. Google counts a session as engaged when it lasts at least 10 seconds, has a key event, or has two or more page or screen views.
Key events and session key-event rate connect a source with a defined action but do not, on their own, establish lead quality.
Total revenue is only meaningful when ecommerce events and their value and currency parameters are correctly implemented.

Investigate a report line in context before taking action. More Paid Social sessions with few confirmed actions could relate to audience targeting, message-to-page fit, UTM data, form friction, or an event defect. Review campaign, landing page, date range, and test evidence before reaching a channel conclusion. If the landing journey needs work, the landing page service is relevant to page structure, message hierarchy, and the next step—not a replacement for measurement.

Keep campaign sources usable with UTMs

For platforms not connected to Analytics, tag destination URLs with UTM parameters. Google maps utm_source, utm_medium, and utm_campaign, among others, to manual traffic-source dimensions. Its manual and auto-tagging documentation recommends setting all relevant parameters when UTMs are used; missing values can produce “(not set)” reporting.

Agree a convention before launch: lowercase source names, controlled medium values, a campaign name that identifies the initiative, and utm_content where creative or placement needs separation. Maintain a shared record of the final URL, owner, date, objective, and approved label. That prevents facebook, Facebook, and fb from becoming three incomparable rows.

For Google Ads, a linked integration and auto-tagging can add platform-specific detail alongside the cross-channel view. It should align with account structure and the destination journey. Digital One Media’s Google Ads service can help connect campaign architecture, landing pages, and measurement without treating GA4 as a bid-management tool.

Never put names, email addresses, phone numbers, or other personal data in URL parameters. Consent choices, visitor notices, access rights, and retention need review with appropriate privacy and legal specialists for the organisation. GA4 configuration alone does not settle those obligations.

Turn the report into a review with a next step

A weekly or monthly review can be brief. Choose a comparable period, record budget, creative, page, or tracking changes, then assess the selected key events and their landing pages. Avoid constructing a narrative from a handful of visits.

Separate observation from hypothesis. “Campaign A generated more sessions in this period” is a report observation. “Its message is more persuasive” is a hypothesis that needs evidence from the creative, page, audience, and commercial process. Record the next check: repair an URL, replay a form test, inspect an event, or reconcile confirmed enquiries with the CRM.

GA4 describes the measured digital journey. It does not independently determine qualification, sales follow-up, duplicate handling, or final commercial outcome. A useful dashboard therefore shows metric definitions, period, filters, major changes, and the owner of the next decision.

Limits to recognise

Reports reflect data collected under a particular configuration. Consent choices, browser protections, blockers, redirects, multiple devices, and implementation faults can change what is observed. Attribution assigns credit under a model and available data; it does not prove that one channel alone caused a decision.

Before comparing GA4 with CRM or ad-platform totals, check definitions, time zones, date ranges, deduplication, and processing dates. Google’s interface and available options can change, so confirm the official documentation before altering a live setup.

FAQ — GA4 setup and acquisition reporting

Should we use Traffic acquisition or User acquisition?

Use Traffic acquisition to assess session sources, including returning visitors. Use User acquisition to understand the initial known source of new users. They answer different questions and are often useful together.

Which events should become key events?

Choose important, clearly defined, testable business actions, such as a confirmed request or correctly tracked purchase. Marking every interaction as key makes the report less clear.

Why does a campaign appear as Direct or “(not set)”?

The link may be untagged, UTM values may be incomplete, a redirect may remove information, or the source may not be available at collection. Check the published URL, full convention, and live journey before interpreting the result.

Can GA4 measure lead quality on its own?

No. GA4 reports observed sources and selected actions. Qualification, sales follow-up, duplicate handling, and eventual outcome also need defined business processes and, where appropriate, CRM reconciliation.