Microsoft Ads (Bing Ads)
Our Microsoft Ads (formerly Bing Ads) integration works by blocking suspicious clicks using audience exclusion. Read on to learn about how to set up your tracking template, and how we configure and manage your blocked user audience.
Make sure you've already followed the steps to install the Hitprobe tag, and that there is a Microsoft UET tag (conversion tracking pixel) loaded within your page.
Tracking template setup
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.
The tracking template can easily be added to your whole account without the need to edit individual ads through Microsoft's account-level tracking template setting.
Automatic setup
When you connect (or reconnect) Microsoft Ads to your site, we'll check if the tracking template is found. If not, Hitprobe will offer to setup the template automatically for you.
You can also check the status of the tracking template at any time by going to Manage site > Ad networks, find the Microsoft account, then select Manage > Tracking template setup.
If Hitprobe finds an existing tracking template (from another service), Hitprobe will not replace it. In this case, you can either choose to delete the old tracking template and retry, or follow the manual setup steps below.
Manual setup using tracking template
If Hitprobe can't automatically add the template, or if you choose the manual setup option when asked, 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.
Here is the tracking template if you still need it:
https://click.hitprobe.com/c/v1?site_key=<your_site_key>&msclkid={msclkid}&hp_source={Network}&hp_campaign={CampaignId}&hp_group={AdGroupId}&hp_content={AdId}&hp_term={keyword:default}&url={lpurl}
Make sure you replace <your_site_key> with the site key for your site.
When you have your template ready, head to Microsoft Ads, then select Campaigns > Settings > Account level options, and save the template in the Tracking template field. Remember to finally Save.
Manual setup using final URL
If you already use tracking templates on your account, and you can't replace them, you can still use Microsoft Ad's Final URL suffix field to make sure the correct info is available to the Hitprobe tag, without clicks going through our tracker.
If you don't use the click tracker, and the visitor bounces very quickly before the tag gets a chance to load, the click won't be recorded at all. So it's much better to follow the steps above for using the tracking template if possible.
Here is the final URL suffix you'll need:
msclkid={msclkid}&hp_source={Network}&hp_campaign={CampaignId}&hp_group={AdGroupId}&hp_content={AdId}&hp_term={keyword:default}&url={lpurl}
If you already use a final URL suffix, it's OK to merge these parameters in with your existing final URL.
When you have your final URL suffix ready, head to Microsoft Ads, then select Campaigns > Settings > Account level options, and save the template in the Final URL suffix field. Remember to finally Save.
Click tracking 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).
- Are there any lower level tracking templates or final URL suffixes that are overriding the account-level settings?
If you're still stuck, remember we're happy to help.
Audience exclusion
When a session is blocked at device level, Hitprobe will add the visitor to a Microsoft Ads audience. This audience can then be excluded from each of your campaigns so those visitors will not see any ads in the future.
When you connect (or reconnect) Microsoft Ads to your site, we'll check if audience exclusion is configured and working. If not, Hitprobe will offer to setup 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 Microsoft ad account panel, then select Manage > Audience setup.
Follow the steps and Hitprobe will create an audience for you, and associate it as a campaign exclusion to all of the campaigns in your account.
If you add new campaigns in future, Hitprobe will periodically recognize them and add the audience exclusion for you.
From now on, Hitprobe will add blocked users to this audience as soon as they're identified, and your Microsoft Ads integration is complete.