Tracking and cookies
The common guide to the marketing tools on the academy site (Google Tag Manager, Google Analytics 4, Google Ads, Meta, TikTok) - where they run, the cookie banner, Consent Mode v2, what we send and what we don't.
08/10/2026
In Settings › Integrations, Marketing category, each tool has its own card and page: Google Tag Manager, Google Analytics 4, Google Ads, Meta and TikTok. Once connected, the academy's tools see visits, course views, requests, sign-ups and purchases on the academy site, to measure and optimise your ads.
This page gathers the rules shared by all of them: where they run, the cookie banner, consent and what we send. How to find the ID, the events with each tool's names and how to check them are on each tool's page.
The tools
You enter only the IDs, never code to paste: Aladia checks the format and loads the official scripts from Google, Meta and TikTok domains. You need the Owner or Admin role in the workspace.
| Tool | What to enter | Format | Consent needed | Guide |
|---|---|---|---|---|
| Google Tag Manager | Web container ID | GTM-XXXXXXX | starts with Consent Mode v2 denied | Google Tag Manager |
| Google Analytics 4 | Measurement ID | G-XXXXXXXXXX | Statistics (without: cookieless pings) | Google Analytics 4 |
| Google Ads | Conversion ID + purchase and request labels | AW-XXXXXXXXX | Marketing (without: cookieless pings) | Google Ads |
| Meta | Dataset ID (formerly pixel) | 15-16 digits | Marketing (without: not loaded) | Meta |
| TikTok | Pixel ID | ~20 uppercase letters and digits | Marketing (without: not loaded) | TikTok |
Each page has a switch, the ID field and Save: saving one tool doesn't touch the others. Once on and saved, the Active badge shows on the page and on the card. When off, the ID stays saved.
Where they run
The tools run only on the public pages of the academy site (<slug>.aladia.io and your custom domain):
- the academy storefront and Marketplace;
- each course's public page and request form (
/courses/…/richiedi); - checkout (
/checkout) and the thank-you page (/grazie); - sign-in and sign-up.
Never in the members' area (lessons, chat, calendar, settings…) and never on app.aladia.io. When someone moves from the site into the members' area the page reloads once, so no academy script stays active.
The cookie banner
With at least one tool on, the site shows the cookie banner to every new visitor, with three equally weighted choices:
- Accept: statistics and marketing;
- Reject: technical cookies only;
- Customize: Statistics (Google Analytics) and Marketing (Google Ads, Meta, TikTok) separately.
The choice lasts 6 months (site cookie aladia-consent), then the banner shows again. The Cookie preferences link in the footer (and below the sign-in and sign-up pages) reopens it at any time. The banner links to the academy's privacy policy, the address set in Settings › Requests and sales › Form privacy; if there is none, to Aladia's.
Consent Mode v2 and consent
| Tool | Before choosing or after Reject | With consent |
|---|---|---|
| Google Tag Manager, GA4, Google Ads | Loaded with Consent Mode v2 all denied (ad_storage, analytics_storage, ad_user_data, ad_personalization): no cookies, only anonymous pings Google uses for modelling | Statistics → analytics_storage granted; Marketing → ad_storage, ad_user_data, ad_personalization granted |
| Meta | Not loaded | Loaded only with Marketing consent (fbq('consent', 'grant')); if consent is withdrawn, fbq('consent', 'revoke') |
| TikTok | Not loaded | Loaded only with Marketing consent; if consent is withdrawn, ttq.revokeConsent() |
The default consent is set before GTM and the Google tag load (Google: Consent Mode, Google Ads: consent mode). For the tags you add in GTM, use the tag's Consent settings so they respect the visitor's choice.
The events, in short
The same six moments of the visitor journey, with the course as the product (item_id/content_id = course ID). Names, parameters and what each tool receives are on its page.
| Aladia event | When | GTM / GA4 | Google Ads | Meta | TikTok |
|---|---|---|---|---|---|
| Page view | Every public page, also when navigating without reloading | page_view | (Google tag on load) | PageView | ttq.page() |
| Course viewed | Opening a course page, by someone not enrolled | view_item | — | ViewContent | ViewContent |
| Checkout opened | Opening checkout | begin_checkout | — | InitiateCheckout | InitiateCheckout |
| Request sent | Successful submission of the request form | generate_lead | request conversion | Lead | SubmitForm |
| Sign-up | Account created and verified on the site | sign_up | — | CompleteRegistration | CompleteRegistration |
| Purchase | Successful payment, once per purchase | purchase | purchase conversion | Purchase | CompletePayment |
Every event has an event_id (for purchases purchase.<checkout session ID>), also passed to Meta (eventID) and TikTok (event_id): it is the same one used by server-side sending, so every conversion is counted once.
What we DON'T send
- Personal data: no email, phone, name, address or form data in the events.
- The members' area: lessons, chat, grades, calendar and settings send nothing.
- Your own code: no scripts are pasted; only IDs in the tool's format.
- Personal data in clear text from the server: with server-side sending email and phone go out only as SHA-256 hashes, and only with consent.
Double counting
One channel per tool
Google Tag Manager and the direct tools (GA4, Google Ads, Meta, TikTok) get the same events. If your GTM container also has the tag of a tool you turned on directly in Aladia, that event is counted twice: the pages flag it with a warning. For each tool choose: either in the container, or on its page.
Server-side sending
08/10/2026
Besides the browser, Aladia can send conversions straight from the server to Meta, TikTok and Google Analytics 4 (and, through GA4, to Google Ads). Events then arrive even when the browser loses them (ad blockers, Safari limiting cookies, the page closed right after paying), and purchases made after signing in and instalment courses are counted too. Turn it on in the Server-side sending section of each tool's page: Meta, TikTok, Google Analytics, Google Ads.
| Event | When, from the server | GA4 | Meta | TikTok |
|---|---|---|---|---|
| Checkout opened | Payment session created (as a guest or signed in) | begin_checkout | InitiateCheckout | InitiateCheckout |
| Request sent | Request saved (not spam) | generate_lead | Lead | SubmitForm |
| Sign-up | Email code verified on the academy site | sign_up | CompleteRegistration | CompleteRegistration |
| Purchase | Payment succeeded on Stripe (instalment courses: on the first instalment), once per purchase | purchase | Purchase | CompletePayment |
Page views and course views stay browser-only. The purchase value is the amount collected by the payment session (for instalment courses, the first instalment).
- Deduplication: browser and server use the same
event_id(for purchasespurchase.<checkout session ID>), so Meta, TikTok and GA4 count the event only once. On our side too, every event goes out once per channel. - Consent: the server sends something only for visitors who accepted cookies in the banner: Meta and TikTok with Marketing consent, GA4 with Statistics (and the
_gacookie). Without consent we send nothing. - Privacy: email, phone, first and last name only as SHA-256 hashes after normalization (lowercase email without spaces, phone with country code), never in clear text. IP address and browser go only to Meta and TikTok, which ask for them that way, and are deleted from our log as soon as the send succeeds. GA4 gets no personal data: only the
client_idfrom the_gacookie. - Tokens and secrets: write-only. We store them encrypted and never show them again (you only see "ends with …1234"); you can replace or delete them. The browser tool must be on with the same ID (dataset, pixel, measurement ID).
- Outcome: the section shows the last send ("Last send: ok at 12:31") or the error (e.g. Invalid token). If the platform does not answer or asks to slow down we retry on our own (after 1, 5, 15 minutes, 1 hour, 3 hours); a rejected token is not retried: replace it.
- Server-side Google Tag Manager: a GTM server container (Google: server-side tagging) cannot be connected yet; it is a later phase.
FAQ
- The banner doesn't show. No tool is on and saved, or you already chose in this browser in the last 6 months: use Cookie preferences or an incognito window.
- Does the old link to the "Tracking" page still work? Yes:
…/settings/integrations/trackingleads to the Integrations page, and links with a tool's anchor (#tracking-ga4…) to its page. - Where do I see the requests? In Requests: see Information requests.