DogQ User-Agent
Learn about our User-Agent, public IP and the ways you can use it to better integrate DogQ into your pipeline.
“User-Agent” is a standard part of HTTP headers that web clients like browsers or web crawlers use to identify themselves to web servers. It plays the role of the client in a client–server system and when a web server receives a request from a client, it typically includes a User-Agent string. The string “DogQ Agent” in our User-Agent serves as a unique identifier for our automated testing software. Let's take a look at a couple examples of how you can use it to your benefit.
Bypassing CAPTCHA with an allow-list
CAPTCHA is a common anti-bot protection system and if the website you're testing utilizes it, DogQ will have trouble performing actions protected by it. As a workaround you can add DogQ to your allow-list so it would not be asked to "solve" CAPTCHA. This can be done in two ways:
use the string “DogQ Agent” from our User-Agent.
use our public IP address 3.145.188.138. Although, this is not preferable since IP may change under specific circumstances, for instance during maintanance or when upgrading the server.
Filtering DogQ activity from your GA4 reports
By default, the activity generated by DogQ is visible in your analytics when testing your website or web application. Here are the steps you can follow to exclude this traffic from your GA4 reports and view clear data of your site metrics:
in Google Analytics, click Admin.
in the Property column, click Data Streams.
click on a web data stream.
in the web stream details, click Configure tag settings.
click Show all.
click Define internal traffic.
click Create.
Enter a name for the rule.
Enter a value for the
traffic_type
parameter. Note:traffic_type
is the only event parameter for which you can define a value. By default, it'sinternal
, you can enter a new value (e.g.dogq
) to represent the traffic origin.in IP address > Match type, select IP address equals.
in IP address > Value, enter our IP address: 3.145.188.138.
click Create.
Please note that you need the Editor role at the property level to identify internal traffic and create, edit, and delete data filters.
Last updated