Rules per location
IP entries checked by script (Python ipaddress module).
| Location | Name | IP entry | Check |
|---|---|---|---|
| L1 | Austin office | 203.0.113.10 | valid |
| L2 | Remote team VPN | 198.51.100.0/24 | valid |
| L3 | Agency | 192.0.2.300 | not valid (300 is above 255 in IPv4): HELD |
You want Austin and the VPN kept apart, so each gets its own traffic_type value. The value names below are my suggestion; please confirm or rename them.
| Rule | Location | traffic_type value | IP match |
|---|---|---|---|
| Rule 1 | L1 | internal_austin | 203.0.113.10 |
| Rule 2 | L2 | internal_vpn | 198.51.100.0/24 |
Which rows proceed: L1 and L2 (valid). Which row is held: L3 Agency gets no rule and no filter until you send a valid address (question 1). Rows: 3 (2 proceed, 1 held), counted by script. The match type for each rule is chosen in the rule's IP address settings; my sources do not list the match type names, so please pick the one your screen offers for a single address (L1) and for a range (L2).
Filter plan
| Filter | Type | traffic_type value | Starting state |
|---|---|---|---|
| F1 | Internal traffic, exclude | internal_austin | Testing |
| F2 | Internal traffic, exclude | internal_vpn | Testing |
Limit check
Google allows "up to 10 data filters per property". Rule: total = existing + proposed.
| Item | Filters |
|---|---|
| Existing (Exclude dev, Active) | 1 |
| Proposed | 2 |
| Total after plan | 3 |
| Limit | 10 |
Validation steps
- Define each rule: Admin, Data streams, your web stream, Configure tag settings, Define internal traffic.
- Create each filter in Testing. In Testing, matching data is labeled with the "Test data filter name" dimension.
- In Explore, break down data by that dimension and check that F1 and F2 match the Austin and VPN traffic you expect, and nothing else.
Activation (held)
- Activate F1 and F2. HELD until you approve after step 3. Google says that once a filter is applied, "the effect on the data is permanent".
Questions for you
- What is the agency's correct IP address? 192.0.2.300 is not a valid IPv4 address.
- Do you have the Editor role on this property? Google says "You need the Editor role" at the property level to set this up.
- Your existing 'Exclude dev' filter is Active; do you want it left as is? I have not changed or reviewed it.
Needs your decision
- Approve creating the two rules and the two filters in Testing.
- Separately approve activation after the Explore check (HELD).