What Is GA4's "(direct)/(none)"? Causes and Measures to Reduce It Explained

When you open GA4's acquisition report, have you ever felt something was off because "(direct) / (none)" occupies a considerable share of referrals? There shouldn't be that many people who visit by typing the URL directly, yet "unknown referral" traffic keeps swelling. In many cases, this is not a problem of user behavior but a matter of measurement gaps. This article organizes what GA4's "(direct) / (none)" is, then explains the main causes and concrete measures to reduce its share.

What is GA4's "(direct) / (none)"

"(direct) / (none)" refers to traffic where the source (traffic source) is "(direct)" and the medium is "(none)" — in other words, traffic whose origin cannot be identified. GA4 determines the origin based on referral information (the referrer) sent from the browser, but when this information is absent or lost, all such access is classified as "(direct) / (none)."

When the origin is clear, it is displayed as "google / organic" for arrivals via Google search, or "referring domain / referral" for links from external sites. In contrast, everything whose referral is unknown is gathered into the "(direct) / (none)" catch-all — it helps to understand it this way.

"(direct) / (none)" is not inherently bad

As a premise, "(direct) / (none)" includes normal traffic that occurs on any site to a certain degree. Access from bookmarks and direct URL entry — inflows that inherently have no referral — fall under this. The problem is the case where inflows that were originally from ads, search, or social get mixed into "(direct) / (none)" due to measurement gaps.

What is the problem when "(direct) / (none)" is high

If you leave the share of "(direct) / (none)" high, you can no longer correctly evaluate the contribution of each inflow channel. When conversions that were originally via email newsletters or social get classified as "(direct) / (none)," the results of those measures are unfairly underestimated, becoming a cause of misjudging ad budget allocation and marketing measures.

Generally, many sites keep direct inflow at around 10% of the total. If it has surged well beyond 20%, or the share is high despite no obvious reason, it is important to suspect a problem with the measurement settings, identify the cause, and address it.

Main causes of "(direct) / (none)"

The causes can be broadly divided into "normal cases where there is no referral to begin with" and "cases where there is originally a referral but it is lost." Ultimately, much of the latter comes down to either "campaign parameters not being attached" or "the referrer disappearing."

Normal cases with no referral

The following inflows become "(direct) / (none)" because there is no referral to begin with. These are normal behavior and basically cannot be prevented.

• Access from browser bookmarks / favorites
• Direct URL entry into the address bar (including selection from input suggestions)
• Inflow from links placed in non-web documents such as PDF, Word, or apps
• When the browser or security software is set not to send referral information

Cases where a referral exists but is lost

The following are cases where the origin should originally be identifiable, but the referrer is lost due to measurement gaps or environmental factors, dropping into "(direct) / (none)." These are where there is room to reduce it through countermeasures.

• Forgetting to attach UTM (campaign) parameters: if parameters are not attached to links for ads, newsletters, social posts, QR codes, etc., the referral cannot be identified and it is measured as direct inflow
• Inflow from in-app browsers: apps like LINE and Instagram often do not pass referral information to external sites for privacy protection
• Transition from https to http: moving from an SSL-enabled page to a non-enabled page means the referrer is not carried over for security reasons, becoming direct inflow
• Loss of the referrer due to redirects: referral information can be lost in the process of passing through a redirect
• When rel="noreferrer" is attached to a link: measurement is impossible if it is specified not to send the referral
• Missing tracking code: if you land on a page without the measurement tag and move to a measured page on the same domain, the referral is lost and it becomes direct inflow

Note that in recent years, due to strengthened privacy protection led by iOS and changes in browser specifications, cases where origins that used to be identifiable become "(direct) / (none)" are on the rise.

How to check and identify "(direct) / (none)"

Before taking measures, first grasp the state of your site's direct inflow. From GA4's left menu, open "Reports" → "Acquisition" → "Traffic acquisition," and switch the dimension to "Session source / medium" to check the session count and share of "(direct) / (none)."

If you want to investigate in more detail, in the exploration report narrow the channel group to "Direct" and check country/region, hostname, average session duration, and so on. If there is a concentration from countries unrelated to your business, unfamiliar hostnames, or a large volume of access with a session duration near 0 seconds, spam is also a possibility.

Measures to reduce "(direct) / (none)"

By addressing preventable cases one by one, you can lower the share of "(direct) / (none)" and raise the proportion of inflow with a known referral. Tackle them in order of the greatest effect.

1. Attach UTM parameters to links

This is the measure with the greatest effect and the highest priority. Attach UTM parameters (utm_source, utm_medium, utm_campaign, etc.) to all external links you manage, such as ads, newsletters, social posts, and QR codes. This lets GA4 correctly identify "from where and via what" a user came. It is also important to unify the parameter values, avoiding notation inconsistencies in utm_source such as "facebook" versus "Facebook."

2. Make the whole site SSL (https)

To prevent the referrer from being lost in transitions from https to http, make all pages of the site SSL. SSL not only reduces direct inflow but also improves security through communication encryption and contributes to user peace of mind. It can often be done for free, so if you have not implemented it, do so early.

3. Eliminate missing tracking code

Check whether there are pages that should have page views but are not being measured, and confirm that the measurement tag is correctly installed on all pages. If you limit the measurement target, also review whether landing pages have been excluded from it.

4. Exclude spam and unwanted access

If access suspected to be spam is found during the checking stage, use IP address exclusion settings and the like so that traffic unrelated to your business does not get mixed into measurement. This raises the accuracy of your reports.

Understand that it will not reach 0%

The important point is that no matter how much you address it, "(direct) / (none)" will not reach 0%. Access via bookmarks, direct URL entry, and from browsers that do not send the referrer will always exist to a certain degree. In practice, if you can lower the share to around 15%, channel classification such as ads, search, and social becomes sufficiently reliable. Rather than aiming for zero, make it your goal to steadily reduce the preventable portion.

Summary

GA4's "(direct) / (none)" is a catch-all for traffic whose referral cannot be identified, mixing normal inflow such as bookmarks and direct URL entry with inflow that lost its original referral due to measurement gaps. If the share stays high, you cannot correctly evaluate each channel's contribution, so it is important to reduce the preventable portion through measures such as attaching UTM parameters, SSL, and reviewing the tracking code. Rather than aiming for 0%, raise the proportion of inflow with a known referral and connect it to accurate access analysis.