• Resolved walakaka

    (@walakaka)


    I have followed the following documentation to filter out internal traffic:

    We specified the following IP as our internal traffic: 195.133.131.203
    This is specified the data stream of our property

    Next we also specified the data filter for our property
    The data filter specifies the traffic_type that was mentioned in the data stream — traffic_type: internal

    GA4 is still registering traffic that originates from 195.133.131.203

    And when we checked the payload from the collect post request — there is no traffic_type parameter passed to GA4.
    We were expecting traffic_type: internal parameter to be passed to GA4

    My IP address is as follows:

    Would you be able to advise if this is an issue with Monster Insights? If there is any configuration I could check with Monster Insights, or more information that I can provide — do let me know.

    If this can be confirmed that it’s GA4 configuration that should be resolved, then the query has already been raised here: https://support.google.com/analytics/thread/249879870?authuser=1&hl=en&sjid=2111757330865926355-AP

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter walakaka

    (@walakaka)

    Just to highlight, that the traffic_type parameter is missing in the collect POST request to GA4 servers.
    Is it possible the Monster Insights configuration affects the parameters that are sent to GA4?

    Plugin Support Michelle D.

    (@devmich)

    Hi @walakaka,

    Thanks for reaching out. I’m sorry for the delay here, I’m currently consulting with our team for further details. I’ll post an update as soon as I’m able.

    Thank you!

    Plugin Support Michelle D.

    (@devmich)

    Hi @walakaka,

    Thanks for waiting. I was able to confirm that this isn’t an issue with MonsterInsights.

    From what I’m able to see, it’s not required for MonsterInsights to send a traffic_type parameter, since Analytics will automatically add this parameter to incoming events once configured within your tag settings.

    That being said, the guide you linked mentions it’s possible to manually track this parameter as well, and I was able to see that traffic_type does appear within the payload (as tt) if added to the Google tag script following these steps here: https://developers.google.com/analytics/devguides/collection/ga4/event-parameters?client_type=gtag

    Out of curiosity, have you tried following Google’s recommendation to test a data filter by using a free-form exploration or custom report? Here’s a link to the steps: https://support.google.com/analytics/answer/10104470/#testing-filter

    I noticed in your Google post the Realtime report was used to test the data filter, and so I was wondering if you’d see different results in the custom exploration.

    Thank you!

    Thread Starter walakaka

    (@walakaka)

    Hihi @devmich,

    Thanks for getting back! Definitely not looking to set the traffic_type value manually using a custom implementation — would prefer to have this set by GA4 since it’s already an existing functionality.

    To address your question, we have re-checked the implementation of our GA4 settings, and yes — we can confirm that the traffic_type value is not_set. Kindly see the following screenshot for reference:

    Internal Traffic is defined — here we specify the internal traffic source IP:

    Afterwhich, we define the data filter. Here, we specify the traffic_type to be included in the data filter. The Data Filter is named Internal Traffic.

    Note: We would expect the Data Filter name Internal Traffic to appear as one of the parameters in Test Data Filter Name, when viewing the GA4 reports

    Next, we hit our website — no traffic_type value is sent back to GA4 servers.
    Note: We assume that thet traffic_type value will be set on the client side based on GA4 scripts that were downloaded. And that GA4 servers would set the Test Data Filter Name accordingly based on the traffic_type sent back

    Lastly, to address your queries — we tested using the steps mentioned in the GA4 documentation, using Custom Exploration. And we can confirm that the no Test Data Filter Name of Internal Traffic was set:

    Do let us know if there are further information that would help you with this. Else, if this is not within the scope of monster insights, we can wait for GA4 team to revert here: https://support.google.com/analytics/thread/249879870?authuser=1&hl=en&sjid=2111757330865926355-AP

    We have dropped a request for assistance here, but I think the GA4 team might be busy celebrating new years, do let us know if you have any advise on how we can highlight this item to their attention

    • This reply was modified 1 year, 2 months ago by walakaka.
    Plugin Support Michelle D.

    (@devmich)

    Hi @walakaka,

    I’m sorry for the delay here. I appreciate the details, it looks like you’ve taken all of the necessary steps, and we appreciate you for proactively reaching out to the Google Analytics help community.

    At this point, I don’t have further insights to share unfortunately. The best next step will be to continue waiting for a response in your Analytics help thread.

    Thanks for your patience!

    • This reply was modified 1 year, 2 months ago by Michelle D..
    Plugin Support Michelle D.

    (@devmich)

    Hi @walakaka,

    I’m going to go ahead and close this thread for now, as we continue to wait for an update at https://support.google.com/analytics/thread/249879870?authuser=1&hl=en&sjid=2111757330865926355-AP. But if you’d like for us to assist further, please feel welcome to continue the conversation. Thanks!

    Thread Starter walakaka

    (@walakaka)

    @devmich,

    Hey hey, thanks for the response. Yeah — since it’s not a MonsterInsights specific issue, think we can close this to avoid clutter.

    Meanwhile, any ideas how we can get some attention from the GA4 team? Been radio silent on that front

    Plugin Support Michelle D.

    (@devmich)

    Hi @walakaka,

    I wish I could share some ideas, but I’m not entirely sure myself.

    Sorry about that!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Internal Traffic not Filtered Out’ is closed to new replies.