Improve Google Analytics – Since reCAPTCHA v3 calculates

Since reCAPTCHA v3 calculates scores based on the interaction with users on the site, it is an ideal candidate to measure with Google Analytics, as we can secretly capture visitor buttons and use custom GA sizes to collect data. They also show how to create a custom HTML tag in Google Tag Manager to download the ReCAPTCHA JavaScript API and determine user honesty. This PHP code receives a response from the Google Tag Manager, checks the response with the reCAPTCHA management API and sends the received object in response, which in turn moves to the data level so that the tags can be used. Thus, it no longer sends the same reCAPTCHA value to Google Analytics when the session is active. Although Google Analytics provides a robotic filtering feature to filter “spam” and “robot traffic” out of sight, it is far from complete to deal with all the robot traffic that may reach the site. Google Analytics explains the meaning of the RecaptchaAnswer Event Action, Custom Dimension sample event whether or not the validation worked. This code block runs the JavaScript API of the reCAPTCHA in the user’s browser and sends the result to the PHP terminal that you configure in the next chapter. These two custom parameters allow us to continuously filter robot traffic from our Google Analytics production views. Copy the keys, because you need them quickly when you define custom HTML tags in Google Tag Manager and on the terminal on the server side. To better understand botnet traffic, create segments based on reCAPTCHA estimates. Google has introduced reCAPTCHA v3, which allows you to control traffic without having to interact with the user. In any case, robot traffic is unlikely to be your goal when creating a website, so the ability to target it in Google Analytics is a great advantage for data quality. Make sure that the size index and user settings are correct based on what you have previously set up in the Google Analytics administration. This prevents Google Analytics from flooding events unnecessarily when only the same value is sent for each event.