> ## Documentation Index > Fetch the complete documentation index at: https://help.weavely.ai/llms.txt > Use this file to discover all available pages before exploring further. # Track forms with Google Analytics & Google Tag Manager > Measure form views, traffic, and submit-button clicks from your Weavely forms in GA4, using your Measurement ID and Google Tag Manager. */} ## Part 1: Track form views with Google Analytics This connects your form directly to GA4 so you can see views and traffic sources. No Tag Manager needed. In Google Analytics, go to **Admin → Data streams**, open your web stream, and copy the **Measurement ID** at the top. It always starts with `G-` (for example, `G-XXXXXXXXXX`). The Measurement ID (`G-…`) is **not** the same as the Property ID (a plain number). Only the `G-` ID works here. Screenshot showing where to add a Google Analytics measurement ID to track form analytics in Weavely AI. Open your form, go to **Settings → Tracking**, and paste the ID into the **Google Analytics** field. Hit **Publish**. Tracking only goes live on the published form, not the editor preview. This tracks **views and traffic only**, not conversions. Submitting the form won't show up as anything special here. To track submissions, continue to Part 2. ## Part 2: Track form submissions with Google Tag Manager Google Analytics can't detect your form's submit button on its own, so this part uses Google Tag Manager to listen for the click and send a `form_submit` event to GA4. Every Weavely submit button carries the CSS class `submit-form`, and that's the stable hook you'll listen for. Screenshot showing how to enable Click Classes in Google Tag Manager. In GTM, go to **Variables → Configure** and enable **Click Classes**. Without this, your trigger can't see the button's class. Screenshot showing how to add a GTM trigger event for Weavely AI forms. Go to **Triggers → New** and choose trigger type **Click – All Elements**. Set it to fire on **Some Clicks**, with the condition: **Click Classes** → **contains** → `submit-form` Name it something like `Submit trigger` and save. Match on the class `submit-form`, not the button's `id`, which is generated per form and isn't reliable. Screenshot showing how to create a GTM tag for Weavely AI forms. Go to **Tags → New** and choose tag type **Google Analytics: GA4 Event**. Set: * **Measurement ID**: your `G-` ID (the same one from Part 1) * **Event Name**: `form_submit` * **Triggering**: the `Submit trigger` you just made Save the tag. Do **not** add a "Google Tag" / GA4 Configuration tag in GTM. Weavely's Google Analytics field (Part 1) already loads GA4 on the page, and adding it again in GTM would count every pageview twice. GTM should hold **only** the event tag. Screenshot showing where to add a Google Analytics measurement ID to track form analytics in Weavely AI. Copy your **Container ID** from GTM (it looks like `GTM-XXXXXXX`). In Weavely, go to **Settings → Tracking**, paste it into the **Google Tag Manager** field, and **Publish** the form. In GTM, click **Preview**, paste your published form's URL, and submit the form with any dummy data. In the Tag Assistant panel you should see your event tag fire **once** when you press submit. For a second check, confirm the `form_submit` event lands in GA4 under **Admin → DebugView**. Back in GTM, click **Submit → Publish** to make the container live. Preview mode alone doesn't publish your changes. This fires on the button **click**, not on a confirmed successful submission. That means clicks where a required field was empty can still count, so your `form_submit` number may run slightly high. It's a solid proxy for "roughly how many submissions"; just don't treat it as an exact count.