Google Tag Manager
Connect the academy's Google Tag Manager container to the site, with Aladia events in the dataLayer (GA4 names), checks with Tag Assistant and how to avoid double counting.
08/10/2026
With Google Tag Manager (GTM) you load your own container on the academy site and manage any tags from there (GA4, Google Ads, Meta, TikTok, others). Aladia loads the container on the public pages of the site and pushes the visitor-journey events into the dataLayer, with GA4 recommended event names: in GTM you decide which tags fire on each one.
Cookies, consent and the pages where it runs apply to every tool: see Tracking and cookies.
Where to find the ID
- Open Tag Manager and pick the account.
- Open the site's Web container (none yet? Google: create an account and container).
- The Container ID is at the top, next to the name:
GTM-followed by letters and digits (e.g.GTM-AB12CD3).
You don't need to copy GTM's install snippet: Aladia loads it.
Connect it in Aladia
- Settings › Integrations, Marketing category, Google Tag Manager card.
- In the Connection section enter the
GTM-…ID and turn the switch on. - Press Save: the Active badge appears at the top, and the card on the Integrations page shows it.
You need the Owner or Admin role. If the ID has the wrong format the field shows Expected format: GTM-XXXXXXX and it won't save. Turning the switch off keeps the ID saved.
Events we send
Events reach the dataLayer with these names. Every event also carries event_id (for deduplication) and, where present, workspace. Sales events use the ecommerce object as in GA4 ecommerce, cleared before each event ({ ecommerce: null }) as Google requires.
| Aladia event | When | dataLayer 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 | ecommerce: currency, value, items |
| Checkout opened | Opening checkout | begin_checkout | ecommerce: currency, value, items |
| Request sent | Successful submission of the request form | generate_lead | lead_source, course_id, course_name, items |
| Sign-up | Account created and verified on the site | sign_up | method |
| Purchase | Successful payment, once per purchase | purchase | ecommerce: transaction_id, value, currency, coupon, items |
items holds the course: item_id (course ID), item_name, price, quantity. No personal data: no email, phone or name.
Setting up tags in GTM
- Create a Custom Event trigger for each name in the table (Google: triggers).
- For page views use the
page_viewcustom event, not the "All Pages" trigger together with "History Change": the site is a single-page app and you'd count pages twice. - For GA4 ecommerce tags turn on Send Ecommerce data with Data Layer as the source.
- In your tags use Consent settings (Google: consent in Tag Manager): the container starts with Consent Mode v2 all denied and receives the update after the visitor chooses.
How to check
- Turn GTM on, save, and publish the container in Tag Manager.
- Open the academy site in an incognito window and press Accept in the cookie banner.
- Open Tag Assistant › Add domain › site address: you see the
GTM-…container, the consent state and, at each step, the events in the table (Google: Tag Assistant). - Or use Tag Manager Preview to see which tags fire on each event (Google: preview and debug).
Common issues
- The container doesn't show in Tag Assistant. Check you saved with the switch on and that you're on a public page of the site (storefront, course, checkout, sign-in): it never runs in the members' area or on
app.aladia.io. - Tags don't fire. The container isn't published, or the trigger doesn't use the exact event name (case included).
- Pages are counted twice. You have an "All Pages" or "History Change" trigger: use only the
page_viewevent. - Purchases made after signing in don't arrive. In the
dataLayerpurchasefires from the checkout without sign-in; the other purchases are counted by server-side sending straight to GA4, Meta and TikTok. A server-side GTM container cannot be connected yet.
Double counting
GTM together with direct GA4, Google Ads, Meta or TikTok
If you turn on GTM and another tool directly in Aladia (GA4, Google Ads, Meta or TikTok), events go to both. If your container also has that tool's tag for the same events, they're counted twice: the GTM page flags it with a warning. Use one channel per tool: either in the container, or on its page in Aladia.
See also: Google Analytics 4, Google Ads, Meta, TikTok.