Google Analytics Traffic for GA4

How GA4 measures traffic

GA4 uses event-based collection and defines sessions as periods of interaction. An owner-authorized property can show users, session statistics, approximate geography, browser and device information. Acquisition reports also use dimensions such as session source / medium.

Which acquisition report answers your question?

Start with the question you want the report to answer. A user’s first visit and a later session can have different sources.

Source identifies the recorded origin of the traffic, such as a search engine, referring website or newsletter label. Medium describes the type of traffic, such as organic search or email. Source platform is a separate, broader platform classification. When sharing a figure, keep the full dimension name, metric, date range and filters with it. The same metric can have different values when grouped by first-user or session dimensions.

Sources: Google on acquisition report scope and traffic-source dimensions.

Keep a campaign identifiable in GA4

Agree the campaign labels before sharing a link. Keep your existing naming convention so that later records refer to the same campaign.

Hypothetical URL-tagging example. These fictional newsletter labels illustrate a website link; they do not describe an Extcorp traffic source.

https://example.com/demo/?utm_source=partner_newsletter&utm_medium=email&utm_campaign=october_demo&utm_id=demo_01&utm_source_platform=example_mail

For manual tagging, look for partner_newsletter / email in Session source / medium and october_demo in Session campaign in Traffic acquisition. Values are case-sensitive: october_demo and October_Demo are different labels. Google also omits UTM parameters from Landing page + query string and Page path + query string; URL information is available through Page location. See Google’s campaign URL guidance.

Choose the measure before reviewing the result.

Google defines separate user metrics and events for measured interactions. A recorded session or event alone does not establish a qualified lead. For a worked check of validation, acceptance and retries, see verify accepted enquiries behind GA4 form events.

Before the review, keep the original link and check the final URL after any redirect. A link can retain its labels while collection remains unresolved. What appears in GA4 depends on collection, consent settings and Google’s processing. Record unresolved issues, including any interaction with auto-tagging, instead of assuming a tagged click was counted.

Save the property, report, chosen dimensions, metric, dates, time zone, filters and capture date in the traffic report record. This gives a GA4 Traffic inquiry a clear review question. Any changes to tagging or consent need a separately agreed scope.

If a GA4 export says collected_traffic_source

In Google’s BigQuery export schema, collected_traffic_source describes traffic-source data present in a collected event. Its manual_source and manual_medium fields hold collected campaign-source and medium information; Google notes that these may also include parsed referral parameters. A Traffic acquisition report instead uses session-scoped dimensions. Keep the export field and report dimension distinct when recording a question.

Using the existing fictional newsletter labels above, an event row could contain manual_source = partner_newsletter and manual_medium = email. That row is evidence about the collected labels. It does not by itself supply a session total or establish that an enquiry was accepted. Keep the event and export context with it, then use the report record or accepted-enquiry example for the relevant next check.

Definitions checked 19 October 2026: Google’s BigQuery schema and acquisition report scopes. This explanation does not add an analytics-setup service. You can ask a short GA4 traffic question before collecting a detailed report record.

Can new users exceed active users?

Yes. New users counts unique users with a first_visit or first_open event in the period. Active users uses engagement or specified collection criteria, which include first_visit on websites. Google explicitly allows New users to exceed Active users and notes that thresholding can contribute to discrepancies. See Google’s user-metric definitions.

Compare the exact report, dates, filters and any data-quality notice first. The difference between the totals does not identify a group of inactive users. For recent figures, also check the report’s processing stage.

Unassigned and (not set): what to check in GA4

Unassigned means a source did not match a channel in the channel group being viewed. (not set) means GA4 lacks information for the selected dimension. Use the actual label to choose the next check.

Google maps sessions with (not set) source / medium to Unassigned in the default channel group.

Sources: Google on missing dimension values and channel classification and tag ordering.

Keep the report name, full dimension label and affected row. A recorded custom source can lack a matching channel rule, so renaming campaign labels is not a universal repair. Any account-specific cause needs an implementation check.

Realtime activity and a processed report

Realtime can help confirm receipt of data, while its acquisition processing and attribution are limited. A visible event there does not establish a completed campaign count. See Google’s Realtime limitations.

Google says processing can take 24 to 48 hours and report figures may change. Reports and Explorations may be unsynchronized; typical processing times are not guarantees. Attribution credit for key events can change for up to 12 days. That specific attribution window is not a waiting period for every traffic metric. See Google’s data-freshness guidance.

For the follow-up check, use the property, dates and filters saved in your campaign record, and add the new capture time. If the acquisition result is still missing, use the label checks above and have the measurement owner inspect collection. Elapsed time alone does not identify the cause.

Sessions, users and views count different things

A person can return for another session and view several pages each time. Choose the unit that answers your question before comparing traffic totals.

Event count includes all collected events, so it is broader than Views. A count of page views alone does not tell you the number of other events. Google’s definitions cover sessions, users and views and events.

Hypothetical counting example

Assume one website and reporting period, two consistently recognized users and collection of every listed page view. The sessions have already been identified separately:

The arithmetic gives 3 Sessions, 2 Total users and 5 Views. Both users have a session with two page views, so both qualify as active: 2 Active users. That equality with Total users belongs to this example; it is not a rule for every report. Other events are unspecified, so Event count cannot be calculated from these rows.

GA4 reporting uses estimation for distinct session and user counts. For an actual comparison, keep the report context in your campaign record and check any data-quality notices alongside the figures.

Campaign and property settings

Share the details you already know to help define the requested campaign.

• GA4 property

  Identify the website, property and web data stream relevant to your question.

• Source / medium

  Share the campaign labels you want to review and any existing tagging convention.

• Landing pages

  Which pages matter, and what should a visitor be able to do there?

• GEO and devices

  Name any countries or device categories you need considered.

• Sessions, users or events

  Choose the metric and period that answer the project question.

• Tagging and consent

  Note known collection issues. Changes to tagging, consent or integrations require an agreed scope of work.

Access authorized by the owner

Access can be discussed after the work is defined. The property owner decides what to grant through Google’s access controls and keeps control of the account.

How GA4 differs from Similarweb and Semrush

GA4 is the first-party view for the client’s own site. Similarweb and Semrush are external market-intelligence estimates. Extcorp offers all three commercially and keeps their metrics and methods distinct.

Free test process

1. Send a short question. Leave your contact. The website URL and report details can follow.
2. Discuss the goal. Identify the report, metric and period you want to review, plus any collection limitations.
3. Confirm the test. After reviewing the request, we will clarify whether a test is available and on what terms.
4. Review the report. After an agreed test, compare the chosen measure over the agreed period before deciding on a paid campaign.

Related services

• Similarweb traffic
  Use an external visibility estimate by GEO, devices and sources.
• Semrush traffic
  Work in a separate competitive traffic context.
• Traffic service guide
  Compare first-party measurement with external estimates.