How to Find Traffic Sources in Google Analytics

Find traffic sources in Google Analytics 4 by opening the Traffic acquisition report and selecting Session source / medium as the main table dimension. This shows where the sessions in your selected period came from. Use the User acquisition report when you want the source that first acquired a user, rather than the source of each later session.

Once you can read the sources correctly, compare them with useful outcomes. If Niwa helps your website visitors buy or book, look at completed purchases or reservations alongside traffic. A source sending many visits can still bring few relevant enquiries.

Open the report for session sources

Select the intended GA4 property, open Reports and find Traffic acquisition. In the Life cycle collection it appears under Acquisition. Properties using business-objective collections can organize navigation differently; the report name is the part to look for.

Choose a date range, then use the dimension selector above the first table column. Change Session primary channel group to Session source / medium for the detailed source view.

Read Sessions, engagement metrics and the specific business key event you care about. Google's Traffic acquisition guide explains the available dimensions and metrics. You need appropriate property access to view the report, and an Editor can help add missing reports or customize columns.

Understand the source and medium pair

The source identifies the origin, such as a search engine, referring domain or campaign label. The medium describes the type of traffic. A pair such as google / organic represents recognized organic search traffic. A campaign link might use newsletter / email.

Channel groups collect sources into broader categories such as Organic Search, Referral or Email. Source / medium gives more detail within those groups. Session campaign helps distinguish campaigns when the link carries suitable campaign information.

Use these dimensions deliberately. A channel group, referring website and individual campaign are different levels of detail. Changing the dimension can answer a different question even when the date range stays the same.

Separate first-user acquisition from repeat visits

Imagine someone discovers your business through organic search, returns later through an email and submits an enquiry. This is an illustrative journey.

The User acquisition report concerns the source that first acquired that person, to the extent GA4 can recognize them. Traffic acquisition concerns session sources, including return sessions. They can therefore show different source distributions without either report being broken.

Google's comparison of the two acquisition reports describes this scope difference. Browser changes, devices, consent and identity settings can also affect whether visits are recognized as belonging to the same user.

For the question "Where did this period's visits come from?", start with Traffic acquisition. For "How did we first acquire these users?", choose User acquisition. Attribution reports answer another question about credit for key events.

Investigate direct and unassigned traffic

(direct) / (none) means GA4 did not have an attributable source in that context. It can include typed URLs or bookmarks, but also links that lost referral or campaign information. Do not treat every direct visit as someone who already knew your brand.

An untagged link in an email or messaging app can obscure its origin. Redirects can also drop campaign parameters. Unassigned traffic concerns channel classification and should be investigated through source / medium and your tagging conventions.

If a payment or booking domain unexpectedly appears as a referral, inspect the customer's actual cross-domain journey. A referral exclusion and cross-domain measurement have different purposes. Do not hide a domain simply to make an attribution report look cleaner.

Tag links you control

Use campaign parameters on external links that your business sends. For example, an illustrative newsletter destination could be https://example.com/services/?utm_source=newsletter&utm_medium=email&utm_campaign=autumn-services.

Agree a naming convention before several people begin sending links. Keep it consistent, including letter case. Google's campaign URL guide explains the parameter fields.

Do not place campaign parameters on links between pages of your own website. Internal navigation should not pretend to be a new external campaign. Do not include customer names, email addresses or phone numbers in tracking links.

For Niwa's WhatsApp-to-website booking journey, a consistently tagged website link can identify the arrival from that link. The booking event must still come from the successfully saved appointment, and your report should not equate the link click with a reservation.

Compare sources with a real outcome

Select the relevant event in the report's Key events column instead of combining all important events. Read the event count with sessions and the session key event rate. Check a useful period and enough observations before drawing conclusions.

For a wider discussion of lead quality and business records, use the Niwa traffic-source guide. This tutorial's job is to make the GA4 source report understandable and the link labels consistent.

Tell Niwa which visitor journey you want to support, whether product selection, enquiries or website booking. Bring the source / medium view and the actual completion event so the discussion connects traffic to the task your customers came to finish.