Google Analytics

Wire Recruitly's public pages and embedded forms into your own Google Analytics 4 property. Once connected, every Recruitly-hosted page a candidate or lead touches — job pages, application forms, candidate registration, GDPR consent, lead forms — reports into the GA4 property you already use, and forms embedded on your own site forward their events to the host page so tracking keeps working despite third-party-cookie blocking.

How the integration works

1. In the Recruitly Marketplace, connect Google Analytics and paste your GA4 Measurement ID (G-XXXXXXXXXX — find it in Google Analytics under Admin → Data Streams). That's the whole connection: Recruitly stores the ID. There is no OAuth or Google sign-in step.
2. Every Recruitly-hosted public page then loads gtag.js with your Measurement ID and fires standard GA4 events into your property.
3. When a Recruitly form runs inside an iframe on your website, it additionally relays every GA command to the parent page via postMessage — see Embedded forms & event relay for the message contract and the snippet.

What gets tracked, where

Surface	What fires
Hosted job pages & application forms (incl. success / duplicate / closed pages)	page_view and GA4 auto-collected events, under your Measurement ID
Candidate registration forms	page_view etc.
GDPR consent pages	page_view etc.
Lead capture forms	page_view, plus a generate_lead event on successful submission
Forms embedded in an iframe on your site	Everything above, relayed to the parent page (with the snippet installed)

generate_lead is a GA4 recommended event, so it slots straight into GA4's standard lead reporting — mark it as a key event (conversion) under Admin → Events.

Verifying it works

1. Realtime — open Reports → Realtime in GA4, then visit one of your hosted job pages: you should appear as an active user with a page_view.
2. DebugView — append ?debug_mode=1 to the page URL (or use the GA Debugger extension) and watch Admin → DebugView, including generate_lead after a test lead-form submission.
3. Embedded forms — see the verification steps for the iframe relay.

Universal Analytics (UA-XXXXX-Y)

The Configuration panel still shows a UA Tracking ID field for legacy accounts, but Google shut Universal Analytics down — UA properties no longer process data. Leave the field blank and use GA4. If only a UA ID is configured, hosted pages fall back to the old analytics.js pageview tracker, which Google no longer processes.

Troubleshooting

Symptom	Cause / fix
No data at all	Wrong Measurement ID (must start with G-), or you're looking at a different GA4 property than the ID belongs to. Check Admin → Data Streams.
Hosted pages track, embedded forms don't	The relay snippet isn't on the host page, or runs before gtag.js is initialised — install it correctly.
Events show in Realtime but not in reports	Standard GA4 processing lag (up to 24–48 h for standard reports). Realtime/DebugView is the source of truth for "is it wired".
Safari/Firefox visitors missing from iframe analytics	That's the third-party-cookie problem the relay exists to solve — install the snippet so events record first-party on your page.