Install the beacon

The beacon is a small script that counts, on the client site, how often Meta Pixel, GA4, Google Tag Manager and TikTok send events. That gives you real event numbers in Trackneat and an alert when clearly fewer arrive than usual. The beacon is included in 1 Website Plus and from the Agency plan.

You can also forward this guide to whoever looks after the client site technically. They don't need a Trackneat account, only the script tag from step 1.

1. Copy the script tag

In Trackneat, open the site, switch to the “Settings” tab and click “Copy script tag” in the “Beacon Installation” card. Every site has its own script tag. It looks like this:

<script src="https://trackneat.com/api/b/s?k=tn_xxxxxxxxxxxxxxxxxxxxxxxx" async></script>

2a. Install via Google Tag Manager

  • Open tagmanager.google.com and select the client site's container.
  • Click “Tags”, then “New”.
  • Click “Tag Configuration” and choose “Custom HTML”.
  • Paste the copied script tag into the HTML field.
  • Click “Triggering” and choose “All Pages” (type “Page View”).
  • Name the tag, for example “Trackneat Beacon”, and click “Save”.
  • Click “Submit” in the top right, then “Publish”. Only then is the beacon live on the site.

2b. Install directly in the code

Without Tag Manager, add the script tag to the <head> section that loads on every page:

  • Shopify: Online Store > Themes > “…” on the current theme > “Edit code” > file layout/theme.liquid, right before </head>.
  • WordPress: with a header code plugin (for example WPCode) or in the child theme's header.php, before </head>.
  • Other systems: in the page template that loads everywhere, before </head>.

Thanks to “async”, the beacon doesn't hold up page loading. It still counts events that were sent before it loaded.

3. Check that the beacon arrives

  • Open the client site in a normal browser window without an ad blocker and accept the cookie banner, so the tracking tags fire. The beacon only counts events that are actually sent.
  • About 3 seconds after loading, the beacon sends its first count. In the developer tools you'll see a request to trackneat.com/api/b/i in the “Network” tab.
  • The site in Trackneat then shows “Installed” under “Beacon Status”. You don't need to click anything, just reload the view in Trackneat.
  • The event chart fills from day one. Alerts on drops need comparison data and usually start after one to two weeks.

If it stays “Not installed”

  • The container isn't published. Check in Tag Manager that you clicked “Submit” and “Publish” after saving.
  • The tag depends on consent and you didn't accept during the test.
  • An ad blocker in the test browser blocks the request. Test in a window without one.
  • The site has a Content Security Policy. Then trackneat.com must be allowed for scripts (script-src) and connections (connect-src).
  • No tracking fires on the site right now. Then there's nothing to count, which is exactly what Trackneat's checks will show you too.

Privacy

The beacon sets no cookies and sends no personal data, only counters per platform and event name. How this is secured technically is on the “Security” page.

Whether you control the beacon through your consent tool is up to you and your client. If it only loads after consent, it only counts visits with consent.