Google Analytics 4
Connect a Google Analytics 4 property to the academy site with the measurement ID, the recommended events we send, how to check them in DebugView and how to avoid double counting.
08/10/2026
With Google Analytics 4 (GA4) you measure visits, course views, checkouts, requests, sign-ups and purchases on the academy site. Aladia loads the Google tag (gtag.js) with your Measurement ID on the public pages and sends GA4 recommended events, with the course as the product: GA4 ecommerce reports and conversions work with no further setup.
Cookies, consent and the pages where it runs apply to every tool: see Tracking and cookies.
Where to find the ID
- In Google Analytics open Admin (the gear at the bottom left).
- Data collection and modification › Data streams, open the site's web stream (none yet? Google: set up Analytics for a website).
- The Measurement ID is at the top right:
G-followed by letters and digits (e.g.G-AB12CD34EF) (Google: Measurement ID).
You need the G-… Measurement ID, not the property ID (digits only) or an old Universal Analytics ID (UA-…).
Connect it in Aladia
- Settings › Integrations, Marketing category, Google Analytics 4 card.
- In the Connection section enter the
G-…ID and turn the switch on. - Press Save: the Active badge appears.
You need the Owner or Admin role. With the wrong format the field shows Expected format: G-XXXXXXXXXX and it won't save.
One setting to change in GA4
We send page_view on every page, also when navigating without reloading (the config starts with send_page_view: false). In GA4, Data streams › your stream › Enhanced measurement › Page views › Show advanced settings, turn off Page changes based on browser history events (Google: enhanced measurement), or internal navigation counts twice.
Events we send
Every event goes to your ID with send_to. Names and parameters are those of GA4 recommended events.
| Aladia event | When | GA4 event | Parameters |
|---|---|---|---|
| Page view | Every public page, also when navigating without reloading | page_view | page_location, page_path, page_title |
| Course viewed | Opening a course page, by someone not enrolled | view_item | currency, value, items |
| Checkout opened | Opening checkout | begin_checkout | currency, value, items |
| Request sent | Successful submission of the request form | generate_lead | items |
| Sign-up | Account created and verified on the site | sign_up | method |
| Purchase | Successful payment, once per purchase | purchase | transaction_id, value, currency, coupon, items |
items holds the course: item_id (course ID), item_name, price, quantity (Google: GA4 ecommerce). The currency is the course's (EUR if not set). No personal data: no email, phone or name.
To count requests and purchases as conversions, mark generate_lead and purchase as key events in GA4.
How to check
- Turn GA4 on and save.
- Open the academy site in an incognito window and press Accept in the cookie banner.
- Connect the site in Tag Assistant: you see the
G-…tag, the consent state and the events. With Tag Assistant connected, events also show in GA4 › Admin › DebugView (Google: DebugView). - Or watch the Realtime report while you browse (Google: Realtime report).
Server-side sending
Besides the Google tag, Aladia sends begin_checkout, generate_lead, sign_up and purchase to GA4 with the Measurement Protocol, only for visitors who gave Statistics consent (the client_id from the _ga cookie is needed) and with no personal data. What we send, deduplication and privacy: Server-side sending.
- In GA4 open Admin › Data streams › your web stream.
- Under Measurement Protocol API secrets choose Create, give it a name (e.g. "Aladia") and copy the secret value (Google: Measurement Protocol).
- In Aladia, on this page, Server-side sending section: paste the secret, Save, then turn the switch on.
- Check: turn on Debug mode, do a test action on the site accepting cookies and look at Admin › DebugView (Google: DebugView) or the Realtime report. Turn debug mode off after testing. GA4 always answers "ok", even when something is wrong: if nothing shows up in DebugView, check the secret and the measurement ID (Google: validate events).
Common issues
- "Expected format" below the field. You copied the property ID or a
UA-ID: you need theG-Measurement ID of the web stream. - Pages are counted twice. Turn off browser history page changes in GA4 (above), or you also have a GA4 tag in Google Tag Manager.
- No data after Reject. That's expected: without Statistics consent GA4 only gets cookieless pings (Consent Mode v2), which Google uses for modelling.
- Purchases made after signing in don't arrive. From the browser the purchase fires from the checkout without sign-in; the others (after sign-in, instalments) are counted by server-side sending, for visitors who accepted cookies.
Double counting
GA4 here and in Google Tag Manager
If you turn on GA4 here and Google Tag Manager, and your container also has a GA4 tag for the same events, every event arrives twice: the page flags it with a warning. Keep GA4 in one place: either here, or in the GTM container.
See also: Google Tag Manager, Google Ads.