Should I use GTM or add GA4 directly?

Either works. GTM gives you more control: manage GA4, conversion pixels, and custom events from one place without changing Cavuno settings. If you only need GA4, adding the Measurement ID directly is simpler.

Can I use GTM and GA4 at the same time?

Yes, but avoid deploying the same GA4 destination both directly in Cavuno and through the GTM container. Duplicate measurement occurs only when both paths send the same event; adding an otherwise empty GTM container does not duplicate GA4 by itself.

Why aren't my GTM tags firing?

Verify your Container ID starts with 'GTM-' and that you published your GTM container after adding tags. Use GTM Preview mode to debug tag firing in real time.

Connect Google Tag Manager

Manage all tracking tags (analytics, ad pixels, custom events) from one GTM container.

By Abi Tyas Tunggal and Jack Walsh

Manage all your tracking tags from a single GTM dashboard. Instead of adding each tracking ID separately in Cavuno, add one Container ID and manage everything through Google Tag Manager.

Before you begin

You need access to a Google Tag Manager Web container and permission to publish it. Inventory the integrations already configured directly in Cavuno before recreating them in GTM; deploying the same destination through both paths can duplicate its events.

When to use Google Tag Manager

Use GTM when you want to:

Manage multiple tracking scripts from one place
Add custom event tracking without changing Cavuno settings
Control when and how tags fire using triggers and variables
Test tags before publishing with Preview mode

If you only need basic GA4 tracking, adding the Measurement ID directly is simpler.

Get your Container ID

Go to tagmanager.google.com
Create an account and container for your job board (select Web as the platform)
Copy your Container ID (starts with "GTM-")

Add to Cavuno

Go to Settings in the sidebar, then click the Analytics tab
Paste your Container ID in the GTM Container ID field
Click Save changes

Cavuno injects the GTM script automatically.

Verify the installation

In GTM, click Preview to start Tag Assistant
Enter your job board URL
Visit your job board in the new tab
Check the Tag Assistant panel to confirm GTM is connected

Troubleshoot the connection

If Tag Assistant does not connect, confirm the saved ID begins with GTM-, retry in a private window without an ad blocker, and accept Cavuno's cookie banner if consent is required. A connected container can still send no data when its tags are paused, have unmatched triggers, or were saved without publishing; inspect each tag in Preview mode before changing Cavuno settings.

Set up GA4 through GTM

If you want to manage Google Analytics through GTM:

In your GTM workspace, click Tags > New
Choose Google tag as the tag type
Enter your GA4 Tag ID or Measurement ID (starts with "G-")
Set the trigger to Initialization — All Pages so the Google tag loads before later page triggers
Click Save, then Submit to publish

Common GTM tags for job boards

Tag	Purpose
Google tag	Send traffic and behavior data to GA4
Meta Pixel	Retarget visitors on Facebook and Instagram
LinkedIn Insight Tag	Track LinkedIn ad conversions
Google Ads Conversion	Track conversions from Google Ads
Custom HTML	Add any third-party script

Standard dataLayer conversion events

Cavuno pushes a small set of standard events to window.dataLayer on hosted job boards. Use them as Custom Event triggers in GTM.

Operators who install Meta Pixel or LinkedIn Insight Tag directly in Cavuno (without GTM) get native conversion events for the same moments — see Meta Pixel and LinkedIn Insight Tag. Prefer either GTM tags or the direct Cavuno fields for a given destination so conversions are not counted twice.

Event	When it fires	Common payload fields
`sign_up`	A candidate or employer account is created (password, OAuth, or magic-link sign-up). For password sign-up this fires on the email-verification landing page immediately after account creation — not after the OTP is entered.	`method` (`password`, `google`, `linkedin`, `magic_link`), `board_slug`
`login`	A user signs in successfully	`method`, `board_slug`
`apply_click`	A candidate opens the apply flow (external redirect or native apply sheet). Not fired when the registration wall opens instead.	`job_id`, `job_slug`, `company_slug`, `apply_type` (`external` or `native`), `board_slug`
`apply_submit`	A native application is submitted successfully	`job_id`, `application_id`, `job_slug`, `company_slug`, `board_slug`
`job_alert_subscribe`	A job alert subscription is created	`board_slug`, `source`, optional `job_id`, `job_slug`

GTM loads on public board pages, including /auth/* and /onboarding/* (verify-email and resume), when a Container ID is configured. Cavuno pushes conversion events to window.dataLayer as they happen; when Require cookie consent is enabled, the GTM container itself loads only after the visitor accepts, then processes any queued events on that page. Accept the cookie banner on the verification page if you are testing password sign_up in GTM Preview.

Example GTM trigger: Trigger type = Custom Event, Event name = sign_up.

When cookie consent is enabled in Cavuno, the entire GTM container waits until a visitor accepts. This is different from an advanced Google Consent Mode implementation, where the container can load with consent defaults and update signals later. If you implement Consent Mode inside GTM, follow Google's consent configuration guidance and verify every tag's consent checks.

Next steps

Connect Google Analytics: use the simpler direct setup when GA4 is your only destination
Cookie banner: understand Cavuno's consent gate before publishing advertising tags