How to exclude the host/production company's access from GA4 | Internal traffic settings

If the host or staff check the homepage every day, their viewing may also be recorded in Google Analytics 4 (GA4).Even in months when production companies repeatedly check for updates, it may appear that the number of actual travelers has increased.

This type of viewing by the operator can be classified as “internal traffic.”However, you should not enable exclusions from the start. The safe order is to determine who will be internal, check it in a test state, and enable it only after you are sure there are no problems.

Contents

Conclusion you should know first
Decide who to include in your internal traffic
Things to check before setting
Setting steps
When numbers do not disappear or disappear too much
Alternatives at accommodations where IP changes
What you can ask AI to do/What people should do
1. Reading survey request text
2. Request for creating a test plan
Final checklist
Sources

Conclusion you should know first

Internal traffic settings using IP addresses are useful for accommodations that meet the following conditions.

The inn’s business internet line has a global IP address that does not change easily.
You can distinguish between Wi-Fi for guests and business lines.
The host and staff have a lot of views, which has a visible impact on access analysis.
After setting up, you can test from the inn’s line and another line.

On the other hand, if you exclude the entire line at an inn where guests and staff use the same Wi-Fi, even the views of real guests may disappear. Smartphone lines, VPNs, and lines whose IP addresses change frequently are also not suitable for simple IP specification.

If it is difficult to exclude completely, there is no need to force the setting. There is also a method of recording the possibility of mixed traffic on the management side and looking at trends by comparing periods or filtering on reports.

Decide who to include in your internal traffic

Rather than “excluding all people related to the inn,” we only select repeated views that greatly skew the measurement.

Viewer/place	Example of judgment
Office computer	Candidate if you check it many times every day
Innkeeper and staff smartphones	Check whether they can be included only while connected to the inn’s Wi-Fi
Production company office	Check fixed IP and scope of responsibility before making candidates
Wi-Fi for guests	As a general rule, do not exclude users to eliminate genuine users
Home/Mobile line/VPN	IP may change, so do not easily specify a wide range

What GA4 uses for determination is normally the global IP address that is visible from the outside. We are not talking about specifying an internal IP address such as 192.168... that is displayed on your computer.

Please do not write your actual IP address in articles, public screenshots, requests to AI, or Git manuscripts. Even when requesting configuration work, the values will be entered on the management screen by the host or an authorized person.

Things to check before setting

Check the target GA4 property and web data stream
Check if Google tags are installed twice
List lines that are candidates for exclusion
Check if guest Wi-Fi and business line are not using the same exit
Check with your line carrier whether the global IP is fixed or variable.
Prepare a smartphone line separate from inside the innWi-Fi for testing

Defining internal traffic requires GA4 property editor or higher privileges. Instead of handing over the inn’s Google account and password to the production company, only the necessary permissions are granted to the person in charge’s own account.

Setting steps

GA4 screen names are subject to change. If you can’t find it, don’t just rely on the screen name in this article; check the Google official help at the end of the article for current instructions.

1. Create rules for internal traffic

Open the target web data stream from the GA4 management screen. Go to Define internal traffic in the Google Tag settings and create a rule.

Use a rule name that indicates its purpose, such as “Inn/Business line”
For the value of traffic_type, use the initial value internal unless there is a special reason.
Choose a match type and enter a verified global IP address or range

If you specify a wide range, there is a risk that unrelated users will be handled internally. Don’t assume that it’s probably within this range; instead, check with the line administrator. Please check the actual connection conditions, as some use not only IPv4 but also IPv6.

Access has not been deleted at this stage. We are preparing to add a value indicating that it is internal to the access that meets the conditions.

2. Start the data filter with “Test”

Next, create a filter that targets “internal traffic” using the property data filter.

Filter type: Internal traffic
Operation: Exclude
Parameter value: internal same as rule
Filter status: Test

Do not enable it from the beginning. Google advises that data excluded by enabled filters will not be processed and cannot be used later. Nor is it a function to retroactively erase past internal access.

3. Check operation from two lines

Open the same page from at least the following two directions at a time when it is distinguishable:

Business line of the inn selected as a candidate for exclusion
External line such as a smartphone line with Wi-Fi turned off, not inside the inn

Use test filter items, DebugView, etc. to check whether only business lines are treated as internal as expected. The confirmation event itself may not be visible on devices that refuse measurement with cookie consent, devices that use ad blocking, or browsers with strong privacy settings.

Rather than adding tags and filters because they are not displayed in real time, check the target property, measurement ID, consent status, and reflection time one by one.

4. Activate after leaving a record

Once confirmed, record the following in the operational record.

Target property and data stream
Rule name and target location
Fixed IP or variable IP?
Does not include Wi-Fi for guests
Test date, person in charge, and external line results
Next confirmation date

We do not leave your actual IP address in our public records. If you are satisfied, enable the filter. It will be easier to make a decision if you switch to a time when you can make comparisons for a while, rather than during busy periods or just before advertising starts.

When numbers do not disappear or disappear too much

If the settings are different from what you expected, check the following before making additional settings.

Is the data filter stuck in “test” or “disabled”?
Do the values match in internal traffic rules and filters?
Are you looking at another GA4 property or data stream?
Has the global IP address of the line changed?
Whether you are connecting via IPv4 or IPv6
Is your smartphone using a mobile line instead of Wi-Fi?
Has the VPN or production company connection route changed?
Are you excluding Wi-Fi for guests as the same IP?
Isn’t it just not being measured by cookie consent, browser functionality, or ad blocking?
Are Google tags installed in multiple ways?

If you suspect that guests’ views are being deleted, disable the filter and check the cause. Data from periods already excluded by active filters cannot be restored, so early judgment is required.

Alternatives at accommodations where IP changes

Forcibly chasing dynamic IPs and mobile lines will result in more rule updates and exclusions.

Check for site updates using testing methods such as DebugView
Use report comparison and filtering only during analysis
Record the date and time of the update activity and take it into account when interpreting increases in that time period
Ask the production company to record the date, time and number of times confirmation work is performed.
Add a note to the monthly report that says “Includes some operator access”

Internal traffic exclusion is not a mechanism for identifying people. It also does not replace Cookie Consent and Privacy Notice.

What you can ask AI to do/What people should do

AI helps organize the current situation, create pre-configuration checklists, test plans, and record confirmation results. On the other hand, it is safe for the host or an authorized person to log in to the Google account, enter the real IP, and make the final decision on activation.

Reading survey request text

Please sort out the issue where the operator's confirmation access is mixed with GA4 of the inn site.

Conditions:
- Do not change settings yet
- Don't ask for your Google account password or real IP address
- Consider Wi-Fi for guests and business lines separately.
- Check the difference between fixed IP, dynamic IP, mobile line, and VPN
- Separately shows unknown points, places to confirm, setting candidates, and options not to set.

Request for creating a test plan

Create a test plan before enabling GA4's internal traffic filter.

Conditions:
- Initially set to "test" state
- Compare the inn's business line and external smartphone line
- Check if you have accidentally excluded Wi-Fi for guests.
- Actual IP address is hidden.
- Indicates passing conditions, conditions for stopping in case of failure, and recording items.
- Do not change to "enabled" without my confirmation

Final checklist

Determined the purpose and target of exclusion
Wi-Fi for guests is not included in the target.
Checked whether the global IP is fixed or variable.
Real IP is not posted in public manuscripts or AI conversations
Matched internal traffic rules and filter values
Created data filter in test state
Confirmed on both business line and external line
I understand that excluded data cannot be restored after activation
Recorded the setting date, person responsible, confirmation result, and next confirmation date.
Review settings once a month or when changing internet lines

Please also check Introduction to Google Analytics 4 for the host for the entire implementation of GA4, and How to measure reservation buttons, phone calls, and inquiries with GA4 for measuring reservation inquiries.