# Google Analytics Events

## 📺 Events&#x20;

Events are sent automatically from your survey to your Google analytics account to let you see what the respondents are currently doing on your survey.&#x20;

Using events you can see for example if the respondent has loaded the survey, submitted the survey and you can even identify the respondents taking the survey if you are using [security items](/form-management/security/security-items.md) like [tokens](/form-management/security/security-items/tokens.md) or [campaigns](/form-management/campaigns.md). &#x20;

## 👀 Viewing events

You can view the events posted by your survey from the **events page** of your Google Analytics accoun&#x74;**.**

![](/files/-MBmRoVmRNZgDmGl-dIB)

As you can see below we can thanks to posted events closely monitor what our respondents are doing in our survey.&#x20;

![](/files/-MBmLM0FYo913ehJXdAh)

{% hint style="info" %}
The event category name is the id of the survey being tracked.&#x20;
{% endhint %}

To see the details of the events you may click on the **event category** to view all their details regarding the requests including the id of the page that was loaded and in this example we can also see the value of the [security token](/form-management/security/security-items/tokens.md) that was used to access the survey to help us identify the respondent who is currently taking the survey.

![](/files/-MBmLAyj4KinF91nDhCj)

## ➡️ Supported Events

Following events may be sent from your survey to Google analytics&#x20;

* **`FormLoaded`** triggers when the survey is loaded up on the respondent's device.
* **`FormSubmitted`** triggers when a respondent saves his answers. The respondent id is send as event value. &#x20;
* **`FormUpdated`** triggers when the respondent updates his answers. The respondent id is send as event value.
* **`SessionRestored`** triggers when a respondent session restored for resume. The respondent id is send as event value.&#x20;
* **`SessionSaved`** triggers when the respondent saves his answers to resume them later on.
* **`PageLoaded`** triggers each time a page is loaded. The page id is send as an event value.&#x20;
* **`EmailCodeAuthSuccess`** triggers each time a valid [email code](/form-management/security/security-items/invitation-code.md) has been used to access the survey. Email code is send as an event value.
* **`EmailCodeAuthDenied`** triggers each time an invalid [email code](/form-management/security/security-items/invitation-code.md) has been entered to  access the survey. Invalid Email code is send as an event value..&#x20;
* **`TokenAuthSuccess`** triggers each time a valid [token](/form-management/security/security-items/tokens.md) has been used to access the survey. Token is send as an event value.
* **`TokenAuthDenied`** triggers each time an invalid [token](/form-management/security/security-items/tokens.md) has been entered to access the survey. Token is send as an event value.
* **`PanelAuthSuccess`** triggers each time a [panelist](/form-management/security/security-items/panel-security.md) is accessing the survey. Panelist id is send as an event value.
* **`PanelAuthDenied`** triggers each time an invalid [panelist](/form-management/security/security-items/panel-security.md) tries to access the survey. Panelist id is send as an event value.&#x20;
* **`HttpAuthSuccess`** triggers each time an [http security item](/form-management/security/security-items/http-security-function.md) is authenticated.
* **`HttpAuthDenied`** triggers each time an [http security item](/form-management/security/security-items/http-security-function.md) is denied.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ngsurvey.com/form-management/form-designer/google-analytics/google-anayltics-events.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
