Your board already has built-in analytics with zero setup. Use the Tracking page when you also want your own tools on the board: Google Analytics 4, Google Tag Manager, or conversion pixels (Google Ads, Meta, LinkedIn) that fire when someone buys a posting or creates an account. Everything on this page runs on your public board only, never inside your admin dashboard.
Before you start
For Google Analytics you need a GA4 property. Your Measurement ID starts with
G-and is shown in Google Analytics under Admin, then Data streams, then your web stream.For Tag Manager you need a container. The container ID starts with
GTM-and is shown at the top of the Tag Manager interface.You need one or the other, not both. If you manage all your tags in GTM, enter only the container ID and add GA4 inside GTM.
Add your Google Analytics or Tag Manager ID
In the sidebar, click Settings (at the bottom), then click the Tracking card.
In the Google Analytics & Tag Manager card, paste your Measurement ID into Google Analytics ID (the placeholder shows the shape:
G-XXXXXXXXXX). The field also accepts olderUA-ids, Google AdsAW-ids, and FloodlightDC-ids.Or paste your container ID into Tag Manager container ID (
GTM-XXXXXXX).Click Save tracking settings at the bottom of the page.
You should see a Tracking settings saved confirmation. If the format is wrong, saving fails with a message like "That doesn't look like a Google Analytics ID": check for stray spaces or a copied label. Leaving a field blank simply disables that tag, which is also how you remove tracking later: clear the field and save.
What appears on your board
Once saved, every public page of your board renders the standard Google boilerplate for the IDs you entered: the gtag.js script for GA4 and the GTM loader for Tag Manager. The scripts load after the page becomes interactive, so they do not slow down the first paint. There is nothing to add in the code injection settings; entering the ID here is the whole job.
Add conversion trackers
The Conversion trackers card holds a snippet per event. Each snippet is injected and executed at the exact moment its event happens, which is what ad platforms need to attribute a conversion to a click. Paste the full <script> tag (or image pixel) that your ad platform gives you, for example a Google Ads event snippet, a Meta pixel fbq('track', ...) call, or a LinkedIn Insight event.
Still on Settings, then Tracking, scroll to Conversion trackers.
Paste a snippet into any of the four event boxes:
Employer purchase: fires on the checkout success page after an employer pays for a posting, package, or subscription.
Employer registration: fires when an employer creates an account on your board.
Job seeker registration: fires when a job seeker creates an account.
Job application: fires when a candidate submits an application on your board.
Click Save tracking settings.
Boxes you leave empty do nothing. Snippets fire only on your own board's pages, and only for that one event, so an "Employer purchase" pixel never fires on a registration.
How consent affects your tags
If the cookie-consent banner is enabled (it is on by default for new boards), your tags are consent-gated automatically:
Google Analytics and Tag Manager load only after the visitor grants analytics consent.
Conversion trackers fire only after the visitor grants marketing consent.
This means a fresh board with the banner on will show zero GA traffic until visitors start accepting cookies: that is the banner working, not the integration failing. If you serve an audience where a banner is not required and you want tags to load for everyone, you can turn the banner off. Both options are covered in Cookie consent and compliance.
Verify it works
Open your public board in a new tab (use the View public board link in the dashboard top bar).
If the consent banner appears, click Accept all.
In Google Analytics, open Reports, then Realtime. Your own visit should appear within a minute or two.
For conversion pixels, most ad platforms offer a tag debugger (such as Google Tag Assistant or the Meta Pixel Helper). Trigger the event, for example register a test job seeker account, and confirm the pixel fires.
Keep in mind that your built-in board analytics and GA will never match exactly: the built-in numbers are server-side and deduplicated per visitor per day, while GA counts what its script sees after consent.