First thing first let’s see which reports can help you to identify Apache-HttpAsyncClient user agent traffic in Old Google Analytics properties and the newest Google Analytics v4 properties.
- Google Analytics v4 property: Reports -> User -> Tech -> Tech Overview -> scroll until Browsers
- Old Analytics property: Audience -> Technology -> Browser & OS
What could Apache-HttpAsyncClient traffic mean?
Well, there are a variety of reasons why you can see this traffic in Analytics but what we can say is that it’s not conventional Client-Side traffic but it could be attributed to Server-Side traffic.
Why do we see Apache-HttpAsyncClient traffic?
Most likely if you’re using Server-Side methodology to track the traffic on your website you’re seeing this traffic because there is no correct User-Agent assigned in the hit sent to Google Analytics from the Server-Side provider you’re using (I.E. Tealium EventStream – AudienceStream ).
When you send traffic to Google Analytics using Server-Side methodologies you perform an HTTP request with a custom payload to your Server-Side provider which is used then to redirect the traffic you’re collecting to your Web Analytics tools like Google Analytics.
The difference between a Client-Side Hit and a Server-Side hit, among the others, is the payload sent to, in this case, Google Analytics. With Client-side traffic you automatically send parameters like User-Agent, Google account ID, Browser language, Referrer, etc.. instead with Server-Side traffic you have to manually send them.
If you are struggling with this or other issues with your Google Analytics feel free to contact us. We also offer an Audit for your Google Analytics property as well as an expert eye on your tracking implementations with Tealium and Google Tag Manager.
