{"id":4985,"date":"2022-02-16T11:53:23","date_gmt":"2022-02-16T08:53:23","guid":{"rendered":"https:\/\/trackingchef.com\/?p=4985"},"modified":"2022-09-04T17:15:45","modified_gmt":"2022-09-04T14:15:45","slug":"how-to-track-bot-traffic-in-your-google-ads-campaigns-for-free","status":"publish","type":"post","link":"https:\/\/trackingchef.com\/google-ads\/how-to-track-bot-traffic-in-your-google-ads-campaigns-for-free\/","title":{"rendered":"How to track bot traffic in your Google Ads campaigns for free"},"content":{"rendered":"\n

A recent Twitter discussion with PPC expert Kirk Williams<\/a> got me thinking about different ways advertisers can battle fraudulent clicks in Google Ads. While there are several great companies out there that offer these services (Cheq<\/a> and Clickcease<\/a> to name two), not every advertiser can justify the use of such tools in their stack.<\/p>\n\n\n\n

Then I remembered Simo Ahava had a great post on using Google’s Recaptcha to identify bot traffic in Google Analytics<\/a>. If you know Simo (if you don’t, shame on you!), you know he works all his magic through Google Tag Manager. So I figured that if we have the data available there, we might as well use it for Google Ads too.<\/p>\n\n\n\n

All it takes is a few simple steps:<\/p>\n\n\n\n

  1. Set up the reCAPTCHA tracking in GTM<\/li>
  2. Create and trigger Google Ads conversions<\/li>
  3. Report on these events in Google Data Studio<\/li><\/ol>\n\n\n\n

    Step #1 – Set up the reCAPTCHA tracking in GTM<\/h2>\n\n\n\n

    Simo has put up a great guide for this, with credit to Sebastian Pospischil and Philipp Schneider as well, no need for me to cover this step.<\/p>\n\n\n\n

    Just follow the steps here Improve Google Analytics Bot Detection With reCAPTCHA<\/a>. It’s really much easier than you think \ud83d\ude42<\/p>\n\n\n\n

    In a nutshell:<\/p>\n\n\n\n

    1. Generate a reCAPTCHA token<\/li>
    2. Add a Custom HTML tag to GTM<\/li>
    3. Add a PHP file to your server (if you’re using WordPress, it’s a copy paste process)<\/li>
    4. GTM Setup – Creating Data Layer values and GA event (optional)<\/li><\/ol>\n\n\n\n

      Step #2 – Create and trigger Google Ads conversions<\/h2>\n\n\n\n

      Now that we have the reCATPCHA tracking in place, we will start receiving a Data Layer event called ‘recaptcha’ in GTM, with the two additional Data Layer values: ‘recaptchaAnswer’ and ‘recaptchaScore’. These will be used to trigger the Google Ads conversions.<\/p>\n\n\n\n

      First, create a Google Ads conversion in your account. The type of conversion is ‘Website’ and the action is ‘Other’. Value should also be set to ‘Don’t use a value for this conversion action’.<\/p>\n\n\n\n

      The conversion count should be set to ‘One’, as the score can trigger multiple times during a session.<\/p>\n\n\n

      \n
      \"image-5343498\"<\/figure><\/div>\n\n\n

      IMPORTANT: Make sure you deselect the ‘Include in Conversions’ check box so that Google’s algorithm won’t optimize for this conversions event<\/p><\/blockquote>\n\n\n

      \n
      \"image-7432370\"<\/figure><\/div>\n\n\n

      Click on ‘Create’ and select ‘Use Google Tag Manager’<\/p>\n\n\n\n

      In your GTM account, create a new tag of the type ‘Google Ad Conversion Tracking’. Paste the Conversion ID and Conversion Label from Google Ads in the matching fields.<\/p>\n\n\n

      \n
      \"image-6410010\"<\/figure><\/div>\n\n\n

      Create a new trigger (you can do so from the tag setup) of the type ‘Custom Event’. The Event name to set is ‘recaptcha’.<\/p>\n\n\n\n

      Set the trigger to fire on ‘Some Custom Events’. Select the Data Layer Variable ‘dl_recaptchaScore’ and set the criteria to ‘less than 0.3’.<\/p>\n\n\n

      \n
      \"image-4796767\"<\/figure><\/div>\n\n\n

      Step #3 – Report on these events in Google Data Studio<\/h2>\n\n\n\n

      Surprisingly, this is actually the most annoying part. Reporting on specific conversions isn’t trivial in Google Ads, which by default reports on ‘All Conversions’. <\/p>\n\n\n\n

      The alternative is using Google Analytics, for views linked to Google Ads, but these lack some of the data available directly in Google Ads. Plus they have a 12-24 hours delay in reporting.<\/p>\n\n\n\n

      Luckily enough, there’s a great way to work around this by using Google Data Studio (DS).<\/p>\n\n\n\n

      1. In DS, create a new report and add Google Ads as a data source.<\/li>
      2. Click on ‘Add a chart’ and select Pivot table.<\/li>
      3. Place the table anywhere on the report.<\/li>
      4. Under ‘Row dimension’, add the Dimensions for which you want the table to report on, e.g. Campaign and Ad Group.<\/li>
      5. Under ‘Column dimension’, add ‘Segment Conversion Type Name’.<\/li>
      6. Under ‘Metric’, add ‘Conversions’<\/li><\/ol>\n\n\n\n

        Voil\u00e0! You have a fully set up table to report on fraudulent bot traffic in your campaigns.<\/p>\n\n\n

        \n
        \"image-8253695\"
        You can add a Date Range selector to control the date range shown on the table<\/figcaption><\/figure><\/div>\n\n\n

        While you can report on these ‘conversions’, the same report can’t show how many Clicks and Impressions these Campaigns\/Ad Groups have driven. It’s possible to create a Blended Data source that connects Click and Impressions with the data in the Pivot Table, so that your reporting gives a full view of your data.<\/p>\n\n\n\n

        Use Cases<\/h2>\n\n\n\n

        These reports can’t be used to ask Google for refunds on bot traffic, you can scratch that one off the board.<\/p>\n\n\n\n

        The immediate use case I have in mind is using this report to analyze Search Queries or Placements. You can add these as Row Dimensions in the DS report and drill down to identify which of these is burning through your ad spend with bot traffic.<\/p>\n\n\n\n

        Caveats<\/h2>\n\n\n\n

        Huge disclaimer: This is an experimental approach. Use it with more than a grain of salt.<\/p><\/blockquote>\n\n\n\n

        The reCAPTCHA scores are dynamic by nature. So if a legit user arrives from a shady source, he might initially score a low reCAPTCHA score that will gradually update to one of a legit user. This might cause some False Positives, as users will ‘graduate’ to being identified as legit after being marked as bot. I do believe this is more of an edge case, but if you’re tracking the data in Google Analytics as well, you should be able to easily identify such users and if this is an actual issue for your tracking.<\/p>\n\n\n\n

        Another point worth noting is that this solution won’t help recover ad spend from Google by claiming that these clicks were invalid. Check out this follow-up post on how to minimize click fraud in your Google Ads account (w\/o external apps!)<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

        A recent Twitter discussion with PPC expert Kirk Williams got me thinking about different ways advertisers can battle fraudulent clicks in Google Ads. While there are several great companies out there that offer these services (Cheq and Clickcease to name two), not every advertiser can justify the use of such tools in their stack. Then […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,39],"tags":[],"class_list":["post-4985","post","type-post","status-publish","format-standard","hentry","category-google-ads","category-google-tag-manager"],"_links":{"self":[{"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/posts\/4985","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/comments?post=4985"}],"version-history":[{"count":2,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/posts\/4985\/revisions"}],"predecessor-version":[{"id":5337,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/posts\/4985\/revisions\/5337"}],"wp:attachment":[{"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/media?parent=4985"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/categories?post=4985"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/trackingchef.com\/wp-json\/wp\/v2\/tags?post=4985"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}