Skip to main content

Configure your tag

tip

When you create a new Hitprobe account, we'll walk you through all the steps to set up your tag. You'll only need to refer to this guide if you get stuck, if you need to configure more advanced options, or if you want to add a tag to a different site later.

Create a site​

Before you can use Hitprobe, you’ll need to create an account, and add details of the site where you want to add the Hitprobe tag. There's a free plan with up to 50 sessions (clicks) a month, perfect for implementation and testing for as long as you need.

First, create an account. Then follow the steps to create your first site.

If you intend to use Hitprobe on multiple subdomains, make sure you enter your site's domain, not the subdomain. I.e. Use example.com and not signup.example.com. You can then use the same Hitprobe site key on example.com, signup.example.com, and other.example.com.

For each domain name you use, you'll need to create a separate site. Each site will have its own site key.

Get the tag​

First, select the site you need the site key for in the site switcher (top left directly under the Hitprobe logo). Then select Manage site from the menu. You'll find your tag under Integration > Hitprobe tag.

You'll learn how to add it to your site's pages shortly. Before you do, there are a few options you should know about that we'll look at next.

Tag options​

The tag's init method accepts a config object that allows you to set options for the tag. By default, only the siteKey is set. All the available options are explained here.

hp('init', { siteKey: '<your_site_key>', mode: 'tracked' });

siteKey​

The site key for the website that the tag is placed on must always be present. It's already set when you copy the tag from the console, but you can always find the site key under Manage site > Integration > Site key.

mode​

You can use the mode setting to tell the tag which types of visits/clicks to send to Hitprobe. By default (when omitted) it's set to 'tracked'. This sends events to Hitprobe whenever the click comes from a supported PPC network (i.e. Google) or has UTM/source tracking tags.

The available settings are:

  • tracked (default) - clicks originating from a supported PPC network or with UTM/source tracking tags.
  • ppc - clicks from any supported PPC network.
  • ppc_google - clicks from Google only.
  • ppc_meta - clicks from Meta only.
  • ppc_microsoft - clicks from Microsoft only.
  • all - clicks from any source, including organic.

Content Security Policies (CSPs)​

If your site declares a CSP (Content Security Policy), you will need to add Hitprobe's domains to your policy.

DirectiveAdd the domain
script-src*.hitprobe.com, *.hitprobe.net
connect-src*.hitprobe.com, *.hitprobe.net

This allows your page to load the tag from app.hitprobe.com, and then reach Hitprobe's platform from within the script.

What next?​

Choose how you would like to deploy your tag: