Meta Ads
The Meta Ads integration relies on adding blocked sessions to a custom audience that is then excluded from your ad sets. Here's how to set up Hitprobe to protect Meta ads.
Make sure you've already followed the steps to install the Hitprobe tag, and that there is a Meta Pixel (conversion tracking pixel) loaded within your page.
Tracking template setup
This is an optional step. Hitprobe can still exclude blocked users without it, but analytics and tracking of some clicks will be degraded without it.
Hitprobe relies on a click tracker or URL parameters so that it can record details of every click, even if the visitor bounces very quickly before the page loads.
You'll need to modify each of your ads. There are two options, but using the Website URL field is preferred. Choosing this option ensures that every click is tracked.
Setup by modifying the Website URL (preferred)
When you connect (or reconnect) Meta Ads, you'll be shown the tracking template in the console, with the correct site key already in place. You can copy it directly from there.
Then, you'll need to replace <your_landing_page> with the landing page URL (e.g. https://example.com/your/page).
If your landing page URL contains a query string (i.e. https://example.com/your/page?foo=bar), make sure you URL encode it. The query string will then be preserved through the redirect.
You can test the tracking template once it's ready. It should redirect to your landing page. Note that the test click may not show up in Hitprobe, as Meta will add a fbclid for real clicks. As long as the tracking template loads your landing page, it's working as expected.
Tracking template not working?
- Check that the site key is correct.
- Is your landing page domain the same as that of the site? You may only redirect to landing pages under your site's domain name (or a subdomain).
If you're still stuck, remember we're happy to help.
When you have your template ready, you'll need to edit your Meta ads, and save the template in the Destination > Website URL field. Do this for each ad you want to track with Hitprobe.
Setup by adding URL parameters
If you'd prefer not to modify the Website URL, you can still use URL parameters to help the Hitprobe tag recognise the source. In this case, use these parameters in the Tracking > URL parameters field.
hp_source={{site_source_name}}&hp_campaign={{campaign.id}}&hp_group={{adset.id}}&hp_content={{ad.id}}&hp_placement={{placement}}
Add these URL parameters for each ad you want to track with Hitprobe.
If there are already parameters in the URL parameters field, you can add the parameters above alongside those that are already set.
Audience setup
When a session is blocked at device level, Hitprobe will add the visitor to a Meta Ads custom audience. This audience can then be excluded from each of your ad sets so those visitors will not see any ads in the future.
When you connect (or reconnect) Meta Ads to your site, we'll check if audience exclusion is configured and working. If not, Hitprobe will offer to set up audience exclusion for you.
You can also check the status of audience exclusion at any time by going to Manage site > Ad networks, find the Meta ad account panel, then select Manage > Audience setup.
Follow the steps and Hitprobe will create a custom audience for you, and also add it as an ad set targeting exclusion to all of the (active) ad sets in your account.
If you add new ad sets in the future, Hitprobe will periodically recognize them and add the targeting exclusion for you.
From now on, Hitprobe will add blocked users to this audience as soon as they're identified, and your Meta Ads integration is working. You can also follow the steps in the next section to add the click tracker (optional).