> For the complete documentation index, see [llms.txt](https://mobsted-2.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mobsted-2.gitbook.io/knowledge-base/references/intro-placeholder/events.md).
# Events
Event is the record in the [Backend](https://kb.mobsted.com/article/1igbgtsyhx-backend). It can be created on the following actions:
* [Button](https://kb.mobsted.com/article/ap8iv7mdhw-single-button) / [Link](https://kb.mobsted.com/article/vszrx4k33t-link) / [Image](https://kb.mobsted.com/article/alqkwjcy6c-image) click
* App Launch
* API request
This new record can contain any data you wish to be stored in it.
## How to create a click Event
1. Select "Actions" in the Properties of the [Single Button](https://kb.mobsted.com/article/ap8iv7mdhw-single-button) / [Link](https://kb.mobsted.com/article/vszrx4k33t-link) / [Image](https://kb.mobsted.com/article/alqkwjcy6c-image)
2. Click "Create Event"
3. Fill in the table: "Key" is the name of the field and "Value" is the parameter. The Parameter can be a static string or [Hashtag](https://kb.mobsted.com/article/9v4k7sfkq1-hastags) reference.
4. Click "Save"
## Where to find an Event Created
Navigate to the [Backend](https://kb.mobsted.com/article/1igbgtsyhx-backend) of the platform, the new row was created that contains all the info on the Event - its **Key** and the **Value**. If you click on the [Event](broken://pages/-LnrgKT0VG3V316rWrg-) you will see it.
## Reading Events
Click on Event to open up its details.
The pop-up displays data saved to **event** during creation and **app state** snapshot data for that moment.
Event pop-up contains following info:
1. The current [Status](https://kb.mobsted.com/article/bsk1mr932m-statuses) of the event. The status can be tracked by using [filters](/knowledge-base/basics/introduction/use_automatic_data_filters.md). [Click here to learn more on Statuses.](https://kb.mobsted.com/article/bsk1mr932m-statuses)
2. Location of the of the device when the event was created.
3. The info on the current event. It contains all the information that was passed in the form of **Key** and **Value** pairs.
4. Files if any file was attached event using the file element.
5. The metadata on the [Object](https://kb.mobsted.com/article/sf7369s2zb-objects) like which browser he used to access the app, which version of operating system, etc.
6. The information about the Object that this event applies to. This is used for convenience purposes to avoid the need to navigate back and forth between Backend and the Objects tabs.
## Working with Events using API Calls
In order to Create / Update / Delete an Event using API Request you should do the following:
1. Get Access token -
2. Create / Update / Delete the Event -
## Good and Almost Good Practices
Events are mostly used when you want to submit some dynamic data.
| **Good Use** | **Could be Better** |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| You have a "Submit a complain form" with some [dropdowns](https://kb.mobsted.com/article/ktiu8t3of5-select-basic) or [text inputs](https://kb.mobsted.com/article/qrub1bfs16-text-input) as well the [button](https://kb.mobsted.com/article/ap8iv7mdhw-single-button) to submit the complain. Since one AppUser can submit multiple complains, it's is good idea to create an event for the button press and store the data from the dropdown and text input in this Event. | You have a "Enter your personal info form" asking the AppUser for the name and DOB. Creating an Event for the button to submit the info entered is redundant since this info is static and will be probably asked only when the AppUser opens the App for the first time. |
### Perform actions on Events
Events can be tracked by filters. Using filters combined with [triggers](https://kb.mobsted.com/article/2sbqtazf79-triggers) allows to set up the rules to perform actions on the Events. Please refer to [Triggers](https://kb.mobsted.com/article/2sbqtazf79-triggers) article for more info.
## RECOMMENDED ARTICLES
* [Backend](https://kb.mobsted.com/article/1igbgtsyhx-backend)
* [Hashtags](https://kb.mobsted.com/article/9v4k7sfkq1-hastags)
* [Single Button](https://kb.mobsted.com/article/ap8iv7mdhw-single-button)
* [Image](https://kb.mobsted.com/article/alqkwjcy6c-image)
* [Link](https://kb.mobsted.com/article/vszrx4k33t-link)
* [Triggers](https://kb.mobsted.com/article/2sbqtazf79-triggers)
## RECOMMENDED ARTICLES (EXTERNAL)
* [Getting Access Token](https://documenter.getpostman.com/view/4564343/S11LscyP#8cdbe179-7e2d-6218-9273-0df0bc8edfdf)
* [Creating / Updating / Deleting the Event](https://documenter.getpostman.com/view/4564343/S11LscyP#cfffad1b-9646-94a2-e74a-7eb03235caf3)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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://mobsted-2.gitbook.io/knowledge-base/references/intro-placeholder/events.md?ask=
```
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.