📄️ Google Ads
The Google Ads integration enables three different blocking methods, IP and network exclusion, domain name exclusion, and audience exclusion. Read on to learn about how to set up your tracking template, and how to configure each of these exclusion types.
📄️ Google Ads tracking template
Hitprobe relies on a click tracker set as your account-level tracking template so that it can record details of every click, even if the visitor bounces very quickly before the page loads.
📄️ Google Ads audience exclusion
When a session is blocked at device level, Hitprobe can add the visitor to a Google Ads audience. This audience can then be excluded from your account so those visitors will not see any ads in the future.
📄️ Google Ads Performance Max
Audience exclusion works differently for Performance Max campaigns. This is because Performance Max doesn't support excluding by audience the same way other campaign types do. You'll need to tell Google to apply a value adjustment to your blocked audience, to optimize your campaigns away from it.
📄️ Meta Ads
The Meta Ads integration relies on adding blocked sessions to a Meta audience that is then excluded from your Meta ad sets. Here's how to set up Hitprobe to protect Meta ads.
📄️ Google Tag Manager datalayer
This guide explains how to hook into the GTM/datalayer events that Hitprobe triggers. If you're looking for instructions on how to set up the Hitprobe tag using Google Tag Manager, you'll need the setup guide instead.
📄️ Other Source Tagged
You can monitor, analyze, and report on traffic from any source, as long as you use click tracking, or the click includes standard UTM source parameters.