Google Analytics (GA) and Google Tag Manager (GTM) Integration
When customers use Google Analytics (GA) to track web traffic, they can easily add their GA tracking IDs to all candidate journeys (vacancies) without any complex setup.
Harver does not embed marketing pixels or cookies directly into candidate journeys. Instead, we enable customers to integrate their own Google Tag Manager (GTM) container at the account level. Once the GTM container ID is added, customers can manage all marketing and analytics tags directly within GTM. These tags will only load for candidates who have provided cookie consent, ensuring compliance with privacy regulations.
Harver’s “Bring Your Own Tag Manager” approach ensures data privacy, platform security, and clear ownership boundaries, while giving customers the flexibility to manage their own tracking needs safely.
Adding your GA and GTM tracking codes
Customer Admin users can configure their Google Analytics (GA) and/or Google Tag Manager (GTM) tracking codes in Account Settings.
Simply enable the desired integration option and paste the corresponding tracking code into the relevant field.
The tracking codes must follow the official Google Analytics and Google Tag Manager formats:
Google Analytics (GA4) Measurement ID:
Format example → G-XXXXXXXXXX (e.g., G-1A2BC3D4E5)
Google Tag Manager (GTM) Container ID:
Format example → GTM-XXXXXXX (e.g., GTM-A1B2C3D)
Make sure you copy the exact ID from your Google Analytics or Google Tag Manager account settings. Incorrect or incomplete IDs may prevent data from being collected correctly.
Once the codes are saved in the account setting, you need to ensure the candidate journeys will serve these as well.
Configuring the Landing page modules
For every vacancy where the GA/GTM tracking should be enabled, you have to edit the landing page module.
You need to enable “non-functional“ cookies for Candidates and select the type.
Please note that Mandatory and Hidden cookies are not compliant with GDPR. In the European Union and in other regions where local privacy regulations apply, these options should not be used.
It is the customer’s responsibility to ensure compliance by understanding their audience and adhering to the applicable local data protection laws.
The cookie text content must comply with the applicable local privacy regulations and clearly explain the purpose of each cookie.
It is the customer’s responsibility to provide an appropriate consent message and, if applicable, include an optional cookie policy link for candidates to learn more.
Cookie consents in action
The cookie consent banner appears on the landing page and remains visible until the candidate either accepts or rejects the cookies.
Cookies are only loaded into the candidate’s browser if they select “Accept all” and begin the journey — that is, after they register, verify their identity via the OTP code, and reach the first assessment module.
If the candidate rejects cookies, no cookies will be loaded at any point during their session.
If the candidate accepts cookies at a later stage, the cookies will be loaded from that moment onward within the candidate journey.
Google Tag Manager events in the Candidate Journey
If Google Tag Manager (GTM) is configured, Harver will automatically construct and fire GTM events throughout the lifecycle of a candidate’s journey.
There are two key events recommended for customers to track:
Started (
vacancyStarted) → Triggered when the candidate has registered and begun the first assessment module.Completed (
vacancyCompleted) → Triggered when the candidate has reached the end-page module, marking the completion of their journey.
Each journey lifecycle event includes the event name and associated data that will be pushed into the GTM container.
Customers should configure the following events in their GTM container to capture these journey milestones:
vacancyStartedvacancyCompleted
Example GTM configuration
Once Harver is configured with your GTM container ID, you can set up triggers and tags to capture key candidate journey events such as vacancyStarted and vacancyCompleted.
Recommended steps
Step 1: Log in to your Google Tag Manager account and select the container you configured for Harver.
Step 2: Create Custom Event(s) Trigger for the Harver events. Just add a new Trigger for each event as “Custom event“, set the event name and set This trigger fires on → All Custom Events.
New trigger:
Step 3: You can configure your custom tag triggered with the new event.
Step 4: Preview. Click Preview in GTM to test your configuration. Start a candidate journey in Harver and confirm that the events appear in GTM’s Preview mode (check the Data Layer tab).
We recommend testing it with a vacancy’s Authentication Strategy set to “Harver first”.
Step 5: Once verified, click Submit → Publish to activate the configuration.
FAQ
Why don’t Harver allow adding “tracking pixels“ directly to the candidate journeys?
Embedding tracking pixels directly would mean Harver is collecting and transmitting candidate data (e.g., IP address, cookies, identifiers) to third-party systems. This blurs the line between Harver’s role as a data processor and the customer’s role as a data controller, introducing potential legal liability under GDPR and similar regulations.
Tracking pixels execute JavaScript from third-party sources, increasing risks of Malicious code injection, Data leakage or exfiltration and Cross-site scripting (XSS) vulnerabilities. GTM containers isolate and sandbox customer scripts under their own control. This makes it safe.
Why do you only support Google Tag Manager (and Google Analytics) and not other 3rd parties?
Customer teams typically manage their tracking setup (e.g., Google Ads, Meta, LinkedIn) via GTM. Using GTM ensures they retain full control, responsibility, and visibility over all scripts and tags. GTM provides built-in version control, change history, and publishing workflows, enabling clear governance.
GTM is an industry-standard solution used across most enterprise platforms and it lets us keep the Harver experience fast and stable while still giving you complete flexibility.