> For the complete documentation index, see [llms.txt](https://docs.doubleloop.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.doubleloop.app/build/event-fields.md).

# Event fields

Here's a quick explanation of each event field. All of the fields are optional except for the title, data, and importance.

* **Event title**. The headline that appears wherever the event info is displayed. Example: "Homepage redesign went live."
* **When did the event occur**. The date of the event. Example: the date the product enhancement was released.
* **Importance**. The significance of the event. It determines how prominently the event is displayed in some views.
* **Impact.** When you set the impact for an event, it will appear as an annotation in the timeline on the workstream and all events pages. Positive impact displays in green. Negative impact displays in red.
* **Summary**. A description of the event.
* **Goal / Hypothesis**. When applicable, explain why the change was made. For example: "Our hypothesis is that, by making the button bigger, the conversion rate will increase."
* **Results**. After time passes, you can record the impact of the change. Example: "The conversion rate increased from 2% to 3%.
* **Type**. Record if the change was a fix, enhancement, chore, improvement, etc..
* **URL title.** A call-to-action to learn more about the event. Example: "Watch the demo!"
* **URL.** The URL where you can learn more, corresponding with the URL title.
* **Labels**. Make it easy to find the event later or add the event to a workstream that filters by label.
* **Contributors**. List the people who worked on the change; the PM, engineer, designer, etc. Give props!

##


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.doubleloop.app/build/event-fields.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.